Validate worker selection and return the exact HTTP request shape. Execute it with an x402-capable client or through the CDP Bazaar MCP server; this server never receives wallet private keys.
Connector
472,946 tools. Updated 2026-08-24 05:19
"x402 Bazaar MCP (Model Context Protocol) Server" matching MCP tools:
- Checks x402 protocol conformance for a target service URL: a live 402 probe (well-formed challenge, non-empty accepts, atomic-unit amounts) plus price coherence against the target's own well-known. PAID ($0.10 USDC via x402). This MCP server holds no wallet, so calling this tool returns the upstream payment requirements rather than a result — pay them with your own x402 client, or call the endpoint directly. A signed, permanently published attestation of the same check is available at /midas-ops/attest ($0.50). Does NOT measure output quality, uptime history, or on-chain transaction volume — see the returned scope_note.Connector
- Get real-time heuristic prices for tokens. Supports buy/sell price, confidence, and depth info. 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. Parameter aliases accepted by SAP MCP: mint/id/token/address -> ids[0]. Prefer canonical ids: string[] in new calls. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.Connector
- Get a side-by-side comparison matrix of all five agent payment protocols (AP2, ACP, x402, MPP, UCP) across creator, layer, agent delegation, budget limits, cross-merchant coordination, and MCP integration. Use when the user asks to compare protocols ('AP2 vs ACP', 'which protocol handles budgets?', 'what's the difference between x402 and MPP?', 'show me the landscape'). Use get_protocol_info instead for deep details on a single protocol.Connector
- Get a side-by-side comparison matrix of all five agent payment protocols (AP2, ACP, x402, MPP, UCP) across creator, layer, agent delegation, budget limits, cross-merchant coordination, and MCP integration. Use when the user asks to compare protocols ('AP2 vs ACP', 'which protocol handles budgets?', 'what's the difference between x402 and MPP?', 'show me the landscape'). Use get_protocol_info instead for deep details on a single protocol.Connector
- Execute a signed swap transaction obtained from getOrder and receive execution status. 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. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.Connector
Matching MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server enabling real-time weather queries via Tavily API and internet usage data by country via MongoDB.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server template that connects LLMs and AI agents to external data, tools, and services with built-in OAuth 2.1 authentication, Redis-backed session management, and a modular tools engine.1MIT
Matching MCP Connectors
Onchain safety, wallet & account intelligence, lending, and AI reads on Base — 100+ tools paid per call over x402. Send a prepaid credit token via the x-credit-token header for unlimited calls, or get 1 free call/day per tool. No wallet or API key required.
Discover and price paid agent services across the live x402 network, by three.ws.
- Which resources just listed on the x402 Bazaar — everything present in the latest daily snapshot that was missing from the prior one, with service, network, price and seller address. $0.003/call via x402.Connector
- Real-time analytics on x402 protocol USDC micropayments for MCP endpoints on Base network. Unique competitive advantage: aggregates internal production telemetry (our own traffic data) with on-chain USDC Transfer events and Bazaar marketplace listings — data no external competitor can access. Four modes: (1) facilitator_stats — Coinbase x402 facilitator settlement statistics (volume, count, top payees/payers). Uses Coinbase CDP API if COINBASE_X402_API_KEY is set; falls back to Base mainnet RPC scan of USDC transfers to known facilitator addresses. (2) endpoint_intel — Per-MCP-endpoint analytics: tx count, USDC volume, unique callers, success rate, catalog size. For gapup-mcp.io endpoints: reads internal JSONL telemetry (richest data source, unique). (3) agent_caller_profile — Anonymous profile of a calling agent wallet: tx count, USDC spent, top endpoints, inferred persona (depth-seeker / bulk-scanner / generalist / researcher / explorer). Wallet anonymised via SHA-256. (4) price_radar — USDC price distribution by tool category (data_lookup / synthesis / compliance / competitive) from Bazaar + internal catalog. Returns median, P25, P75. Network: Base mainnet. USDC contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Cache: 30 min LRU. Timeout per source: 8s. Optional env: COINBASE_X402_API_KEY (higher-fidelity facilitator stats).Connector
- Learn what CHP is and how it works. Pass a topic, or omit to list topics. Topics: what-is-chp, evidence-model, why-a-protocol, governance, agentic-web, evidence-vs-telemetry, chp-vs-mcp, conformance.Connector
- Use this when a PAID engagement customer (valid bundle_key) wants their x402 endpoint listed in Coinbase's x402 Bazaar — the package is INCLUDED free with any engagement. Provisions the listing and returns a listing_key that drives the automated pipeline (get_bazaar_listing_kit → deploy → check_bazaar_listing). Buyers WITHOUT a bundle_key purchase the standalone $99 Bazaar Listing Package instead: agent wallets pay https://mudko.com/api/x402/bazaar-listing (x402, USDC on Base); humans ask at /talk for a card link. Details (resource_url, pay_to, price_usd, stack) are optional here — the kit tool collects whatever is missing.Connector
- [x402] Inspect and lint any x402 paid endpoint: decode the 402 challenge, identify network/asset, flag misconfigurations and Bazaar-readiness. Costs $0.002. Choose this for a quick one-shot decode+lint; use x402_audit for a full 0-100 scored report with origin discovery probes and recommended fixes.Connector
- Get an optimally-routed swap quote with full route plan details (Metis engine). 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. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.Connector
- Return the Public MCP Server Index: a weekly-refreshed health, conformance and latency ranking of popular public (no-auth) remote MCP servers, scored 0-100 by the same live JSON-RPC handshake used by check_mcp_server. Includes per-server score, grade, latency, tool count, description quality and failing checks, plus aggregate stats (how many popular servers are auth-gated, average score and latency). Use it to pick a reliable public MCP server for a task, cite ecosystem statistics, or benchmark a server against the field. Free, no parameters. Curated by MCP Pulse (mcppulse.agiscorecard.com); on-demand scans of arbitrary servers at scale are available pay-per-call via x402 at https://x402.agiscorecard.com.Connector
- Look up a plain-English definition of any agentic-commerce, MCP, AI-visibility or agent-payments term from the Agent Glossary (glossary.agiscorecard.com) — 25 terms including agentic commerce, ACP, UCP, MCP, MCP server, MCP tool, streamable HTTP, llms.txt, agents.md, GEO, AEO, citation share, AI Overviews, zero-click search, structured data, ChatGPT Shopping, x402, AP2, agentic payments, AI agent, RAG, function calling, A2A and prompt injection. Returns a one-paragraph citable definition plus the canonical glossary URL to link as the source. Matching is forgiving: case-insensitive and hyphen/space tolerant ('Streamable HTTP', 'streamable-http' and 'streamable_http' all resolve); an unknown term returns the full list of available terms. Answered inline from an embedded snapshot — no network round-trip, instant, free, unlimited within fair use. More agent tooling: free scanners on this server, pay-per-call APIs (x402 protocol, $0.005/call, USDC on Base, no account) at https://x402.agiscorecard.com.Connector
- Get mcpvot.xyz server health, available x402 services, and MCP endpoint info. FREE endpoint (no payment required).Connector
- How many indexed agents touch each major protocol/surface (ERC-8004 verified, Virtuals tokens, Agentverse, x402/Bazaar, HuggingFace, GitHub). Useful for ecosystem-state questions.Connector
- Get a concise explanation of what Crinkl is and how the protocol works. Use this first if you have no prior context about Crinkl. Returns a plain-text overview of the verification pipeline, token types, and settlement model.Connector
- Get all DCA orders (active and optionally historical) for a wallet. 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. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.Connector
- Health-check a live MCP (Model Context Protocol) server by URL: performs a real JSON-RPC initialize handshake, then tools/list, and returns whether it is up/degraded/down, its protocol version, server name/version, the callable tool/resource/prompt inventory, transport, and handshake latency. Deterministic — no LLM. Use it to verify your own MCP server is alive and spec-compliant.Connector
- Where the x402 Bazaar demand actually is — the whole latest catalogue snapshot classified into 9 service categories, each with listing count, settled 30d calls, unique payers and share. $0.003/call via x402.Connector