Adds Storybook component and story documentation tools to an MCP server you run yourself.
Sap MCP Server
oobe-protocol-labs · MCP server(filed by default)
SAP MCP Server exposes the OOBE Synapse Agent Protocol to AI agents on Solana. Agents can work with SAP identity, registry, reputation, tools, memory, payments, settlement and proof of execution, and hosted tools can be priced per call with x402 payments. It runs locally or as a hosted endpoint, with optional policy checks and local or external signing. Read-only discovery on the hosted endpoint needs no local signer, while paying or moving value needs a wallet you control.
Written by ooruby from the README of @oobe-protocol-labs/sap-mcp-server 0.9.86.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your agent can register an identity, make payments and settle work on Solana through the tools of one protocol.
What you could do with it
- Use the hosted endpoint for read-only discovery without setting up a local signer.
- Run the setup wizard to create a profile and a dedicated agent wallet before your agent pays for hosted tools.
- Charge for your own hosted tools per call with x402 payments and the self-hosted facilitator.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Official MCP gateway for OOBE Protocol SAP — AI agents can interact with SAP identity, registry, reputation, tools, memory, payments, settlement, and proof-of-execution on Solana
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.9.86, the file with digest sha512-Ipvq6mspJY2PG7ja2dxfc6mHX0qYn6eWMktzmjkn62P66PvtnRwVo+DxhMZ/P6V3a6+0X+nop70YpH4rJ6Wxmg==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- No auth declared. Its hosted endpoint, as the official MCP registry lists it, does not say it asks for a key. That is what the listing declares, not a finding that it has no protection.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"sap-mcp-config": {
"command": "npx",
"args": [
"-y",
"-p",
"@oobe-protocol-labs/sap-mcp-server@0.9.86",
"sap-mcp-config"
]
}
}
}Or run it directly.
npx -y -p @oobe-protocol-labs/sap-mcp-server@0.9.86 sap-mcp-configPinned to 0.9.86, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @oobe-protocol-labs/sap-mcp-server
- Version read
- 0.9.86
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/oobe-protocol-labs-sap-mcp-server)About this listing
- Kind
- MCP server
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-04
Similar MCP servers
All MCP serversLets your agent control and inspect a live Chrome browser using Chrome DevTools.
Pulls version-specific library docs and code examples straight into your agent's context.
Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.