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 (2 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 →
3land_buyNFT ~122
Purchase an NFT from a 3.Land listing. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | string | yes | Solana public key (base58) |
| listingId | string | yes | 3.Land listing ID |
No output schema declared.
No examples provided.
3land_cancelListing ~124
Cancel an active NFT listing on 3.Land. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | string | yes | 3.Land listing ID to cancel |
| seller | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
3land_createCollection ~159
Create a new NFT collection on 3.Land marketplace. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| creators | array | – | – |
| description | string | – | Collection description |
| image | string | yes | Collection cover image URL |
| name | string | yes | Collection name |
| owner | string | yes | Collection owner wallet |
| royaltyBps | number | – | – |
| symbol | string | yes | Collection symbol |
No output schema declared.
No examples provided.
3land_listForSale ~165
List an NFT for sale on 3.Land in any SPL token. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| expiry | string | – | ISO 8601 listing expiry timestamp |
| mint | string | yes | NFT mint to list |
| price | string | yes | Listing price (in specified token) |
| priceMint | string | – | NFT mint address (base58) |
| seller | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
3land_mintAndList ~193
Mint an NFT on 3.Land and automatically list it for sale. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | array | – | – |
| collection | string | yes | 3.Land collection ID |
| description | string | – | – |
| image | string | yes | NFT image URL |
| name | string | yes | – |
| owner | string | yes | Solana public key (base58) |
| price | string | yes | Listing price in token amount |
| priceMint | string | – | NFT mint address (base58) |
| supply | number | – | Edition supply |
No output schema declared.
No examples provided.
adrena_addCollateral ~114
Add collateral to an existing Adrena position. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Raw token amount (smallest unit) |
| positionKey | string | yes | Solana public key (base58) |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
adrena_closePosition ~100
Close a perpetual position on Adrena Protocol. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| positionKey | string | yes | Solana public key (base58) |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
adrena_getPositions ~85
Get all open positions on Adrena Protocol. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
adrena_openPosition ~181
Open a leveraged perpetual position on Adrena Protocol. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| collateralAmount | string | yes | Raw token amount (smallest unit) |
| collateralMint | string | yes | Collateral token mint (e.g. USDC, SOL) |
| leverage | number | yes | Leverage multiplier |
| market | string | yes | Market symbol (e.g. "SOL", "BTC", "ETH") |
| side | string | yes | – |
| stopLoss | number | – | Stop loss price |
| takeProfit | number | – | Take profit price |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
adrena_removeCollateral ~113
Remove collateral from an Adrena position. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Raw token amount (smallest unit) |
| positionKey | string | yes | Solana public key (base58) |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
alldomains_getOwnedDomains ~90
Get all domains owned by a wallet across all TLDs. SAP MCP context: Protocol alldomains; operation class read. Use to list domains owned by a wallet through AllDomains. Use as discovery context before choosing a name to associate with an agent.
| Name | Type | Req | Description |
|---|---|---|---|
| tld | string | – | Filter by TLD |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
alldomains_registerDomain ~141
Register a domain on AllDomains (supports multiple TLDs: .abc, .bonk, .poor, etc.). SAP MCP context: Protocol alldomains; operation class write. Use for AllDomains name registration and resolution workflows. Confirm domain, TLD, owner, and renewal or purchase terms before writes. Use only when the requested name service is not SNS-specific.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Full domain (e.g. "myname.abc", "trader.bonk") |
| tld | string | – | TLD if not included in domain string |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
alldomains_resolveDomain ~72
Resolve a multi-TLD domain to its owner wallet. SAP MCP context: Protocol alldomains; operation class read. Use to resolve an AllDomains name without changing ownership or records. Use only when the requested name service is not SNS-specific.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Full domain to resolve |
No output schema declared.
No examples provided.
blinks_buildActionUrl ~108
Build and optionally wrap a Solana Action URL for sharing as a Blink. SAP MCP context: Protocol blinks; operation class read. Use for Solana Actions and Blinks metadata fetch, validation, and POST action preparation. Preview and validate actions before signing or submitting transactions through SAP transaction tools.
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | yes | Action API endpoint |
| blinkProvider | string | – | Optionally wrap in a Blink provider URL |
| params | object | – | Template parameters to encode |
No output schema declared.
No examples provided.
blinks_confirmAction ~92
Confirm a completed Solana Action by sending the tx signature back to the Action provider. SAP MCP context: Protocol blinks; operation class read. Use for Solana Actions and Blinks metadata fetch, validation, and POST action preparation. Preview and validate actions before signing or submitting transactions through SAP transaction tools.
| Name | Type | Req | Description |
|---|---|---|---|
| actionUrl | string | yes | – |
| signature | string | yes | Transaction signature after signing and submitting |
No output schema declared.
No examples provided.
blinks_executeAction ~128
Execute a Solana Action — sends wallet to the Action endpoint and receives a transaction to sign. SAP MCP context: Protocol blinks; operation class write. Use to execute a Solana Action POST flow. Confirm the action metadata, parameters, expected transaction, and user intent before invoking. Preview and validate action output before signing or submitting any returned transaction through SAP transaction tools.
| Name | Type | Req | Description |
|---|---|---|---|
| actionUrl | string | yes | Action endpoint URL (from getAction links) |
| params | object | – | Key-value parameters to fill Action template variables |
| wallet | string | yes | User wallet to sign the transaction |
No output schema declared.
No examples provided.
blinks_getAction ~95
Fetch metadata for a Solana Action (Blink) — returns title, description, available actions, and parameters. SAP MCP context: Protocol blinks; operation class read. Use for Solana Actions and Blinks metadata fetch, validation, and POST action preparation. Preview and validate actions before signing or submitting transactions through SAP transaction tools.
| Name | Type | Req | Description |
|---|---|---|---|
| actionUrl | string | yes | Solana Action URL (https endpoint implementing the Actions spec) |
No output schema declared.
No examples provided.
blinks_resolveBlinkUrl ~101
Resolve a Blink URL (e.g. dial.to link) to its underlying Solana Action URL. SAP MCP context: Protocol blinks; operation class read. Use for Solana Actions and Blinks metadata fetch, validation, and POST action preparation. Preview and validate actions before signing or submitting transactions through SAP transaction tools.
| Name | Type | Req | Description |
|---|---|---|---|
| blinkUrl | string | yes | Blink URL (e.g. https://dial.to/?action=solana-action:...) |
No output schema declared.
No examples provided.
blinks_validateActionsJson ~96
Validate a domain's actions.json file — checks if a website correctly implements the Solana Actions spec. SAP MCP context: Protocol blinks; operation class read. Use for Solana Actions and Blinks metadata fetch, validation, and POST action preparation. Preview and validate actions before signing or submitting transactions through SAP transaction tools.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check for actions.json (e.g. "jupiter.exchange") |
No output schema declared.
No examples provided.
bridging_bridgeDeBridge ~240
Bridge tokens across chains via deBridge DLN. Fast cross-chain transfers with deterministic pricing. SAP MCP context: Protocol bridging; operation class write. Use for cross-chain asset movement through Wormhole or deBridge. Confirm source chain, destination chain, token mint, amount, recipient, route fees, and finality expectations before invoking a bridge write. For bridge flows call the matching status tool after submission. If the bridge capability belongs to a registered SAP agent, advertise it with sap_publish_tool_by_name and include bridge capability IDs in sap_register_agent or sap_update_agent.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to bridge (raw) |
| destinationChain | number | yes | Destination chain ID |
| recipient | string | yes | Recipient address on destination chain |
| sender | string | yes | Sender address |
| slippageBps | number | – | Slippage tolerance in bps |
| sourceChain | number | yes | Source chain ID (e.g. 7565164 for Solana) |
| tokenIn | string | yes | Token address on source chain |
| tokenOut | string | yes | Token address on destination chain (use "0x0" for native) |
No output schema declared.
No examples provided.
bridging_bridgeDeBridgeStatus ~81
Check the status of a deBridge DLN cross-chain transfer. SAP MCP context: Protocol bridging; operation class read. Use to check deBridge transfer status after a bridge submission. Call this after bridging_bridgeDeBridge and keep the resulting status with the user-facing bridge audit trail.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | deBridge DLN order ID |
No output schema declared.
No examples provided.
bridging_bridgeWormhole ~231
Bridge tokens across chains via Wormhole. Supports Solana ↔ EVM chains. SAP MCP context: Protocol bridging; operation class write. Use for cross-chain asset movement through Wormhole or deBridge. Confirm source chain, destination chain, token mint, amount, recipient, route fees, and finality expectations before invoking a bridge write. For bridge flows call the matching status tool after submission. If the bridge capability belongs to a registered SAP agent, advertise it with sap_publish_tool_by_name and include bridge capability IDs in sap_register_agent or sap_update_agent.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to bridge (raw, smallest unit) |
| destinationChain | string | yes | Destination chain identifier |
| recipient | string | yes | Recipient address on destination chain |
| relayerFee | string | – | Raw token amount (smallest unit, no decimals) |
| sender | string | yes | Sender wallet on source chain |
| sourceChain | string | yes | Source chain identifier (e.g. "solana", "ethereum", "base", "polygon") |
| token | string | yes | Token address on source chain |
No output schema declared.
No examples provided.
bridging_bridgeWormholeStatus ~92
Check the status of a Wormhole bridge transfer. SAP MCP context: Protocol bridging; operation class read. Use to check Wormhole bridge transfer status after a bridge submission. Call this after bridging_bridgeWormhole and keep the resulting status with the user-facing bridge audit trail.
| Name | Type | Req | Description |
|---|---|---|---|
| sequence | string | yes | Wormhole sequence number from bridgeWormhole response |
| sourceChain | string | yes | – |
No output schema declared.
No examples provided.
coingecko_getOHLCV ~106
Get OHLCV (price chart) data from CoinGecko. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments.
| Name | Type | Req | Description |
|---|---|---|---|
| days | string | – | – |
| tokenId | string | yes | – |
| vsCurrency | string | – | – |
No output schema declared.
No examples provided.
coingecko_getPoolsByToken ~113
Get all liquidity pools for a token from CoinGecko on-chain DEX tracker. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | – |
| page | number | – | – |
| tokenAddress | string | yes | Token contract/mint address |
No output schema declared.
No examples provided.
coingecko_getTokenInfo ~97
Get detailed token information from CoinGecko (description, links, market data). SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenId | string | yes | CoinGecko token ID |
No output schema declared.
No examples provided.
coingecko_getTokenPrice ~132
Get token price and market data from CoinGecko. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments.
| Name | Type | Req | Description |
|---|---|---|---|
| include24hChange | boolean | – | – |
| include24hVolume | boolean | – | – |
| includeMarketCap | boolean | – | – |
| tokenId | string | yes | CoinGecko token ID or contract address |
| vsCurrency | string | – | – |
No output schema declared.
No examples provided.
coingecko_getTopGainersLosers ~97
Get top gainers and losers from CoinGecko. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | string | – | – |
| vsCurrency | string | – | – |
No output schema declared.
No examples provided.
coingecko_getTrending ~77
Get trending tokens and NFTs on CoinGecko. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
das_getAsset ~85
Get detailed information about a single NFT/asset via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Asset mint address |
No output schema declared.
No examples provided.
das_getAssetsByCollection ~102
Get all NFTs in a collection via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update.
| Name | Type | Req | Description |
|---|---|---|---|
| collectionAddress | string | yes | NFT mint address (base58) |
| limit | number | – | – |
| page | number | – | – |
No output schema declared.
No examples provided.
das_getAssetsByCreator ~114
Get all NFTs/assets created by a specific creator via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update.
| Name | Type | Req | Description |
|---|---|---|---|
| creatorAddress | string | yes | Solana public key (base58) |
| limit | number | – | – |
| onlyVerified | boolean | – | – |
| page | number | – | – |
No output schema declared.
No examples provided.
das_getAssetsByOwner ~130
Get all NFTs/assets owned by a wallet via DAS (supports pagination). SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | – |
| before | string | – | – |
| limit | number | – | – |
| ownerAddress | string | yes | Solana public key (base58) |
| page | number | – | – |
| sortBy | string | – | – |
No output schema declared.
No examples provided.
das_searchAssets ~165
Search NFTs/assets with flexible filters via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update.
| Name | Type | Req | Description |
|---|---|---|---|
| burnt | boolean | – | – |
| compressed | boolean | – | – |
| creatorAddress | string | – | Solana public key (base58) |
| frozen | boolean | – | – |
| grouping | – | – | Grouping key-value pair (e.g. ["collection", "mint_address"]) |
| jsonUri | string | – | – |
| limit | number | – | – |
| ownerAddress | string | – | Solana public key (base58) |
| page | number | – | – |
No output schema declared.
No examples provided.
drift_borrow ~119
Borrow tokens on Drift against deposited collateral. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Raw token amount (smallest unit) |
| mint | string | yes | Token mint address (base58) |
| subAccountId | number | – | – |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
drift_closePerpPosition ~101
Close a perpetual position on Drift. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| marketIndex | number | yes | – |
| subAccountId | number | – | – |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
drift_deposit ~127
Deposit tokens into a Drift account for trading or lending. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Raw token amount (smallest unit) |
| mint | string | yes | Token to deposit (e.g. USDC, SOL) |
| subAccountId | number | – | – |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
drift_getPositions ~96
Get all open positions and account info for a Drift account. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| subAccountId | number | – | – |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
drift_lend ~120
Lend tokens on Drift to earn interest. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Raw token amount (smallest unit) |
| mint | string | yes | Token mint address (base58) |
| subAccountId | number | – | – |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
drift_openPerpPosition ~186
Open a perpetual futures position on Drift. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | yes | – |
| leverage | number | – | Leverage multiplier (max 20x) |
| marketIndex | number | yes | Drift perp market index (0=SOL-PERP, 1=BTC-PERP, etc.) |
| orderType | string | – | – |
| price | number | – | Limit price (required for limit orders) |
| reduceOnly | boolean | – | – |
| size | string | yes | Position size in base token units |
| subAccountId | number | – | – |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
drift_withdraw ~118
Withdraw tokens from a Drift account. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Raw token amount (smallest unit) |
| mint | string | yes | Token mint address (base58) |
| subAccountId | number | – | – |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
gibwork_createBounty ~154
Create a new bounty on Gib Work with on-chain escrow. SAP MCP context: Protocol gibwork; operation class write. Use for bounty creation, listing, and work submission. Confirm scope, payout, recipient, and deliverable evidence before writes. Use SAP attestation or feedback tools after work completion when reputation should be recorded on SAP.
| Name | Type | Req | Description |
|---|---|---|---|
| creator | string | yes | Solana public key (base58) |
| deadline | number | – | Deadline (Unix timestamp) |
| description | string | yes | Detailed bounty description |
| rewardAmount | string | yes | Reward amount |
| rewardMint | string | – | Token mint address (base58) |
| tags | array | – | – |
| title | string | yes | Bounty title |
No output schema declared.
No examples provided.
gibwork_listBounties ~97
List available bounties on Gib Work. SAP MCP context: Protocol gibwork; operation class write. Use for bounty creation, listing, and work submission. Confirm scope, payout, recipient, and deliverable evidence before writes. Use SAP attestation or feedback tools after work completion when reputation should be recorded on SAP.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
gibwork_submitWork ~122
Submit completed work for a Gib Work bounty. SAP MCP context: Protocol gibwork; operation class write. Use for bounty creation, listing, and work submission. Confirm scope, payout, recipient, and deliverable evidence before writes. Use SAP attestation or feedback tools after work completion when reputation should be recorded on SAP.
| Name | Type | Req | Description |
|---|---|---|---|
| bountyId | string | yes | – |
| notes | string | – | – |
| submissionUrl | string | yes | URL to the completed work (PR, doc, etc.) |
| wallet | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
jito_getBundleStatus ~81
Check the status of a submitted Jito bundle. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleId | string | yes | – |
No output schema declared.
No examples provided.
jito_getTipEstimate ~75
Get current Jito tip percentile estimates for bundle inclusion priority. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jito_sendBundle ~112
Send a Jito bundle for MEV-protected, atomic transaction execution. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_register_agent, sap_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.
| Name | Type | Req | Description |
|---|---|---|---|
| tipLamports | string | – | Raw token amount (smallest unit) |
| transactions | array | yes | Array of base64-encoded signed transactions (max 5) |
No output schema declared.
No examples provided.
jupiter_cancelDCA ~134
Create an unsigned transaction to cancel a DCA recurring order. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy.
| Name | Type | Req | Description |
|---|---|---|---|
| computeUnitPrice | string | – | – |
| order | string | yes | DCA order public key to cancel |
| recurringType | string | yes | Recurring order type — "time" for time-based DCA, "price" for price-triggered |
| user | string | yes | Wallet that owns the DCA order |
No output schema declared.
No examples provided.
jupiter_cancelLimitOrder ~103
Create an unsigned transaction to cancel a specific limit order. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy.
| Name | Type | Req | Description |
|---|---|---|---|
| computeUnitPrice | string | – | – |
| maker | string | yes | Solana wallet public key (base58) |
| order | string | yes | Order public key to cancel |
No output schema declared.
No examples provided.
jupiter_cancelLimitOrders ~105
Create unsigned transactions to cancel multiple limit orders in batch. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy.
| Name | Type | Req | Description |
|---|---|---|---|
| computeUnitPrice | string | – | – |
| maker | string | yes | Solana wallet public key (base58) |
| orders | array | yes | Array of order public keys to cancel |
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.