SAP MCP Server
NPM · @OOBE-PROTOCOL-LABS/SAP-MCP-SERVER · 2 COMPONENTS
Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments.
Available components
Last scanned (6 hours ago)
Scores higher than 55% of npm servers
Category Crypto and Web3
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 Security76
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 400 of 907 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 45 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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.
- 1 Nov 26 +1
- Security disclosure: unverified → pass ▲ functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- CVE-2026-114142 affects this package: high ▼ security
- 24 Oct 26 −1
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
- Stability: 0.97 → pass security
- 23 Oct 26 0
- CVE-2026-114141 affects this package: high ▼ security
- CVE-2026-114144 affects this package: high ▼ security
- CVE-2026-114143 affects this package: high ▼ security
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 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 15 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| 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-hqr4-qq8f-hg3x | CVE-2026-104182 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-mjw6-4jj6-33hc | CVE-2026-104183 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L | yes |
| GHSA-4qx8-w7c3-pj3p | CVE-2026-114141 | high | 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-9j65-hcg3-gc64 | CVE-2026-114143 | high | yes | |
| GHSA-9qmh-m7c6-f92p | CVE-2026-114144 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-h895-cgqg-jf52 | CVE-2026-114142 | high | 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 |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 400 packages
| Packages resolved | 400 |
|---|---|
| Deprecated | 2 |
| Stale | 92 |
| 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 →
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 →
sap_report_calls ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| callsServed | number | – | Number of calls served to report for the agent |
No output schema declared.
No examples provided.
sap_report_tool_invocations ~90
Report invocation count for a SAP tool descriptor. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| invocations | number | – | Number of invocations to report |
| toolName | string | – | Name of the tool descriptor to report invocations for |
No output schema declared.
No examples provided.
sap_request_unstake ~85
Request unstake 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) |
| amount | string | – | Unstake request amount in lamports (as a decimal string) |
No output schema declared.
No examples provided.
sap_revoke_attestation ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) to revoke attestation for |
No output schema declared.
No examples provided.
sap_revoke_feedback ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) to revoke feedback for |
No output schema declared.
No examples provided.
sap_session_read_latest ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | – | High-level session identifier string to read latest entries from |
No output schema declared.
No examples provided.
sap_session_start ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | – | High-level session identifier string |
| vaultNonce | array | – | Optional vault nonce as a byte array, hex string, or base64 string |
No output schema declared.
No examples provided.
sap_session_status ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | – | High-level session identifier string to get status for |
No output schema declared.
No examples provided.
sap_settle_escrow ~116
Settle calls against 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.
| Name | Type | Req | Description |
|---|---|---|---|
| callsToSettle | string | – | Number of calls to settle (as a decimal string) |
| depositorWallet | string | – | Depositor wallet public key (base58) |
| serviceHash | array | – | 32-byte service hash as a byte array, hex string, or base64 string |
No output schema declared.
No examples provided.
sap_settle_escrow_batch ~124
Batch settle V1 escrow entries using SDK EscrowModule.settleBatch. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| batchRoot | array | – | Optional 32-byte Merkle root for batch verification |
| depositorWallet | string | – | Depositor wallet public key (base58) |
| settlements | array | – | Array of settlement objects, each containing callsToSettle (string) and serviceHash (32-byte array) |
No output schema declared.
No examples provided.
sap_settle_escrow_v2 ~138
Settle calls against 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.
| Name | Type | Req | Description |
|---|---|---|---|
| callsToSettle | string | – | Number of calls to settle (as a decimal string) |
| depositorWallet | string | – | Depositor wallet public key (base58) |
| nonce | string | – | Escrow nonce (as a decimal string, default: 0) |
| serviceHash | array | – | 32-byte service hash as a byte array, hex string, or base64 string |
No output schema declared.
No examples provided.
sap_sign_transaction ~44
Sign a serialized Solana transaction with the configured SAP MCP signer.
| Name | Type | Req | Description |
|---|---|---|---|
| encoding | string | – | Input encoding |
| transaction | string | – | Unsigned or partially signed transaction |
No output schema declared.
No examples provided.
sap_skills_bundle ~42
Return bundled SAP MCP skills as JSON so an agent can load or write them itself.
| Name | Type | Req | Description |
|---|---|---|---|
| includeContents | boolean | – | – |
| skills | array | – | – |
No output schema declared.
No examples provided.
sap_skills_install ~56
Install bundled SAP MCP skills into a local agent skill directory. Requires confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | – |
| confirm | boolean | – | – |
| skills | array | – | – |
| targetDir | string | – | – |
No output schema declared.
No examples provided.
sap_skills_list ~26
List bundled SAP MCP skills and their files.
| Name | Type | Req | Description |
|---|---|---|---|
| skills | array | – | – |
No output schema declared.
No examples provided.
sap_sns_batch_check_domains ~56
Check availability for multiple .sol domains (up to 25) using the SAP SDK SnsModule.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | – | Array of .sol domain names to batch-check for availability (1-25 domains) |
No output schema declared.
No examples provided.
sap_sns_build_manage_record_transaction ~167
Build an unsigned SNS record create/update/delete transaction using the Bonfida SDK. The returned transaction must be signed with sap_sign_transaction before submission. Use null value to delete a record. Note: SOL record is not supported — it requires a separate Ed25519 signature flow.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The .sol domain name whose record should be created, updated, or deleted |
| owner | string | – | The Solana public key (base58) of the domain owner authorizing the record change |
| recordType | string | – | The SNS record type to manage (e.g. TXT, Url, IPFS, ETH, BTC, etc.) |
| value | string|null | – | The new record value as a string, or null to delete the record |
No output schema declared.
No examples provided.
sap_sns_build_set_primary_domain_transaction ~92
Build an unsigned transaction to set a .sol domain as primary for the owner using the Bonfida SDK. The returned transaction must be signed with sap_sign_transaction before submission.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The .sol domain name to set as primary for the owner |
| owner | string | – | The Solana public key (base58) of the domain owner setting their primary domain |
No output schema declared.
No examples provided.
sap_sns_check_domain ~52
Check whether a .sol domain is available for registration using the SAP SDK SnsModule.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The .sol domain name to check for availability (with or without .sol suffix) |
No output schema declared.
No examples provided.
sap_sns_check_ownership ~69
Check whether a wallet owns a .sol domain using the Bonfida SDK.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The .sol domain name to check ownership of |
| owner | string | – | The Solana public key (base58) of the wallet to verify as the domain owner |
No output schema declared.
No examples provided.
sap_sns_get_domain_pda ~51
Derive the SNS domain PDA for a .sol domain using the SAP SDK SnsModule.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The .sol domain name to derive the SNS domain PDA for |
No output schema declared.
No examples provided.
sap_sns_get_domain_records ~57
Fetch all configured SNS records for a .sol domain using the Bonfida SDK. Returns a key-value map of all records.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The .sol domain name to fetch all configured SNS records for |
No output schema declared.
No examples provided.
sap_sns_get_record ~78
Fetch a single SNS record value for a .sol domain using the Bonfida SDK.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The .sol domain name to fetch a record from |
| recordType | string | – | The SNS record type to fetch (e.g. SOL, TXT, Url, IPFS, ETH, BTC, etc.) |
No output schema declared.
No examples provided.
sap_sns_get_record_pda ~86
Derive the SNS record PDA for a domain and record type using the SAP SDK SnsModule.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The .sol domain name to derive the record PDA for |
| recordType | string | – | The SNS record type for the PDA derivation (e.g. SOL, TXT, Url, IPFS, ETH, BTC, etc.) |
No output schema declared.
No examples provided.
sap_sns_register_agent_domain ~340
Register a .sol domain for the configured local SAP agent wallet using the SAP SDK SnsModule. Builds, signs, and submits the full registration transaction with USDC payment in one call. Domain registration fees are paid in USDC plus SOL for rent and transaction fees. The SOL record is NOT set during registration (it requires a separate Ed25519 signature) — set it after using sap_sns_build_manage_record_transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | The Solana public key (base58) of the SAP agent wallet that will own the domain |
| capabilities | array | – | Optional list of SAP capability IDs to advertise in the domain TXT record |
| domain | string | – | The .sol domain name to register for the SAP agent (with or without .sol suffix) |
| durationYears | number | – | Registration duration in years (default: 1) |
| pic | string | – | Profile picture URL for the SNS Pic record (required if not provided in records.Pic) |
| protocols | array | – | Optional list of protocol IDs the agent supports |
| records | object | – | Optional map of SNS record key-value pairs to set during registration (e.g. { "Url": "https://...", "Twitter": "@handle" }). Note: SOL record is skipped during registration. |
| sapData | object | – | Optional structured SAP metadata to embed in the domain TXT record (capabilities, protocols, endpoints, etc.) |
| setAsPrimary | boolean | – | Whether to set this domain as the agent primary .sol domain |
| space | number | – | Storage space in bytes for the domain name account (default: 600) |
No output schema declared.
No examples provided.
sap_sns_resolve_domain ~58
Resolve a .sol domain to SAP agent identity, wallet, metadata, and SNS records using the SAP SDK SnsModule.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The .sol domain name to resolve to SAP agent identity and SNS records |
No output schema declared.
No examples provided.
sap_sns_resolve_wallet ~50
Resolve a .sol domain to its owner wallet public key using the Bonfida SDK.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The .sol domain name to resolve to its owner wallet public key |
No output schema declared.
No examples provided.
sap_sns_validate_records ~51
Validate SNS records for SAP agent compatibility (checks SOL, Pic, TXT records on-chain).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The .sol domain name whose SNS records should be validated for SAP agent compatibility |
No output schema declared.
No examples provided.
sap_submit_signed_transaction ~68
Submit a signed Solana transaction through the configured RPC endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| encoding | string | – | Input encoding |
| maxRetries | number | – | Maximum RPC send retries |
| signedTransaction | string | – | Signed serialized transaction |
| skipPreflight | boolean | – | Skip RPC preflight checks |
No output schema declared.
No examples provided.
sap_update_agent ~81
Update the connected wallet SAP agent using SDK AgentModule.update. SAP MCP context: Use this after sap_register_agent to refresh name, description, capabilities, pricing, supported protocols, x402 endpoint, or metadataUri. For NFT-backed identity changes, update the Metaplex asset first when needed, then point the SAP agent metadataUri at the current metadata document.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sap_update_feedback ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) to update feedback for |
| commentHash | array | – | Optional 32-byte comment hash as a byte array, hex string, or base64 string |
| score | number | – | New feedback score (numeric, e.g. 1–5) |
| tag | string | – | Optional new feedback tag/category |
No output schema declared.
No examples provided.
sap_update_reputation_metrics ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| avgLatencyMs | number | – | Average response latency in milliseconds to report |
| uptimePercent | number | – | Uptime percentage (0–100) to report for the agent |
No output schema declared.
No examples provided.
sap_update_tool ~78
Update tool descriptor hashes using SDK ToolsModule.update. 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sap_withdraw_escrow ~85
Withdraw funds from 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) |
| amount | string | – | Withdrawal amount in lamports (as a decimal string) |
No output schema declared.
No examples provided.
sap_withdraw_escrow_v2 ~107
Withdraw funds from 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) |
| amount | string | – | Withdrawal amount in lamports (as a decimal string) |
| nonce | string | – | Escrow nonce (as a decimal string, default: 0) |
No output schema declared.
No examples provided.
sap_x402_build_headers_from_escrow ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) |
| network | string | – | Optional network identifier for X-Payment-Network |
No output schema declared.
No examples provided.
sap_x402_build_payment_headers ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentPda | string | – | Agent PDA (base58) |
| agentWallet | string | – | Agent wallet public key (base58) |
| depositorWallet | string | – | Depositor wallet public key (base58) |
| escrowPda | string | – | Escrow PDA (base58) |
| maxCalls | string | – | Max calls as a decimal string |
| network | string | – | Optional override for X-Payment-Network |
| networkIdentifier | string | – | x402 network identifier stored in the payment context |
| pricePerCall | string | – | Price per call in token base units |
| txSignature | string | – | Escrow creation transaction signature |
No output schema declared.
No examples provided.
sap_x402_calculate_cost ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| basePrice | string | – | Base price per call in token base units |
| calls | number | – | Number of calls to calculate |
| totalCallsBefore | number | – | Cumulative settled calls before this calculation (default: 0) |
| volumeCurve | array | – | Array of { afterCalls, pricePerCall } pricing breakpoints |
No output schema declared.
No examples provided.
sap_x402_estimate_cost ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) |
| calls | number | – | Number of calls to estimate |
| pricePerCall | string | – | Optional base price per call override in token base units |
| totalCallsBefore | number | – | Optional cumulative settled calls before this estimate |
| volumeCurve | array | – | Optional array of { afterCalls, pricePerCall } pricing breakpoints |
No output schema declared.
No examples provided.
sap_x402_fetch_escrow ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) |
| depositor | string | – | Optional depositor wallet (base58); defaults to caller in SDK |
No output schema declared.
No examples provided.
sap_x402_get_balance ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) |
| depositor | string | – | Optional depositor wallet (base58) to filter balance by |
No output schema declared.
No examples provided.
sap_x402_has_escrow ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) |
| depositor | string | – | Optional depositor wallet (base58); defaults to caller in SDK |
No output schema declared.
No examples provided.
sap_x402_paid_call ~274
Local helper that initializes the hosted MCP session, signs an x402 payment with the user SAP MCP profile wallet, retries the remote tool call, and returns the settlement receipt. Use this instead of calling hosted paid tools directly when the runtime cannot attach x402 payment headers. Requires confirm: true and maxPriceUsd.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | Arguments for the remote tools/call request. |
| body | object | – | Optional full JSON-RPC request body. Use this instead of toolName when the caller already has a complete request. |
| confirm | boolean | – | Must be true. Confirms the user allows this helper to sign an x402 payment payload. |
| endpoint | string | – | Hosted MCP endpoint. Defaults to https://mcp.sap.oobeprotocol.ai/mcp. |
| maxAttempts | number | – | Optional retry count for transient x402/RPC failures such as BlockhashNotFound. Defaults to 3; max 5. |
| maxPriceUsd | number | – | Maximum accepted x402 payment amount in USD. The call aborts if the challenge exceeds this cap. |
| profileName | string | – | SAP MCP profile used to sign the x402 payment. Defaults to the active profile. |
| toolName | string | – | Remote hosted SAP MCP tool name to call, for example sap_list_all_agents. |
No output schema declared.
No examples provided.
sap_x402_prepare_payment ~218
Prepare a V1 x402 payment context using SDK X402Registry.preparePayment. Deprecated by the SDK for production escrow creation; prefer Escrow V2 tools for new 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentWallet | string | – | Agent wallet public key (base58) |
| deposit | string | – | Initial deposit amount as a decimal string |
| expiresAt | string | – | Optional expiry timestamp in unix seconds |
| maxCalls | string | – | Optional maximum number of calls covered |
| networkIdentifier | string | – | Optional x402 network identifier written into headers |
| pricePerCall | string | – | Price per call as a decimal string |
| tokenDecimals | number | – | Optional token decimals |
| tokenMint | string | – | Optional SPL token mint; omit/null for SOL |
| volumeCurve | array | – | Optional array of { afterCalls, pricePerCall } pricing breakpoints |
No output schema declared.
No examples provided.
sap_x402_settle ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| callsToSettle | number | – | Number of calls to settle |
| commitment | string | – | Optional processed|confirmed|finalized commitment |
| computeUnits | number | – | Optional compute-unit limit |
| depositorWallet | string | – | Depositor wallet public key (base58) |
| maxRetries | number | – | Optional RPC retry limit |
| priorityFeeMicroLamports | number | – | Optional priority fee in microlamports per compute unit |
| serviceData | string | – | Service data to hash into the settlement proof |
| skipPreflight | boolean | – | Optional skip preflight flag |
No output schema declared.
No examples provided.
sap_x402_settle_batch ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| commitment | string | – | Optional processed|confirmed|finalized commitment |
| computeUnits | number | – | Optional compute-unit limit |
| depositorWallet | string | – | Depositor wallet public key (base58) |
| entries | array | – | Array of { calls, serviceData } settlement entries |
| maxRetries | number | – | Optional RPC retry limit |
| priorityFeeMicroLamports | number | – | Optional priority fee in microlamports per compute unit |
| skipPreflight | boolean | – | Optional skip preflight flag |
No output schema declared.
No examples provided.
send-arcade_listGames ~80
List available games on Send Arcade. SAP MCP context: Protocol send-arcade; operation class write. Use for Send Arcade game listing and play flows. Confirm account, wager or spend, and game rules before writes. Keep gaming activity separate from SAP identity unless it is intentionally part of an agent profile.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
No output schema declared.
No examples provided.
send-arcade_playGame ~119
Enter and play a game on Send Arcade (pays entry fee via transaction). SAP MCP context: Protocol send-arcade; operation class write. Use for Send Arcade game listing and play flows. Confirm account, wager or spend, and game rules before writes. Keep gaming activity separate from SAP identity unless it is intentionally part of an agent profile.
| Name | Type | Req | Description |
|---|---|---|---|
| betAmount | string | – | Raw token amount (smallest unit) |
| gameId | string | yes | – |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
sns_resolveDomain ~83
Resolve a .sol domain to its owner wallet address. SAP MCP context: Protocol sns; operation class read. Use to resolve a .sol domain through AgentKit SNS helpers. For SAP-linked domains, prefer sap_sns_resolve_domain because it returns SAP MCP-shaped context.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Full domain name (e.g. "myname.sol") |
No output schema declared.
No examples provided.
sns_reverseLookup ~78
Reverse-lookup all .sol domains owned by a wallet. SAP MCP context: Protocol sns; operation class read. Use to find the SNS domain associated with a wallet. For SAP profile checks, pair this with sap_sns_resolve_wallet or sap_sns_check_ownership.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | Wallet address to reverse-lookup |
No output schema declared.
No examples provided.
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
claude mcp add ai-oobeprotocol-sap-mcp-sap-mcp -- npx -y @oobe-protocol-labs/sap-mcp-server
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 77 out of 100 on VerifyMCP. We recorded 15 known advisories against it as of 5 November 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 5 November 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.