Hermes Hermes Codex Codex Claude Claude OpenClaw OpenClaw Hermes Hermes Codex Codex Claude Claude OpenClaw OpenClaw Hermes Hermes Codex Codex Claude Claude OpenClaw OpenClaw

OOBE Protocol · Hosted MCP gateway

Agent operations, wired into Solana.

SAP MCP is the hosted MCP surface for agents that need real Solana work: protocol tools, registry state, identity, payments, policy, and local non-custodial signing.

Start with the wizard Read docs MCP endpoint

Hosted tools run at https://mcp.sap.oobeprotocol.ai/mcp. Paid and write calls are authorized by the user-owned local sap_payments bridge or an external signer.

sap:mcp://remote
SAP
MCPTools
x402Receipts
SNSIdentity
RPCSolana
Tools268
TransportHTTP
KeysLocal
01

Solana DeFi Protocols

Jupiter, Raydium, Orca, Meteora, Pyth, DAS, Metaplex and more.

02

Solana RPC Methods

Balances, token accounts, assets, simulation, programs, transactions and raw chain reads.

Live endpoint

Streamable HTTP MCP

https://mcp.sap.oobeprotocol.ai/mcp

Free discovery. Paid tools return x402 challenges. Local signatures stay on the user's machine.

03

Synapse Agent Protocol

Registry, tools, reputation, attestations, escrow, settlement, memory, SNS identity.

04

x402 / pay.sh Revenue

$9.90 settled volume across 703 settlement events.

Live hosted gateway

Payment-aware MCP infrastructure.

Public ledger counters show the hosted payment rail without exposing secrets, wallet files, or RPC credentials.

Facilitator Volume $9.90

Estimated settled x402/pay.sh tool volume recorded by the hosted ledger.

Total Settlements 703

2026-08-07T23:42:29.815Z

x402 Challenges 38,813

795 paid, 2 verification failures, 981 local-signer blocks.

Scroll the coordination engine

Hosted calls open into local authorization.

The remote server exposes the tool surface. The local profile owns signer state. The payment bridge resolves x402 challenges and replays the exact call with a receipt.

01 Remote MCP

https://mcp.sap.oobeprotocol.ai/mcp

02 Policy

Limits, approvals, Bento optional.

SAP MCP
03 x402/pay.sh

Challenge, settlement, receipt.

04 Local signer

Keypair bytes never leave device.

Protocol surface

Three buckets. One agent operations layer.

SAP MCP exposes Solana DeFi protocols, Solana RPC methods, and Synapse Agent Protocol operations through one MCP-compatible interface.

01
Jupiter Raydium Orca Meteora Adrena MagicBlock Metaplex Solana Jupiter Raydium Orca Meteora Adrena MagicBlock Metaplex Solana
Solana DeFi

Jupiter, Raydium, Orca, Meteora and market data flows.

02
Solana RPC

Balances, token accounts, DAS assets, transactions, programs and simulation.

03
SAP MCP
SAP Protocol

Agent registry, discovery, reputation, escrow, settlement and attestations.

04 Identity

SNS domain checks, reverse lookup, linked identity and agent profile context.

05 Payments

x402 challenge tools, pay.sh provider metadata, receipts and paid-call replay.

06 Policy

Local limits and optional Bento Guard policy checks before sensitive execution.

07 Skills

Bundled agent skills explain how to choose tools, fetch context and avoid waste.

08 Remote-first

Hosted Streamable HTTP with local non-custodial signing for paid/write calls.

Listed and verifiable

Discover SAP MCP from trusted MCP indexes.

Hosted metadata is public, crawler-friendly, and linked from registries agents already inspect.

Smithery MCP server marketplace listing with hosted server metadata, tools, prompts, and configuration UX. Verified Official MCP Registry Canonical Model Context Protocol registry entry for ai.oobeprotocol.sap.mcp/sap-mcp. Verified

Fast integration path

Remote tools. Local signatures. Smooth payments.

Both paths end with the same production model: hosted SAP MCP tools at /mcp, plus a local non-custodial sap_payments bridge for paid and write calls.

Recommended for most users

Native download

