Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SAP MCP Server

NPM · @OOBE-PROTOCOL-LABS/SAP-MCP-SERVER · 2 COMPONENTS · SCANNED SEP 21

Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments.

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects langsmith 0.3.87, reached via @langchain/core > langsmith. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 400 of 495 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 32719 tokens (~121/item across 269 items; 269 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 26 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "sap_withdraw_escrow" implies "withdraw" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 269 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the SAP MCP Server server?

SAP MCP Server runs locally as an npm package, launched with npx -y @oobe-protocol-labs/sap-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @oobe-protocol-labs/sap-mcp-server

# add to Claude Code
claude mcp add ai-oobeprotocol-sap-mcp-sap-mcp -- npx -y @oobe-protocol-labs/sap-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-oobeprotocol-sap-mcp-sap-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@oobe-protocol-labs/sap-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-oobeprotocol-sap-mcp-sap-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@oobe-protocol-labs/sap-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ai-oobeprotocol-sap-mcp-sap-mcp -- npx -y @oobe-protocol-labs/sap-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-oobeprotocol-sap-mcp-sap-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@oobe-protocol-labs/sap-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-oobeprotocol-sap-mcp-sap-mcp --command npx --arg -y --arg @oobe-protocol-labs/sap-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  ai-oobeprotocol-sap-mcp-sap-mcp:
    command: "npx"
    args: ["-y", "@oobe-protocol-labs/sap-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-oobeprotocol-sap-mcp-sap-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@oobe-protocol-labs/sap-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ai-oobeprotocol-sap-mcp-sap-mcp -t stdio -c npx -a -y @oobe-protocol-labs/sap-mcp-server
// mcp.json
{
  "mcpServers": {
    "ai-oobeprotocol-sap-mcp-sap-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@oobe-protocol-labs/sap-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 18 Sept 26 +1
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 0
    • CVE-2026-82417 no longer affects this package security
    • CVE-2026-82562 no longer affects this package security
  • 14 Sept 26 +1
    • Security disclosure: unverified → pass functional
  • 13 Sept 26 0
    • CVE-2026-63376 affects this package: high security
    • CVE-2026-71429 affects this package: high security
    • CVE-2026-77465 affects this package: high security
    • CVE-2026-82562 affects this package: high security
    • CVE-2026-41907 affects this package: high security
    • CVE-2026-82417 affects this package: high security
    • Security disclosure: pass → unverified functional
  • 12 Sept 26 −3
    • CVE-2026-77465 no longer affects this package security
    • CVE-2026-63376 no longer affects this package security
    • CVE-2026-41907 no longer affects this package security
    • CVE-2026-82417 no longer affects this package security
    • CVE-2026-82562 no longer affects this package security
    • CVE-2026-71429 no longer affects this package security
    • Stability: pass → 0.80 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/@oobe-protocol-labs/sap-mcp-server@0.7.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 9 findings
ID CVE Severity Vector Fix available
GHSA-3gc7-fjrx-p6mg CVE-2025-3194 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
GHSA-3644-q5cj-c5c7 CVE-2026-45134 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N yes
GHSA-fw9q-39r9-c252 CVE-2026-40190 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L yes
GHSA-rr7j-v2q5-chgv CVE-2026-41182 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-v34v-rq6j-cj6p CVE-2026-25528 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N yes
GHSA-528h-pc64-c93x CVE-2026-71429 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-82x6-q7mm-w9cf CVE-2026-77465 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-v5mp-jgw5-2x6j CVE-2026-63376 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 400 packages
Packages resolved 400
Deprecated 3
Stale 100
No linked repository 6
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools · 269 exposed · ~32,719 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
sap_deposit_escrow ~85

Deposit funds into a V1 escrow. 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.

NameTypeReqDescription
agentWalletstringAgent wallet public key (base58)
amountstringDeposit amount in lamports (as a decimal string)

No output schema declared.

No examples provided.

sap_deposit_escrow_v2 ~107

Deposit funds into a V2 escrow. 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.

NameTypeReqDescription
agentWalletstringAgent wallet public key (base58)
amountstringDeposit amount in lamports (as a decimal string)
noncestringEscrow nonce (as a decimal string, default: 0)

No output schema declared.

No examples provided.

sap_deposit_stake ~86

Deposit additional stake for an agent wallet. SAP MCP context: SAP protocol staking flow. Confirm agent wallet, amount, and unstake timing before writes; this is distinct from external AgentKit staking protocol tools.

NameTypeReqDescription
agentWalletstringAgent wallet public key (base58)
amountstringAdditional stake deposit amount in lamports (as a decimal string)

No output schema declared.

No examples provided.

sap_discover_agents ~182

Discover agents by protocol, capability, or capability list. Unfiltered global listing is not exposed by SDK v0.20. 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.

NameTypeReqDescription
capabilitiesarrayArray of capability IDs to filter agents by (requires at least one)
capabilitystringSingle capability ID to filter agents by (e.g. "jupiter:swap")
hydratebooleanWhether to include full hydrated agent profiles in results (default: true)
limitnumberMaximum number of agents to return (default: 50)
protocolstringProtocol identifier to filter agents by (e.g. "jupiter", "drift")

No output schema declared.

No examples provided.

sap_fairscale_score ~101

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.

NameTypeReqDescription
agentstringAgent PDA or wallet (base58) to score
taskstringOptional FairScale task type: one of "defi_execution", "trust_focused", "work_focused", "hiring"

No output schema declared.

No examples provided.

sap_fairscale_trust_gate ~106

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.

NameTypeReqDescription
agentstringAgent PDA or wallet (base58) to evaluate
minScorenumberOptional minimum trust score threshold
requireVerificationbooleanWhether verified status is required to pass the gate (default: false)

No output schema declared.

No examples provided.

sap_fetch_attestation ~107

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.

NameTypeReqDescription
agentPdastringAgent PDA (base58) to fetch attestation for
attesterstringOptional attester wallet (base58) to filter attestation by

No output schema declared.

No examples provided.

sap_fetch_capability_index ~86

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.

NameTypeReqDescription
capabilityIdstringCapability ID to fetch the index for (e.g. "jupiter:swap")

No output schema declared.

No examples provided.

sap_fetch_dispute ~77

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.

NameTypeReqDescription
disputePdastringDispute PDA (base58) to fetch

No output schema declared.

No examples provided.

sap_fetch_epoch_page ~97

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.

NameTypeReqDescription
epochIndexnumberZero-based epoch index to fetch
sessionPdastringSession PDA (base58) to fetch epoch page for

No output schema declared.

No examples provided.

sap_fetch_escrow ~132

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.

NameTypeReqDescription
agentPdastringAgent PDA (base58) — used when escrowPda is omitted
depositorstringOptional depositor wallet (base58) to filter by
escrowPdastringEscrow PDA (base58) to fetch directly

No output schema declared.

No examples provided.

sap_fetch_escrow_v2 ~163

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.

NameTypeReqDescription
agentPdastringAgent PDA (base58) — used when escrowPda is omitted
depositorstringOptional depositor wallet (base58) to filter by
escrowPdastringEscrow V2 PDA (base58) to fetch directly
noncenumberEscrow nonce (default: 0) — used with agentPda and depositor

No output schema declared.

No examples provided.

sap_fetch_feedback ~100

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.

NameTypeReqDescription
agentPdastringAgent PDA (base58) to fetch feedback for
reviewerstringOptional reviewer wallet (base58) to filter feedback by

No output schema declared.

No examples provided.

sap_fetch_pending_settlement ~79

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.

NameTypeReqDescription
pendingPdastringPending settlement PDA (base58) to fetch

No output schema declared.

No examples provided.

sap_fetch_protocol_index ~87

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.

NameTypeReqDescription
protocolIdstringProtocol ID to fetch the index for (e.g. "jupiter", "drift")

No output schema declared.

No examples provided.

sap_fetch_session ~79

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.

NameTypeReqDescription
sessionPdastringSession PDA (base58) to fetch the ledger for

No output schema declared.

No examples provided.

sap_fetch_stake ~103

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.

NameTypeReqDescription
agentPdastringAgent PDA (base58) — used when stakePda is omitted
stakePdastringStake PDA (base58) to fetch directly

No output schema declared.

No examples provided.

sap_fetch_subscription ~147

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.

NameTypeReqDescription
agentPdastringAgent PDA (base58) — used when subscriptionPda is omitted
subIdnumberSubscription ID (default: 0) — used with agentPda and subscriber
subscriberstringOptional subscriber wallet (base58) to filter by
subscriptionPdastringSubscription PDA (base58) to fetch directly

No output schema declared.

No examples provided.

sap_fetch_tool ~97

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.

NameTypeReqDescription
agentPdastringAgent PDA (base58) that owns the tool descriptor
toolNamestringName of the tool descriptor to fetch

No output schema declared.

No examples provided.

sap_fetch_tool_category_index ~79

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.

NameTypeReqDescription
categorynumberNumeric tool category ID to fetch the index for

No output schema declared.

No examples provided.

sap_fetch_vault ~81

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.

NameTypeReqDescription
agentPdastringAgent PDA (base58) to fetch the memory vault for

No output schema declared.

No examples provided.

sap_file_dispute_v2 ~151

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.

NameTypeReqDescription
agentWalletstringAgent wallet public key (base58)
disputeTypenumberOptional dispute type identifier (numeric)
evidenceHasharray32-byte evidence hash as a byte array, hex string, or base64 string
noncestringEscrow nonce (as a decimal string, default: 0)
settlementIndexstringSettlement index to dispute (as a decimal string)

No output schema declared.

No examples provided.

sap_finalize_settlement_v2 ~122

Finalize a V2 pending settlement. 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.

NameTypeReqDescription
agentWalletstringAgent wallet public key (base58)
depositorWalletstringDepositor wallet public key (base58)
noncestringEscrow nonce (as a decimal string, default: 0)
settlementIndexstringSettlement index to finalize (as a decimal string)

No output schema declared.

No examples provided.

sap_find_tools_by_category ~133

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.

NameTypeReqDescription
categorystring|numberTool category name (e.g. "defi", "infrastructure") or numeric category ID
hydratebooleanWhether to include full hydrated tool descriptors in results (default: true)
limitnumberMaximum number of tools to return (default: 50)

No output schema declared.

No examples provided.

sap_fund_subscription ~100

Fund a recurring subscription. 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.

NameTypeReqDescription
agentWalletstringAgent wallet public key (base58)
amountstringFunding amount in lamports (as a decimal string)
subIdstringSubscription ID (as a decimal string, default: 0)

No output schema declared.

No examples provided.

sap_get_agent ~95

Fetch agent identity by owner wallet. If omitted, fetches the connected wallet agent. 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.

NameTypeReqDescription
walletstringSolana public key of the agent owner wallet (base58). If omitted, uses the connected wallet.

No output schema declared.

No examples provided.

sap_get_agent_profile ~81

Fetch a hydrated SAP agent profile by owner 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.

NameTypeReqDescription
walletstringSolana public key of the agent owner wallet (base58)

No output schema declared.

No examples provided.

sap_get_agent_stats ~78

Fetch agent stats 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.

NameTypeReqDescription
agentPdastringAgent PDA (base58) to fetch stats for

No output schema declared.

No examples provided.

sap_get_global_state ~66

Fetch the on-chain global registry through SDK AgentModule.fetchGlobalRegistry. 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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sap_get_network_overview ~65

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sap_get_tool_category_summary ~62

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sap_give_feedback ~130

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.

NameTypeReqDescription
agentWalletstringAgent wallet public key (base58) to give feedback for
commentHasharrayOptional 32-byte comment hash as a byte array, hex string, or base64 string
scorenumberFeedback score (numeric, e.g. 1–5)
tagstringOptional feedback tag/category (default: "general")

No output schema declared.

No examples provided.

sap_init_stake ~90

Initialize stake for an agent wallet. SAP MCP context: SAP protocol staking flow. Confirm agent wallet, amount, and unstake timing before writes; this is distinct from external AgentKit staking protocol tools.

NameTypeReqDescription
agentWalletstringAgent wallet public key (base58) to initialize stake for
initialDepositstringInitial stake deposit amount in lamports (as a decimal string)

No output schema declared.

No examples provided.

sap_init_vault ~70

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.

NameTypeReqDescription
vaultNoncearrayVault nonce as a byte array, hex string, or base64 string

No output schema declared.

No examples provided.

sap_inscribe_memory ~50

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sap_is_agent_active ~86

Check if a wallet owns an active SAP agent. 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.

NameTypeReqDescription
walletstringSolana public key of the wallet to check for an active SAP agent (base58)

No output schema declared.

No examples provided.

sap_list_agents ~182

Compatibility alias for filtered SAP agent discovery. Requires protocol or capability. Use sap_list_all_agents for a global on-chain directory snapshot. 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.

NameTypeReqDescription
capabilitiesarrayArray of capability IDs to filter agents by (requires at least one)
capabilitystringSingle capability ID to filter agents by (e.g. "jupiter:swap")
hydratebooleanWhether to include full hydrated agent profiles in results (default: true)
limitnumberMaximum number of agents to return (default: 50)
protocolstringProtocol identifier to filter agents by (e.g. "jupiter", "drift")

No output schema declared.

No examples provided.

sap_list_all_agents ~195

Enumerate SAP AgentAccount PDAs directly from the on-chain program account set. Use this for current global directory requests such as "list all agents in the SAP ecosystem rn". 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.

NameTypeReqDescription
capabilitystringOptional capability ID filter such as jupiter:swap.
includeInactivebooleanInclude inactive agents. Defaults to false.
includeProtocolIndexesbooleanInclude compact protocol index summaries. Defaults to true.
limitnumberMaximum rows to return. Defaults to 100; hard-capped at 500.
offsetnumberZero-based pagination offset. Defaults to 0.
protocolstringOptional protocol filter matched against agent profile protocols and protocol-index membership.

No output schema declared.

No examples provided.

sap_network_stats ~42

Fetch real SAP network statistics using synapse-sap-sdk DiscoveryRegistry and GlobalRegistry.

NameTypeReqDescription
detailedbooleanInclude both discovery overview and raw global registry state.

No output schema declared.

No examples provided.

sap_next_settlement_index ~104

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.

NameTypeReqDescription
agentWalletstringAgent wallet public key (base58)
depositorWalletstringDepositor wallet public key (base58)
noncestringEscrow nonce (as a decimal string, default: 0)

No output schema declared.

No examples provided.

sap_open_vault_session ~76

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.

NameTypeReqDescription
sessionHasharray32-byte session hash as a byte array, hex string, or base64 string

No output schema declared.

No examples provided.

sap_preview_transaction ~37

Preview a Solana transaction before signing or submission.

NameTypeReqDescription
encodingstringInput encoding
transactionstringSerialized transaction

No output schema declared.

No examples provided.

sap_profile_current ~23

Return the currently loaded SAP MCP profile and redacted signer/config metadata.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sap_profile_list ~24

List available SAP MCP profiles with redacted signer metadata and no wallet paths.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sap_profile_public_key ~43

Return the configured public agent key for a profile without reading or exposing keypair bytes.

NameTypeReqDescription
profileNamestringProfile name. Defaults to the loaded profile.

No output schema declared.

No examples provided.

sap_profile_switch ~64

Switch the live SAP MCP runtime to another existing profile and reload client, signer, connection, and policy.

NameTypeReqDescription
confirmbooleanMust be true because switching profile can change signer, network, and policy.
profileNamestringExisting profile name to load.

No output schema declared.

No examples provided.

sap_publish_tool_by_name ~243

Publish a tool descriptor using SDK ToolsModule.publishByName. SAP MCP context: Use tool registry writes to advertise concrete capabilities that this MCP can serve, including AgentKit bridge tools such as bridging_bridgeWormhole and Metaplex tools such as metaplex-nft_mintNFT. Publish only schemas and descriptions that match the actual MCP tool surface.

NameTypeReqDescription
categorynumberNumeric tool category ID
descriptionstringHuman-readable description of the tool
httpMethodnumberHTTP method code (e.g. 0=GET, 1=POST)
inputSchemaJsonstringJSON string of the tool input schema
isCompoundbooleanWhether the tool is a compound tool (default: false)
outputSchemaJsonstringJSON string of the tool output schema
paramsCountnumberTotal number of parameters the tool accepts
protocolIdstringProtocol ID the tool belongs to (e.g. "jupiter")
requiredParamsnumberNumber of required parameters
toolNamestringName of the tool to publish

No output schema declared.

No examples provided.

sap_reactivate_agent ~56

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sap_reactivate_tool ~73

Reactivate a SAP tool descriptor by name. 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.

NameTypeReqDescription
toolNamestringName of the tool descriptor to reactivate

No output schema declared.

No examples provided.

sap_register_agent ~286

Register the connected wallet as a SAP agent using SDK AgentModule.register. SAP MCP context: This is the primary on-chain SAP agent registration tool for the connected profile signer. Use agentUri or metadataUri for off-chain metadata, including a Metaplex or DAS-backed identity document when the agent also has NFT/collection metadata. After registration, use sap_publish_tool_by_name for advertised MCP capabilities and AgentKit metaplex-nft_* tools for NFT collection, badge, or metadata workflows.

NameTypeReqDescription
agentIdstringOptional unique agent identifier string
agentUristringOptional URI to the agent's off-chain metadata or service endpoint
capabilitiesarrayArray of capability objects or strings identifying what the agent can do (e.g. "jupiter:swap")
descriptionstringDetailed description of the agent's purpose and capabilities
metadataUristringAlias for agentUri — URI to off-chain agent metadata JSON
namestringHuman-readable name for the SAP agent
pricingarrayArray of pricing tier objects defining per-call costs, rate limits, and settlement terms
protocolsarrayArray of protocol identifiers the agent supports (e.g. "jupiter", "drift")
x402EndpointstringOptional x402 payment endpoint URL for HTTP-based agent payments

No output schema declared.

No examples provided.

Common questions

What is the SAP MCP Server server?

SAP MCP Server is listed in the public MCP registry as ai.oobeprotocol.sap.mcp/sap-mcp. Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments. This page covers its npm package (@oobe-protocol-labs/sap-mcp-server).

Is the SAP MCP Server server safe to use?

SAP MCP Server scores 79 out of 100 on VerifyMCP. We recorded 9 known advisories against it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SAP MCP Server server expose?

SAP MCP Server exposes 269 tools: sap_register_agent, sap_update_agent, sap_deactivate_agent, sap_reactivate_agent, sap_close_agent, and 264 more. Their descriptions and schemas cost roughly 32,719 tokens of context every time the server is loaded.

Is the SAP MCP Server server still maintained?

SAP MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the SAP MCP Server server under?

SAP MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.