B2P Central MCP Server — Privacy-first Bitcoin & crypto service aggregator: compare P2P offers, swap quotes, lending rates and gift cards across multiple providers, with hardened safeguards for AI agents (no private keys, no auto-payments, mandatory human confirmation). B2P Central MCP Server exposes the B2P Central aggregator API to AI assistants through the Model Context Protocol, enabling safe, auditable crypto service discovery and preparation. What it does • P2P market comparison — Search and compare Bitcoin P2P buy/sell offers across providers (HodlHodl, Bisq, RoboSats, etc.) by price, limits, payment methods, and claimed No-KYC classification. • Swap rate aggregation — Compare fixed and floating crypto swap quotes across networks (Bitcoin, Lightning, Liquid, Ethereum…), with expiry tracking and best-route highlighting. • Lending & borrowing discovery — Browse collateralized crypto loan offers (APR, LTV, duration) across providers. • Gift card catalog — Search gift-card products purchasable with crypto (experimental flow). • Provider intelligence — Access curated metadata on KYC requirements, privacy practices, terms of service and reliability for every listed provider. • Order tracking — Follow the status of existing swaps and gift orders with built-in rate limiting and payment-detail redaction. Safety-first design Unlike generic crypto connectors, this server is engineered for agentic workflows with strict guardrails: • 🔒 Never custodial — The server never stores, signs, or transmits private keys, and never pays invoices automatically. • ✅ Two-step confirmation — Every write operation (b2p_create_swap, b2p_create_gift_order, b2p_create_subscription) requires an explicit prepare → confirm flow with idempotency keys and expiring tickets. • 🛡️ Sensitive data redaction — Addresses, invoices, emails and tracking URLs are masked by default; payment details require an extra opt-in scope. • 📊 Scope-based authorization — Distinct read, create and track scopes let operators enforce least-privilege access.

MCP readiness

B · 88/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (2311 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 13 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (2311 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 95% of peers; This listing 88 · peer median 81
Latency: Faster than 10% of peers; This listing 901 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-10-01 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/admin-zh6a/b2pcentral/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/admin-zh6a/b2pcentral/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://www.b2p-central.com/#/mcp

Listed at (smithery)

https://www.b2p-central.com/#/mcp