Best when the user wants a guided desktop installer for profile creation, wallet isolation, runtime detection, and payment bridge repair.

  1. 1 Download the desktop wizard for your operating system.
    Windows x64 .exe macOS Apple Silicon .dmg Linux x64 .tar.gz
  2. 2Open the wizard and choose Full hosted SAP MCP setup.
  3. 3Select detected runtimes such as Codex, Claude, Hermes, or OpenClaw.
  4. 4Restart the agent and connect to the hosted /mcp endpoint.
Desktop docs

Developer path

CLI wizard

Best for terminals, servers, and deterministic setup from npm without touching runtime config files by hand.

  1. 1Run the CLI wizard command.
  2. 2Choose Full hosted SAP MCP setup for new profiles, or repair when the profile already exists.
  3. 3Let the wizard configure hosted sap plus local sap_payments.
  4. 4Call sap_payments_readiness; use sap_payments_call_paid_tool for x402 challenges and sap_payments_finalize_transaction for unsigned hosted transactions.
npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config wizard

Already have a profile? Repair only the hosted runtime/payment bridge:

npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config repair
Start here Client configs Payments

Install wizard

Choose native or npm setup.

Create a local SAP MCP profile, signer, policy limits, hosted client config, and payment bridge. For guided details, start with the user docs.

Native installer script 
curl -fsSL https://mcp.sap.oobeprotocol.ai/wizard/install.sh | sh
npm wizard 
npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config wizard
Repair hosted runtime/payment bridge only 
npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config repair

x402 Challenge Tools For Agents

Payment challenges are first-class tools.

Hosted paid calls return x402 requirements. The local sap_payments bridge signs, settles, replays the exact tool call, and returns the receipt without sending keypair bytes to OOBE.

Agent-native paid call flow

1

Agent checks sap_payments_readiness for local profile, signer, balance, and policy status.

2

Paid tools return an x402 challenge with resource, amount, asset, and payTo.

3

Local sap_payments_call_paid_tool signs payment proof and retries the call.

4

If the output is an unsigned transaction, local sap_payments_finalize_transaction previews, signs, and optionally submits already-signed bytes through the hosted relay.

5

The bridge returns receipt, signature, confirmation status, and retry guidance instead of treating a bare signature as success.

npx --yes --package @oobe-protocol-labs/sap-mcp-server sap-mcp-x402-paid-call --tool sap_list_all_agents --arguments '{"limit":5}' --max-usd 0.05 --confirm

Provider metadata

pay.sh and x402 discovery endpoints are public, machine-readable, and secret-free.

Start operating

Documentation that maps to the agent workflow.

Getting started Hosted remote MCP Client configs Desktop wizard x402 and pay.sh Skills and tools

Endpoint map

Public surface area.

POST https://mcp.sap.oobeprotocol.ai/mcp
POST https://mcp.sap.oobeprotocol.ai/tx/submit
GET https://mcp.sap.oobeprotocol.ai/docs
GET https://mcp.sap.oobeprotocol.ai/health
GET https://mcp.sap.oobeprotocol.ai/server.json
GET https://mcp.sap.oobeprotocol.ai/pricing.json
GET https://mcp.sap.oobeprotocol.ai/openapi.json
GET https://mcp.sap.oobeprotocol.ai/premium/catalog.json
GET https://mcp.sap.oobeprotocol.ai/premium/streams.json
GET https://mcp.sap.oobeprotocol.ai/premium/webhooks.json
GET https://mcp.sap.oobeprotocol.ai/.well-known/x402
GET https://mcp.sap.oobeprotocol.ai/pay/provider.yml
GET https://mcp.sap.oobeprotocol.ai/.well-known/mcp/server-card.json
GET https://mcp.sap.oobeprotocol.ai/.well-known/agent-card.json
GET https://mcp.sap.oobeprotocol.ai/.well-known/sap-mcp-wizard.json

MCP clients should connect to /mcp with Accept: application/json, text/event-stream.

Security boundary

Non-custodial by default.

  • Keypair bytes are never exposed by public endpoints.
  • RPC secrets are redacted from public metadata and UI.
  • Paid tools require payment before execution.
  • Write tools require a user-controlled local signer or external signer.