Home / MCP registry index / ai.oobeprotocol.sap.mcp/sap-mcp
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp in the official MCP registry.
Endpoint https://mcp.sap.oobeprotocol.ai/mcp. Source: github.com/OOBE-PROTOCOL/sap-mcp.
The registry describes it as: Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments.
We read its 200 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
sap_protocol_invariants sap_agent_identity_plan sap_register_agent sap_update_agent sap_deactivate_agent sap_reactivate_agent sap_agent_migrate_pricing_menu sap_close_agent sap_report_calls sap_update_reputation_metrics sap_get_agent sap_get_agent_stats sap_get_global_state sap_build_agent_register_transaction sap_build_agent_update_transaction sap_build_agent_lifecycle_transaction sap_build_agent_report_calls_transaction sap_get_network_overview sap_agent_context sap_export_agent_oasf sap_get_agent_profile sap_is_agent_active sap_discover_agents sap_list_agents sap_list_all_agents sap_find_tools_by_category sap_get_tool_category_summary sap_fetch_capability_index sap_fetch_protocol_index sap_fetch_tool_category_index sap_fetch_tool sap_fetch_feedback sap_fetch_attestation sap_fetch_escrow sap_fetch_escrow_v2 sap_fetch_pending_settlement sap_fetch_dispute sap_fetch_vault sap_fetch_session sap_fetch_epoch_page sap_fetch_stake sap_fetch_subscription sap_x402_estimate_cost sap_x402_calculate_cost sap_x402_prepare_payment sap_x402_build_payment_headers sap_x402_build_headers_from_escrow sap_x402_has_escrow sap_x402_fetch_escrow sap_x402_get_balance sap_x402_settle sap_x402_settle_batch sap_escrow_build_create_transaction sap_escrow_build_deposit_transaction sap_escrow_build_settle_transaction sap_escrow_build_finalize_transaction sap_escrow_build_withdraw_transaction sap_escrow_build_close_transaction sap_create_escrow_v2 sap_deposit_escrow_v2 and 140 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-oobeprotocol-sap-mcp-sap-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.