{"id":"ai.oobeprotocol.sap.mcp/sap-mcp","slug":"ai-oobeprotocol-sap-mcp-sap-mcp","title":"SAP MCP Server","description":"Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments.","version":"0.7.1","publisher":{"kind":"domain","id":"mcp.sap.oobeprotocol.ai","label":"mcp.sap.oobeprotocol.ai","url":"https://mcp.sap.oobeprotocol.ai"},"website":"https://mcp.sap.oobeprotocol.ai/","repository":"https://github.com/OOBE-PROTOCOL/sap-mcp","remotes":[{"type":"streamable-http","url":"https://mcp.sap.oobeprotocol.ai/mcp"}],"packages":[{"registryType":"npm","identifier":"@oobe-protocol-labs/sap-mcp-server","version":"0.7.1","runtimeHint":"npx","transport":{"type":"stdio"},"runtimeArguments":[{"type":"positional","value":"--yes"},{"type":"positional","value":"--package"},{"type":"positional","value":"@oobe-protocol-labs/sap-mcp-server@0.7.1"},{"type":"positional","value":"sap-mcp-server"}],"environmentVariables":[{"description":"Keep SAP MCP pointed at the active profile manager instead of stale client env overrides.","format":"boolean","value":"false","name":"SAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE"},{"description":"Runtime log level for local SAP MCP stdio sessions.","format":"string","default":"info","name":"SAP_LOG_LEVEL"}]}],"published":"2026-07-13","updated":"2026-07-13","status":"online","auth":"","latency_ms":1626,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"sap_protocol_invariants","title":"Get SAP Protocol Invariants","description":"Free read-only protocol invariant card for agents. Returns the current SAP program id, protocol treasury, source-level expected 0.1 SOL registration fee invariant, hosted write routing rules, local sap_payments routes, identity pipeline, and forbidden actions. Use this before SAP registry writes and whenever fee/treasury behavior is unclear. SAP MCP context: Direct synapse-sap-sdk wrapper served b","read_only":false},{"name":"sap_agent_identity_plan","title":"Plan SAP Agent Identity","description":"Free read-only planner for SAP agent registration, profile/image updates, Metaplex/MPL Core identity linking, SNS linking, x402 pricing metadata, and post-write verification. Use this before sap_payments_register_agent or sap_payments_update_agent so agents know the exact local-signer route, metadata contract, forbidden actions, and protocol fee verification checklist. It does not touch chain and ","read_only":false},{"name":"sap_register_agent","title":"Register SAP Agent (Blocked in hosted Steve — use the builder)","description":"DISABLED: this direct write cannot run in hosted Steve (no server keypair) and fails with \"Explicit user approval is required\" or hosted_local_signer_required. In Steve web the ONLY registration path is sap_build_agent_register_transaction → Steve UI preview → user approval → browser signature → finalize submit. In LOCAL sap_payments setups use sap_payments_register_agent instead. SAP MCP context:","read_only":false},{"name":"sap_update_agent","title":"Update SAP Agent","description":"Local-signer-only: update the connected wallet SAP agent using SDK AgentModule.update. Hosted accountless SAP MCP rejects this direct write before x402 payment; hosted users should call sap_payments_update_agent from the local sap_payments bridge. SAP MCP context: Use this after sap_register_agent to refresh name, description, capabilities, pricing, supported protocols, x402 endpoint, or metadataU","read_only":false},{"name":"sap_deactivate_agent","title":"Deactivate SAP Agent","description":"Deactivate the connected wallet SAP agent. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools require signer policy, configured RPC, and the active SAP profile.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountle","read_only":false},{"name":"sap_reactivate_agent","title":"Reactivate SAP Agent","description":"Reactivate the connected wallet SAP agent. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools require signer policy, configured RPC, and the active SAP profile.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountle","read_only":false},{"name":"sap_agent_migrate_pricing_menu","title":"Migrate Agent Pricing Menu","description":"Backfill or resync the AgentPricingMenu PDA for the connected wallet SAP agent. Run this once if sap_update_agent, sap_close_agent, or createEscrowV2 fails with AccountNotInitialized on the pricing_menu account. Agents registered before pricing menus were created at registration need this one-time migration. Local-signer-only; hosted accountless SAP MCP rejects this direct write before x402 paymen","read_only":false},{"name":"sap_close_agent","title":"Close SAP Agent","description":"Close the connected wallet SAP agent and reclaim rent. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools require signer policy, configured RPC, and the active SAP profile.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: host","read_only":false},{"name":"sap_report_calls","title":"Report Agent Calls","description":"Report served call count for the connected wallet SAP agent. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools require signer policy, configured RPC, and the active SAP profile.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime ","read_only":false},{"name":"sap_update_reputation_metrics","title":"Update Reputation Metrics","description":"Update self-reported latency and uptime metrics for the connected wallet SAP agent. SAP MCP context: Reputation and trust flow. Use after verifying the target agent PDA or wallet and keep hashes/attestation metadata stable and auditable.\n\nSAP MCP execution guidance: Intent: local-signer write workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routi","read_only":false},{"name":"sap_get_agent","title":"Get SAP Agent","description":"Free exact SAP agent identity read by owner wallet. If omitted, fetches the connected wallet agent. Use this before paid discovery when the wallet is known. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: ","read_only":true},{"name":"sap_get_agent_stats","title":"Get SAP Agent Stats","description":"Free exact SAP agent stats read by agent PDA. Use after sap_get_agent or sap_get_agent_profile when stats are needed. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricin","read_only":true},{"name":"sap_get_global_state","title":"Get SAP Global State","description":"Free compact global SAP registry state read. Use for initial orientation before paid network analytics. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: priced by h","read_only":true},{"name":"sap_build_agent_register_transaction","title":"Build SAP Agent Registration Transaction","description":"Hosted-safe unsigned builder for register_agent. Browser runtimes preview this transaction, the owner wallet approves and signs locally, then it goes through the Steve signed-transaction submit relay or sap_payments_finalize_transaction. Pays the 0.1 SOL SAP protocol registration fee from the signing wallet. Keypair bytes never leave the user device. SAP MCP context: Direct synapse-sap-sdk wrapper","read_only":false},{"name":"sap_build_agent_update_transaction","title":"Build SAP Agent Update Transaction","description":"Hosted-safe unsigned builder for update_agent. The owner wallet signs locally after preview; null fields are ignored on-chain. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools require signer policy, configured RPC, and the active SAP profile.\n\nSAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid buil","read_only":false},{"name":"sap_build_agent_lifecycle_transaction","title":"Build SAP Agent Lifecycle Transaction","description":"Hosted-safe unsigned builder for the agent lifecycle actions: deactivate_agent, reactivate_agent, close_agent (reclaims rent), and migrate_pricing_menu (one-time backfill of the PricingMenu PDA for agents registered before pricing menus existed). The owner wallet signs locally. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools require","read_only":false},{"name":"sap_build_agent_report_calls_transaction","title":"Build SAP Agent Report Calls Transaction","description":"Hosted-safe unsigned builder for report_calls. The agent owner wallet signs locally after serving calls to consumers. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools require signer policy, configured RPC, and the active SAP profile.\n\nSAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; esti","read_only":false},{"name":"sap_get_network_overview","title":"Get SAP Network Overview","description":"Fetch real network counters from SDK DiscoveryRegistry.getNetworkOverview. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: priced by hosted x402 challenge. Routing","read_only":true},{"name":"sap_agent_context","title":"Get SAP Agent Context","description":"Free one-shot SAP orientation context for agents. Use this when the user asks whether SAP MCP is connected, wants to understand an agent/wallet, or needs the next safe paid/write route. It combines exact reads or a compact directory page with routing guidance without triggering x402. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools r","read_only":false},{"name":"sap_export_agent_oasf","title":"Export SAP Agent OASF Profile","description":"Export a known SAP agent into an OASF-style, machine-readable profile view for agent directories and cross-runtime discovery. This is an exact owner-wallet read: it derives the SAP agent PDA, fetches the current on-chain agent/profile/stats when available, and normalizes identity, protocols, capabilities, pricing, x402 endpoint, metadata links, and trust facts without exposing local wallet paths o","read_only":false},{"name":"sap_get_agent_profile","title":"Get SAP Agent Profile","description":"Micro-read exact SAP agent profile lookup by owner wallet. Use this for a known agent before read-premium discovery or enrichment. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery wor","read_only":true},{"name":"sap_is_agent_active","title":"Check SAP Agent Active","description":"Micro-read exact activity check for an owner wallet. Use this before read-premium discovery when the wallet is known. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing:","read_only":false},{"name":"sap_discover_agents","title":"Discover SAP Agents","description":"Paid hosted discovery for SAP agents. Search and filter the current on-chain AgentAccount directory by query, wallet, protocol, capability, x402 endpoint presence, and cursor pagination. Use this for targeted agent discovery before calling per-agent fetch tools. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain st","read_only":false},{"name":"sap_list_agents","title":"List SAP Agents","description":"Compact SAP agent orientation list. Micro-read when limit <= 20, view is compact, hydrate is false, and includeProtocolIndexes is false; larger or enriched pages are read-premium. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP M","read_only":true},{"name":"sap_list_all_agents","title":"List All SAP Agents","description":"Paid hosted global SAP agent directory read. Enumerates current on-chain AgentAccount PDAs and supports query, wallet, protocol, capability, x402 endpoint filtering, compact/full views, and cursor pagination. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, mem","read_only":true},{"name":"sap_find_tools_by_category","title":"Find SAP Tools By Category","description":"Find on-chain tool descriptors by SDK tool category name or numeric category. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: priced by hosted x402 challenge. Routin","read_only":false},{"name":"sap_get_tool_category_summary","title":"Get SAP Tool Category Summary","description":"Fetch SDK discovery summary across SAP tool categories. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: priced by hosted x402 challenge. Routing: paid hosted call;","read_only":true},{"name":"sap_fetch_capability_index","title":"Fetch Capability Index","description":"Fetch a SAP capability index by capability ID. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: priced by hosted x402 challenge. Routing: paid hosted call; call sap","read_only":true},{"name":"sap_fetch_protocol_index","title":"Fetch Protocol Index","description":"Fetch a SAP protocol index by protocol ID. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: priced by hosted x402 challenge. Routing: paid hosted call; call sap_est","read_only":true},{"name":"sap_fetch_tool_category_index","title":"Fetch Tool Category Index","description":"Fetch a SAP tool category index by numeric category. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: priced by hosted x402 challenge. Routing: paid hosted call; ca","read_only":true},{"name":"sap_fetch_tool","title":"Fetch SAP Tool Descriptor","description":"Fetch a tool descriptor by agent PDA and tool name. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_p","read_only":true},{"name":"sap_fetch_feedback","title":"Fetch SAP Feedback","description":"Fetch a feedback PDA by agent PDA and optional reviewer wallet. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_pay","read_only":true},{"name":"sap_fetch_attestation","title":"Fetch SAP Attestation","description":"Fetch an attestation PDA by agent PDA and optional attester wallet. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap","read_only":true},{"name":"sap_fetch_escrow","title":"Fetch SAP Escrow V1","description":"Fetch a V1 escrow by escrow PDA, or by agent PDA and optional depositor. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then us","read_only":true},{"name":"sap_fetch_escrow_v2","title":"Fetch SAP Escrow V2","description":"Fetch a V2 escrow by escrow PDA, or by agent PDA, depositor, and nonce. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use","read_only":true},{"name":"sap_fetch_pending_settlement","title":"Fetch Pending Settlement","description":"Fetch a V2 pending settlement PDA. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the","read_only":true},{"name":"sap_fetch_dispute","title":"Fetch SAP Dispute","description":"Fetch a V2 dispute PDA. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\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 ca","read_only":true},{"name":"sap_fetch_vault","title":"Fetch SAP Vault","description":"Fetch a memory vault by agent PDA. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the","read_only":true},{"name":"sap_fetch_session","title":"Fetch SAP Session","description":"Fetch a session ledger by session PDA. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when","read_only":true},{"name":"sap_fetch_epoch_page","title":"Fetch SAP Epoch Page","description":"Fetch an epoch page by session PDA and epoch index. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_p","read_only":true},{"name":"sap_fetch_stake","title":"Fetch SAP Stake","description":"Fetch agent stake by stake PDA or agent PDA. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_too","read_only":true},{"name":"sap_fetch_subscription","title":"Fetch SAP Subscription","description":"Fetch a subscription by PDA or by agent PDA/subscriber/subId. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payme","read_only":true},{"name":"sap_x402_estimate_cost","title":"Estimate SAP x402 Cost","description":"Estimate cost for a number of calls using SDK X402Registry.estimateCost. Reads escrow/pricing when available and supports optional volume curve overrides. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow.","read_only":false},{"name":"sap_x402_calculate_cost","title":"Calculate SAP x402 Cost","description":"Pure local cost calculation using SDK X402Registry.calculateCost; does not read chain state. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: free; call directly without x402. Routing: free host","read_only":false},{"name":"sap_x402_prepare_payment","title":"Prepare SAP x402 Payment","description":"Prepare an x402 payment context using SDK X402Registry.preparePayment. New production escrow funding should use Escrow V2 fields and nonce-aware flows. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pr","read_only":false},{"name":"sap_x402_build_payment_headers","title":"Build SAP x402 Payment Headers","description":"Build SAP x402 HTTP headers from a public PaymentContext returned by sap_x402_prepare_payment. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then p","read_only":false},{"name":"sap_x402_build_headers_from_escrow","title":"Build SAP x402 Headers From Escrow","description":"Build SAP x402 HTTP headers by fetching escrow data for an agent wallet with SDK X402Registry.buildPaymentHeadersFromEscrow. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid b","read_only":false},{"name":"sap_x402_has_escrow","title":"Check SAP x402 Escrow","description":"Check whether an x402 escrow exists for an agent/depositor pair. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: priced by hosted x402 challenge. Routing: paid hosted call; call sap_estimate_to","read_only":false},{"name":"sap_x402_fetch_escrow","title":"Fetch SAP x402 Escrow","description":"Fetch raw x402 escrow account data using SDK X402Registry.fetchEscrow. Resolves V2 first, then V1 fallback. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: priced by hosted x402 challenge. Ro","read_only":true},{"name":"sap_x402_get_balance","title":"Get SAP x402 Balance","description":"Fetch x402 escrow balance using SDK X402Registry.getBalance. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: read/discovery workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and kee","read_only":true},{"name":"sap_x402_settle","title":"Settle SAP x402 Calls","description":"Settle served x402 calls through SDK X402Registry.settle. Must be called by the agent owner wallet. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transacti","read_only":false},{"name":"sap_x402_settle_batch","title":"Batch Settle SAP x402 Calls","description":"Batch-settle served x402 calls through SDK X402Registry.settleBatch. Must be called by the agent owner wallet. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost an","read_only":false},{"name":"sap_escrow_build_create_transaction","title":"Build SAP Escrow V2 Create Transaction","description":"Hosted-safe unsigned builder for create_escrow_v2. Use this from hosted SAP MCP, preview the result, then call local sap_payments_finalize_transaction with submit:true. The depositorWallet signs locally; keypair bytes never leave the user machine. Defaults to DisputeWindow settlementSecurity=2 and rejects SelfReport/0. SAP MCP context: Hosted-safe unsigned Escrow V2 builder. The output is not subm","read_only":false},{"name":"sap_escrow_build_deposit_transaction","title":"Build SAP Escrow V2 Deposit Transaction","description":"Hosted-safe unsigned builder for deposit_escrow_v2. Use this when a hosted workflow needs to add funds to an existing V2 escrow, then finalize locally with sap_payments_finalize_transaction. SAP MCP context: Hosted-safe unsigned Escrow V2 builder. The output is not submitted and is not signed by hosted SAP MCP. Preview it, then call local sap_payments_finalize_transaction with submit:true and conf","read_only":false},{"name":"sap_escrow_build_settle_transaction","title":"Build SAP Escrow V2 Settlement Transaction","description":"Hosted-safe unsigned builder for settle_calls_v2. The agent owner wallet signs locally. DisputeWindow escrows create a pending settlement PDA; CoSigned escrows require the coSigner account when configured. SAP MCP context: Hosted-safe unsigned Escrow V2 builder. The output is not submitted and is not signed by hosted SAP MCP. Preview it, then call local sap_payments_finalize_transaction with submi","read_only":false},{"name":"sap_escrow_build_finalize_transaction","title":"Build SAP Escrow V2 Finalize Transaction","description":"Hosted-safe unsigned builder for finalize_settlement. Use after the dispute window has elapsed and a pending settlement exists; any payerWallet can locally sign to crank finalization. SAP MCP context: Hosted-safe unsigned Escrow V2 builder. The output is not submitted and is not signed by hosted SAP MCP. Preview it, then call local sap_payments_finalize_transaction with submit:true and confirm:tru","read_only":false},{"name":"sap_escrow_build_withdraw_transaction","title":"Build SAP Escrow V2 Withdraw Transaction","description":"Hosted-safe unsigned builder for withdraw_escrow_v2. The depositor signs locally and can only withdraw unlocked balance after pending amounts are excluded. SAP MCP context: Hosted-safe unsigned Escrow V2 builder. The output is not submitted and is not signed by hosted SAP MCP. Preview it, then call local sap_payments_finalize_transaction with submit:true and confirm:true. Never create temporary si","read_only":false},{"name":"sap_escrow_build_close_transaction","title":"Build SAP Escrow V2 Close Transaction","description":"Hosted-safe unsigned builder for close_escrow_v2. The depositor signs locally; the builder refuses to close until balance and pendingAmount are both zero. SAP MCP context: Hosted-safe unsigned Escrow V2 builder. The output is not submitted and is not signed by hosted SAP MCP. Preview it, then call local sap_payments_finalize_transaction with submit:true and confirm:true. Never create temporary sig","read_only":false},{"name":"sap_create_escrow_v2","title":"Create SAP Escrow V2","description":"Local-signer-only direct V2 escrow creation using SDK EscrowV2Module.create. Defaults to DisputeWindow settlementSecurity=2; SelfReport/0 is rejected. Hosted accountless SAP MCP rejects this before x402 payment; hosted users should call sap_escrow_build_create_transaction and finalize locally. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling","read_only":false},{"name":"sap_deposit_escrow_v2","title":"Deposit SAP Escrow V2","description":"Local-signer-only direct deposit into a V2 escrow. Hosted users should call sap_escrow_build_deposit_transaction and finalize locally. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value","read_only":false},{"name":"sap_settle_escrow_v2","title":"Settle SAP Escrow V2","description":"Local-signer-only direct settlement against a V2 escrow. Hosted users should call sap_escrow_build_settle_transaction and finalize locally. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid ","read_only":false},{"name":"sap_next_settlement_index","title":"Get Next Settlement Index","description":"Read the next V2 settlement index. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 na","read_only":false},{"name":"sap_finalize_settlement_v2","title":"Finalize SAP Escrow V2 Settlement","description":"Local-signer-only direct finalization of a V2 pending settlement. Hosted users should call sap_escrow_build_finalize_transaction and finalize locally. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pri","read_only":false},{"name":"sap_file_dispute_v2","title":"File SAP Escrow V2 Dispute","description":"File a dispute for a V2 pending settlement. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP. Read tools return on-chain state; write tools require signer policy, configured RPC, and the active SAP profile.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountl","read_only":false},{"name":"sap_withdraw_escrow_v2","title":"Withdraw SAP Escrow V2","description":"Local-signer-only direct withdrawal from a V2 escrow. Hosted users should call sap_escrow_build_withdraw_transaction and finalize locally. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid v","read_only":false},{"name":"sap_close_escrow_v2","title":"Close SAP Escrow V2","description":"Local-signer-only direct close for an empty V2 escrow. Hosted users should call sap_escrow_build_close_transaction and finalize locally. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid val","read_only":false},{"name":"sap_give_feedback","title":"Give SAP Feedback","description":"Create on-chain feedback for an agent wallet. SAP MCP context: Reputation and trust flow. Use after verifying the target agent PDA or wallet and keep hashes/attestation metadata stable and auditable.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: host","read_only":false},{"name":"sap_update_feedback","title":"Update SAP Feedback","description":"Update existing on-chain feedback for an agent wallet. SAP MCP context: Reputation and trust flow. Use after verifying the target agent PDA or wallet and keep hashes/attestation metadata stable and auditable.\n\nSAP MCP execution guidance: Intent: local-signer write workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: paid hosted call; call sa","read_only":false},{"name":"sap_revoke_feedback","title":"Revoke SAP Feedback","description":"Revoke feedback for an agent wallet. SAP MCP context: Reputation and trust flow. Use after verifying the target agent PDA or wallet and keep hashes/attestation metadata stable and auditable.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accoun","read_only":false},{"name":"sap_create_attestation","title":"Create SAP Attestation","description":"Create an on-chain attestation for an agent wallet. SAP MCP context: Reputation and trust flow. Use after verifying the target agent PDA or wallet and keep hashes/attestation metadata stable and auditable.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocke","read_only":false},{"name":"sap_revoke_attestation","title":"Revoke SAP Attestation","description":"Revoke attestation for an agent wallet. SAP MCP context: Reputation and trust flow. Use after verifying the target agent PDA or wallet and keep hashes/attestation metadata stable and auditable.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted acc","read_only":false},{"name":"sap_fairscale_score","title":"Get FairScale Score","description":"Score an agent with SDK FairScaleRegistry.score. SAP MCP context: Reputation and trust flow. Use after verifying the target agent PDA or wallet and keep hashes/attestation metadata stable and auditable.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: p","read_only":false},{"name":"sap_fairscale_trust_gate","title":"FairScale Trust Gate","description":"Evaluate an agent with SDK FairScaleRegistry.trustGate. SAP MCP context: Reputation and trust flow. Use after verifying the target agent PDA or wallet and keep hashes/attestation metadata stable and auditable.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Rou","read_only":false},{"name":"sap_init_vault","title":"Initialize SAP Vault","description":"Initialize a memory vault for the connected agent. SAP MCP context: Memory/session flow. Store only intentionally encrypted payloads or public hashes; session and vault PDAs are visible on-chain metadata.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing:","read_only":false},{"name":"sap_open_vault_session","title":"Open SAP Vault Session","description":"Open a vault session by 32-byte session hash. SAP MCP context: Memory/session flow. Store only intentionally encrypted payloads or public hashes; session and vault PDAs are visible on-chain metadata.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: host","read_only":false},{"name":"sap_inscribe_memory","title":"Inscribe SAP Memory","description":"Inscribe encrypted memory using SDK VaultModule.inscribe. SAP MCP context: Memory/session flow. Store only intentionally encrypted payloads or public hashes; session and vault PDAs are visible on-chain metadata.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. R","read_only":false},{"name":"sap_compact_inscribe_memory","title":"Compact Inscribe SAP Memory","description":"Compact memory inscription with explicit vault/session PDAs. SAP MCP context: Memory/session flow. Store only intentionally encrypted payloads or public hashes; session and vault PDAs are visible on-chain metadata.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively","read_only":false},{"name":"sap_session_start","title":"Start SAP Memory Session","description":"Start a high-level SDK session by session ID. SAP MCP context: Memory/session flow. Store only intentionally encrypted payloads or public hashes; session and vault PDAs are visible on-chain metadata.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid","read_only":false},{"name":"sap_session_read_latest","title":"Read Latest SAP Session Entries","description":"Read latest entries from a high-level SDK session ID. SAP MCP context: Memory/session flow. Store only intentionally encrypted payloads or public hashes; session and vault PDAs are visible on-chain metadata.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routi","read_only":false},{"name":"sap_session_status","title":"Get SAP Session Status","description":"Fetch high-level SDK session status by session ID. SAP MCP context: Memory/session flow. Store only intentionally encrypted payloads or public hashes; session and vault PDAs are visible on-chain metadata.\n\nSAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing:","read_only":false}],"server_info":{"name":"sap-mcp-server","title":"SAP MCP Server | OOBE Protocol","version":"0.9.86","description":"Solana-native MCP gateway for Synapse Agent Protocol tools, DeFi protocols, SNS identity, x402/pay.sh payments, and user-controlled agent operations.","websiteUrl":"https://mcp.sap.oobeprotocol.ai/","icons":[{"src":"https://mcp.sap.oobeprotocol.ai/favicon.png","mimeType":"image/png","sizes":["512x512"]}]},"category":"crypto","tags":["finance","security","analytics"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-07-13","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/ai-oobeprotocol-sap-mcp-sap-mcp/"}