Scan report

ai.oobeprotocol.sap.mcp/sap-mcp

npm, scanned 2026-09-09, tool surface via remote-tools-list

This page reports an automated security scan of ai.oobeprotocol.sap.mcp/sap-mcp (npm), scanned 2026-09-09. It rates trust (provenance, transport, known vulnerabilities, instruction integrity) as grade C and capability risk (what the tools can do) separately at high. It does not certify the server is safe to connect; it reports what could be checked from outside.

Tool surface changed. This server’s tool schema differs from its previous scan (2026-07-28). Re-review §2 and §5 before continuing to trust it - silent schema changes are the "rug pull" pattern.

Automated checks

Status	Check	Policy	Result
PASS	Listed on the official MCP registry	§1.1	Listed on registry.modelcontextprotocol.io as ai.oobeprotocol.sap.mcp/sap-mcp. 1 finding Registry entry: ai.oobeprotocol.sap.mcp/sap-mcp ↗
PASS	Source repository is public and maintained	§1.2	Active repository with a license. 5 findings Repository ↗ Last push: 0 days ago Stars: 3 License: MIT Security policy (SECURITY.md): absent
WARN	Published package is consistent and attested	§1.3	Minor integrity gaps: no npm provenance attestation. 6 findings Package: @oobe-protocol-labs/sap-mcp-server@0.9.82 ↗ Ecosystem: npm Age: 72 days Weekly downloads: 508 Repo field matches source repo: true Build-provenance attestation: absent
PASS	Tool surface is inspectable and proportionate	§2.1–§2.4	412 tool(s) enumerated. Capabilities detected: filesystem, network-egress. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 16 findings Tools exposed: 412 sap_sns_register_agent_domain: filesystem sap_sns_build_set_primary_domain_transaction: filesystem sap_premium_plugin_catalog: network-egress sap_webhook_catalog: network-egress sap_premium_plugin_template: network-egress sap_premium_session_start: network-egress sap_premium_session_status: network-egress sap_premium_close_session: network-egress sap_premium_webhook_register: network-egress sap_premium_webhook_unregister: network-egress sap_premium_webhook_status: network-egress sap_premium_webhook_relay: network-egress sap_premium_webhook_relay_status: network-egress sap_skills_upgrade_plan: filesystem Detected capabilities: filesystem, network-egress
PASS	HTTPS-only endpoint	§3.1	Endpoint uses HTTPS. 1 finding Endpoint: https://mcp.sap.oobeprotocol.ai/mcp
UNVERIFIABLE	Authentication required	§3.2	Endpoint rejected the probe (HTTP 400); whether it requires authentication could not be determined.
WARN	OAuth protected-resource metadata published	§3.3	No protected-resource metadata found - clients cannot discover the authorization server per spec. 1 finding Checked: https://mcp.sap.oobeprotocol.ai/.well-known/oauth-protected-resource
PASS	No known vulnerabilities (OSV.dev)	§4.1	No advisories on record for @oobe-protocol-labs/sap-mcp-server @0.9.82 (npm).
WARN	Server-supplied instructions free of poisoning indicators	§5.1–§5.4	2 suspicious indicator(s) found in server-supplied instructions, tool descriptions, or schemas. 2 findings sap_discover_agents: cross-tool shadowing: before calling per-agent fetch tool sap_payments_prepaid_balance: cross-tool shadowing: before calling sap_payments_call_paid_tool

Verify manually - the scoring model can’t judge these for you

§2.3 - Is the tool surface no broader than the server’s stated purpose requires?
§3.4 - For stdio servers: which environment credentials does it read, and are they scoped rather than org-wide tokens?
§6.1 - Cross this server’s capabilities with your already-connected servers: any read-capability × send-capability pairs need explicit sign-off.
§6.2 - Run the connecting agent with sandboxing and egress controls sized to the combined tool surface, not just this server’s.

Methodology: MCP Server Security Policy. Checks and scoring weights are open source. Unfamiliar term? See the glossary.