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 (7 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 →
sol_get_balance ~62
Fetch the SOL balance for a wallet or account using the configured Solana RPC endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Wallet or account public key in base58 |
| commitment | string | – | Optional commitment override |
| pubkey | string | – | Alias for address |
No output schema declared.
No examples provided.
spl-token_burn ~119
Burn SPL tokens from the owner's token account. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to burn |
| mint | string | yes | Token mint address (base58) |
| owner | string | yes | Token account owner |
No output schema declared.
No examples provided.
spl-token_closeAccount ~122
Close a token account and reclaim the rent SOL. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Token account to close |
| destination | string | – | Solana public key (base58) |
| owner | string | yes | Token account owner |
No output schema declared.
No examples provided.
spl-token_deployToken ~263
Deploy a new SPL token with Metaplex metadata. Returns the mint address and an unsigned transaction. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| decimals | number | – | Token decimals (default: 9) |
| freezeAuthority | string | – | Solana public key (base58) |
| initialSupply | string | – | Raw token amount (smallest unit, no decimals) |
| isMutable | boolean | – | Whether metadata is mutable (default: true) |
| mintAuthority | string | – | Solana public key (base58) |
| name | string | yes | Token name (stored in Metaplex metadata) |
| owner | string | yes | Token owner / mint authority wallet |
| sellerFeeBasisPoints | number | – | Royalty fee in bps (for fungible with metadata) |
| symbol | string | yes | Token symbol (e.g. "MYTKN") |
| uri | string | – | URI to off-chain metadata JSON (image, description, etc.) |
No output schema declared.
No examples provided.
spl-token_freezeAccount ~127
Freeze a token account (prevents all transfers). Requires freeze authority. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Token account to freeze |
| freezeAuthority | string | yes | Freeze authority wallet |
| mint | string | yes | Token mint address (base58) |
No output schema declared.
No examples provided.
spl-token_getBalance ~120
Get token or SOL balance for a wallet. If mint is omitted, returns native SOL balance. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | – | Token mint address (base58) |
| wallet | string | yes | Wallet address to check |
No output schema declared.
No examples provided.
spl-token_getTokenAccounts ~119
List all SPL token accounts for a wallet with balances and metadata. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| showZeroBalance | boolean | – | Include zero-balance accounts |
| wallet | string | yes | Wallet to query all token accounts for |
No output schema declared.
No examples provided.
spl-token_mintTo ~138
Mint additional tokens to a destination wallet (requires mint authority). SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to mint (raw, smallest unit) |
| destination | string | yes | Wallet to receive minted tokens |
| mint | string | yes | Token mint address |
| mintAuthority | string | yes | Mint authority wallet |
No output schema declared.
No examples provided.
spl-token_rugCheck ~108
Check a token for potential rug pull risks: mint/freeze authority, holder concentration, liquidity. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | Token mint to analyze |
No output schema declared.
No examples provided.
spl-token_thawAccount ~125
Thaw (unfreeze) a previously frozen token account. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Token account to thaw |
| freezeAuthority | string | yes | Freeze authority wallet |
| mint | string | yes | Token mint address (base58) |
No output schema declared.
No examples provided.
spl-token_transfer ~165
Transfer SPL tokens between wallets. Optionally creates the recipient ATA. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to transfer (raw, smallest unit) |
| createAta | boolean | – | Create recipient ATA if needed (default: true) |
| from | string | yes | Sender wallet address |
| memo | string | – | Optional memo to attach to the transaction |
| mint | string | yes | Token mint address |
| to | string | yes | Recipient wallet address |
No output schema declared.
No examples provided.
spl-token_transferSol ~143
Transfer native SOL between wallets via SystemProgram.transfer. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount in lamports (1 SOL = 1_000_000_000 lamports) |
| from | string | yes | Sender wallet address |
| memo | string | – | Optional memo to attach |
| to | string | yes | Recipient wallet address |
No output schema declared.
No examples provided.
staking_getStakeAccounts ~93
List all stake accounts for a wallet with delegation status. SAP MCP context: Protocol staking; operation class write. Use for SOL and liquid staking flows. Confirm validator or provider, amount, lockup/unstake terms, and account ownership before writes. Use SAP staking tools for SAP protocol stake accounts; use AgentKit staking tools for external staking protocols.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | Wallet to query stake accounts for |
No output schema declared.
No examples provided.
staking_stakeJupSOL ~121
Stake SOL for jupSOL (Jupiter liquid staking). Instant liquidity, auto-compounding. SAP MCP context: Protocol staking; operation class write. Use for SOL and liquid staking flows. Confirm validator or provider, amount, lockup/unstake terms, and account ownership before writes. Use SAP staking tools for SAP protocol stake accounts; use AgentKit staking tools for external staking protocols.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount in lamports to stake for jupSOL |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
staking_stakeSOL ~121
Stake native SOL to a validator. Creates a stake account and delegates. SAP MCP context: Protocol staking; operation class write. Use for SOL and liquid staking flows. Confirm validator or provider, amount, lockup/unstake terms, and account ownership before writes. Use SAP staking tools for SAP protocol stake accounts; use AgentKit staking tools for external staking protocols.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount in lamports to stake |
| validator | string | – | Solana public key (base58) |
| wallet | string | yes | Wallet to stake from |
No output schema declared.
No examples provided.
staking_stakeSolayer ~117
Stake SOL for sSOL via Solayer. Re-staking protocol with additional yield. SAP MCP context: Protocol staking; operation class write. Use for SOL and liquid staking flows. Confirm validator or provider, amount, lockup/unstake terms, and account ownership before writes. Use SAP staking tools for SAP protocol stake accounts; use AgentKit staking tools for external staking protocols.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount in lamports to stake for sSOL |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
staking_unstakeJupSOL ~109
Unstake jupSOL back to SOL. SAP MCP context: Protocol staking; operation class write. Use for SOL and liquid staking flows. Confirm validator or provider, amount, lockup/unstake terms, and account ownership before writes. Use SAP staking tools for SAP protocol stake accounts; use AgentKit staking tools for external staking protocols.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount of jupSOL to unstake |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
staking_unstakeSOL ~107
Deactivate and withdraw SOL from a stake account. SAP MCP context: Protocol staking; operation class write. Use for SOL and liquid staking flows. Confirm validator or provider, amount, lockup/unstake terms, and account ownership before writes. Use SAP staking tools for SAP protocol stake accounts; use AgentKit staking tools for external staking protocols.
| Name | Type | Req | Description |
|---|---|---|---|
| stakeAccount | string | yes | Stake account to deactivate and withdraw |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
staking_unstakeSolayer ~109
Unstake sSOL back to SOL via Solayer. SAP MCP context: Protocol staking; operation class write. Use for SOL and liquid staking flows. Confirm validator or provider, amount, lockup/unstake terms, and account ownership before writes. Use SAP staking tools for SAP protocol stake accounts; use AgentKit staking tools for external staking protocols.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount of sSOL to unstake |
| wallet | string | yes | Solana public key (base58) |
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.