mcp-registry/ai.oobeprotocol.sap.mcp/sap-mcp · v0.9.86
Also listed as glama/oobe-protocol/sap-mcp-server
As of 2026-10-20 21:24 UTC, the Oobeprotocol Sap Sap MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 6 minutes.
Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments.
Claude Code
claude mcp add --transport http oobeprotocol-sap-sap-mcp-server https://mcp.sap.oobeprotocol.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"oobeprotocol-sap-sap-mcp-server": {
"type": "http",
"url": "https://mcp.sap.oobeprotocol.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
Loading this server's tool list costs an agent ~205,768 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
3 tool definition(s) exceed ~1,200 tokens each (largest: sap_agent_identity_plan, ~2,085).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~3,918 tokens every session. How to fix →
453 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Handshake + tools/list takes ~2,054 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
4 tools share an identical description with another tool on this server.
Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →
In the last 30 days: 0 tool(s) removed and 8 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fai.oobeprotocol.sap.mcp%2Fsap-mcp/fixes
{
"name": "das_searchAssets",
"description": "Search NFTs/assets with flexible filters via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x40",
"inputSchema": {
"type": "object",
"properties": {
"page": {
"type": "number",
"description": "Page pagination control for Das Search Assets."
},
"burnt": {
"type": "boolean",
"description": "Burnt parameter for Das Search Assets."
},
"limit": {
"type": "number",
"description": "Limit controlling the maximum number of results returned by Das Search Assets."
},
"frozen": {
"type": "boolean",
"description": "Frozen parameter for Das Search Assets."
},
"jsonUri": {
"type": "string",
"description": "Json URI parameter for Das Search Assets."
},
"grouping": {
"description": "Grouping key-value pair (e.g. [\"collection\", \"mint_address\"])",
"type": "string"
},
"compressed": {
"type": "boolean",
"description": "Compressed parameter for Das Search Assets."
},
"ownerAddress": {
"type": "string",
"description": "Solana public key (base58)"
},
"creatorAddress": {
"type": "string",
"description": "Solana public key (base58)"
}
},
"description": "Das Search Assets input schema. Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. Use exact field names from this schema; do not guess aliases or include private key material.",
"additionalProperties": false
},
"annotations": {
"title": "Das Search Assets",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Das Search Assets"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.oobeprotocol.sap.mcp/sap-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.oobeprotocol.sap.mcp/sap-mcp"}) over MCP.
sap_agent_identity_plan ~2,085 tokenssap_register_agent ~1,861 tokenssap_update_agent ~1,772 tokenssap_steve_launch_build_dbc ~1,060 tokenssap_perpspad_launch_dbc ~1,057 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fai.oobeprotocol.sap.mcp%2Fsap-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.oobeprotocol.sap.mcp%2Fsap-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.oobeprotocol.sap.mcp%2Fsap-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.oobeprotocol.sap.mcp%2Fsap-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fai.oobeprotocol.sap.mcp%2Fsap-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:39e75fbbf8d6c880…, first seen 2026-10-17, included at leaf 16832 of 35,315. Version history · verify what your client received.
Compare: most reliable blockchain servers · most reliable finance servers · most reliable knowledge servers · most reliable other servers · most reliable web servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 21:24 UTC, the Oobeprotocol Sap Sap MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 6 minutes.
Oobeprotocol Sap Sap MCP server advertises 300+ tools, including 3land_buyNFT, 3land_cancelListing, 3land_createCollection, 3land_listForSale, 3land_mintAndList.
Point your MCP client at this streamable-http endpoint: https://mcp.sap.oobeprotocol.ai/mcp
Glimind scanned all 453 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.