Related Servers

Many tools are clear within their protocol namespace, but the set contains near-duplicates and overlapping surfaces: sap_x402_paid_call and sap_payments_call_paid_tool have essentially identical descriptions, hosted escrow builders duplicate direct escrow writes, and multiple domain-resolution tools (sap_sns_resolve_wallet, sap_sns_resolve_domain, sns_resolveDomain, alldomains_resolveDomain) serve similar lookup purposes. This creates real misselection risk for agents.

Naming is inconsistent across the tool surface: sap_* tools use snake_case verbs (sap_create_attestation), while many protocol-prefixed tools use camelCase (jupiter_getQuote, 3land_cancelListing, spl-token_getTokenAccounts, magicblock_getAccountInfo). Each namespace is internally consistent, but across 271 tools there is no unified naming pattern.

271 tools is an extreme count for a single MCP server, far beyond the typical well-scoped 3-15 tool range. The server aggregates the SAP SDK, payment bridges, chat, SNS, MagicBlock, Jupiter, Meteora, Raydium, Drift, Adrena, Lulo, Jito, Metaplex, 3.Land, DAS, Pyth, CoinGecko, and many other unrelated protocol surfaces into one poorly bounded toolset.

Core SAP flows (registry lifecycle, escrows, x402 payments, reputation, memory, chat, SNS, tool registry) are covered in depth, including read and write paths. However, many bundled external protocols are partial one-off surfaces—for example, pump has launch/trade but no token or position reads, openbook lacks an orderbook reader, and some descriptions reference tools like sap_get_agent that are not present.