"Simple MCP example using HTTP transport" matching MCP tools:

• guild_check

  agent-guild

  START HERE when asking "which agent should I hire for this capability?" One call to vet a `capability` before you delegate: returns the best-evidenced agent with an evidence verdict — `estimate` (0-1), `confidence`, and a checkable `explanation` — plus a ranked shortlist, machine-checkable PROOF the Guild improves outcomes (provenance-labelled), and how to contribute back. Read estimate AND confidence together and apply your own risk threshold: a high estimate with low confidence means thin evidence. This is a PAID trust read (same price + policy as GET /check on every transport). When the rail is active, an unpaid call returns a complete x402 payment challenge for the canonical HTTP resource; retry with the payment in the request _meta['x402/payment'] (official x402 MCP meta key), or pass a funded `api_key` for SANDBOX credits (never revenue). Free while the service is in soft-launch. Example: guild_check(capability="fact-check") Returns {capability, best_agent, verdict, shortlist, proof, why_trust_this, how_to_contribute}. Use guild_search / guild_risk_score for finer control.

  Connector

• interest_rate

  mcp

  Use this when you need the exact interest rate that grows a principal to a target amount over a set number of years. type="compound" (default) uses the closed-form nth-root formula for the given compounding frequency; type="simple" uses linear growth. Requires target greater than principal and all values positive. Returns the annual rate as a percent plus the interest earned and the growth multiple; compoundingPerYear is null for simple interest. Deterministic: same input, same output. Example: principal=1000, target=2000, years=10, compoundingPerYear=12 -> ratePercent=6.9515, growthMultiple=2. Prefer this over trial-and-error.

  Connector

• upload_design_file

  a2a2p — Agent-to-Agent-to-Physical

  Turn local manufacturing file bytes into the temporary HTTPS reference used by specification.design_files. This is a bounded intake operation, not a request, provider call, quote, order, payment, or fabrication action. Common RFC 4648 transport forms are normalized, then decoded bytes are recognized by signature, checked against the declared format, screened before storage, retained for one hour, and never included in telemetry. Supported roles include geometry (STL/STEP) and drawings (DXF/PDF). The 2 MiB MCP ceiling is transport-specific; use POST /api/upload with purpose=manufacturing_design_file for files up to 8 MiB. Pass the returned file_reference object unchanged in specification.design_files on the next call.

  Connector

• stream_feed_ndjson

  Opedd — Licensed Content for AI

  Bulk-export a buyer's licensed catalog via GET /enterprise-license?format=ndjson (Phase 11 M3). Returns up to 1000 articles per call (collected from line-delimited JSON wire format). Same per-scope content contract as list_feed: METERED (filtered-scope) keys export metadata only (content_body null, content_access 'metered_per_call') — use get_content for article text. Each article emits one usage_records row (analytics-only sentinel 'bulk-export:<request_id>:<article_id>' — not metered-billable per the revenue-model bifurcation invariant). Use `since` (ISO 8601) for delta-feed. Use `cursor` to paginate beyond 1000. Backend supports 5000 articles per call; the MCP cap is 1000 for transport reasonability. Real bulk-ingest pipelines should use the Python SDK (pip install opedd) directly — not via MCP. Requires OPEDD_ACCESS_KEY (ent_*).

  Connector

• list_paired_models

  ReliaStats

  Return the catalog of paired models — concrete real-world systems that live in two ChiAha sandboxes simultaneously, one for dynamics (DES via ReliaSim) and one for statistics (distribution fitting + validation via ReliaStats). Today: a single paired model — the bottling line. Returns canonical model IDs + cross-MCP routing metadata (which ReliaSim chapter, which ReliaSim MCP tools, which ReliaStats mode consumes which file shape). Use when a user asks about cross-MCP workflows, paired sandboxes, or the bottling-line example. ANTI-FABRICATION: this is a soft-reference catalog — to actually run a simulation, the LLM client calls ReliaSim's MCP tools directly.

  Connector

• scan_mcp_server

  Compuute MCP Security Scanner

  Scan a public GitHub MCP-server repository for security issues. Clones the repo (shallow, <60s, <200 MB), runs compuute-scan v0.6.2 in static analysis mode (no code execution from the target), and returns a structured report with severity counts, a 0-100 score, and the 10 most severe findings. WHEN TO USE: - Before connecting to an unknown MCP server discovered via Anthropic Registry, Smithery, mcp.so, or a Discord recommendation. - Before installing a third-party MCP-server package into a production pipeline. - As part of an agent's pre-commit / pre-deploy due-diligence step when adding new dependencies. - As one input to a multi-source trust evaluation (combine with publisher reputation, package install count, last-update recency). WHEN NOT TO USE: - For private repos. Use the on-prem CLI instead: `npx compuute-scan ./path-to-private-repo` - For deep exploitability assessment of a specific code path. This is pattern matching, not dataflow analysis. Book a manual L2-L4 audit at https://compuute.se/audit for that depth. - For non-GitHub hosts (GitLab, Bitbucket, self-hosted). v1 supports github.com only. - For repos > 200 MB or clone time > 60s. The endpoint returns a 413 or 504 in those cases — fall back to local CLI. EXPECTED RESPONSE TIME: - Median: ~1-2 seconds for small repos (<100 files). - p99: ~10 seconds for medium repos. - Hard timeout at clone=60s, scan=120s combined. EXPECTED COST: - Free tier in MVP. Future Pro tier may charge per-scan or per-month. DATA FRESHNESS: - Scanner version is reported in response.scanner.version. - L1 rule set freshness reflects compuute-scan releases — see github.com/Compuute/compuute-scan/CHANGELOG.md for the latest CVE and threat-intel response timeline. EXAMPLES: Example 1 — scan an MCP server you're evaluating: github_url = "https://github.com/modelcontextprotocol/servers" → score: 0, summary: {critical: 1, high: 94, medium: 22} → top_findings include SSRF, eval, etc. → recommendation: "AVOID — 1 critical and 94 high finding(s)..." Example 2 — scan a clean reference implementation: github_url = "https://github.com/microsoft/azure-devops-mcp" → score: 90+, summary: {critical: 0, high: 1} → recommendation: "REVIEW — 1 high finding(s)..." Example 3 — scan your own dev MCP-server before publishing: github_url = "https://github.com/yourorg/your-mcp" → audit your own surface before others install it OUTPUT FIELDS (stable schema): - repo_url (str): canonical URL of the scanned repo. - score (int): 0-100, higher safer. Coarse summary, not a precision claim. - summary (object): {critical, high, medium, low, info, files_scanned}. - recommendation (str): action guidance derived from severity counts. - findings_count (int): total raw findings (may include false positives). - top_findings (list): up to 10 most severe, each with {id, title, severity, file, line, owasp, cwe}. - l0_discovery (object): MCP transport, tool count, dependency pinning. - performance (object): clone_seconds, scan_seconds, repo_size_bytes. - scanner (object): {name, version, layers_covered}. - _disclaimer (str): MANDATORY triage disclaimer. Read it. Args: github_url: Public GitHub HTTPS URL (e.g. https://github.com/org/repo). Must be public and < 200 MB. v1 is github.com only. Returns: Structured scan result. On error, returns {"error": code, "message": ...} with HTTP-style code (invalid_url, clone_failed, scan_timeout, etc.).

  Connector

• mpp_smoke_test

  Weftly

  Smoke-test the MPP payment plumbing end-to-end via this MCP server, for $0.01 USDC. Two-call flow: (1) call with no arguments to receive an MPP `payment_challenge`; (2) pay via MPP and call again with `payment_credential` set to the resulting Authorization header value (e.g. "Payment eyJ...") to receive {paid: true, timestamp, receipt_ref, payment_method}. Uses the exact same `createPayToAddress` + `createMppHandler` verification path as paid product tools (transcribe, summarize), so a green run here means real paid calls will work too. Stateless — no job is created, no database row written. Use this whenever you want to confirm a wallet, the MCP transport, the worker, and the production payment middleware are all healthy without paying a transcribe price. Cost: $0.01 USDC per attempt.

  Connector

• record_execution

  Routescore

  Persist 1-100 already-built execution_record.v1 documents as immutable, personal-account post-trade evidence. Requires a stable idempotency_key; an exact replay returns the original result and reuse with different content fails closed. Pro tier, owner-scoped, and bounded by the MCP transport byte limit. This tool never accepts calldata, signing material, routes funds, executes a transaction, applies reviewer overrides, or exposes another tenant. Invalid rows are recorded only as redacted rejection reasons and are never echoed.

  Connector

• render_html_to_pdf

  pdfzen

  Prepare a paid PDF render from arbitrary Handlebars-flavoured HTML. Use only when no starter fits (one-off layouts, custom branding). Prefer render_template_to_pdf when a starter matches. Validates your HTML and returns the exact, ready-to-execute HTTP request to run against pdfzen's render endpoint — POST /v402/render/pdf (x402, $0.006 USDC on Base, no API key) or POST /v1/render/pdf (pdfzen API key). pdfzen renders are executed over HTTP, not streamed in-band over MCP; this tool is the bridge.

  Connector

• ateam_bootstrap

  ateam-mcp

  REQUIRED onboarding entrypoint for A-Team MCP. MUST be called when user greets, says hi, asks what this is, asks for help, explores capabilities, or when MCP is first connected. Returns platform explanation, example solutions, and assistant behavior instructions. Do NOT improvise an introduction — call this tool instead.

  Connector

• security_headers_check

  IA-QA — 130+ QA & Dev Tools for AI Agents

  Analyse the HTTP security headers of a public URL OR of raw response headers you paste in. Grades each header (A–F) for: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, X-XSS-Protection, Cross-Origin-Opener-Policy, Cross-Origin-Resource-Policy, and Cross-Origin-Embedder-Policy. Returns an overall score (0–100), per-header grades, missing headers, and fix snippets for Express, Nginx, and Apache. For localhost/private targets the remote server cannot reach, pass the `headers` parameter instead of `url`.

  Connector

• colony_vault_export

  mcp-server

  List what a vault export would contain (a download MANIFEST). Returns ``{files: [{filename, size, etag}], total_files, total_bytes, download_hint}`` — NOT the zip bytes (MCP is a text transport). ``size`` is each file's byte length; ``etag`` is the strong content ETag. Fetch ``GET /api/v1/vault/export`` (optionally ``?prefix=``) for the actual ``.zip`` archive. Optional ``prefix`` scopes to a folder/name prefix (literal "starts with"). Requires authentication. Rate limit: 120/hour (shared with search).

  Connector

• get_payment_info

  changegamer

  Return the agent payment manifest: every way to pay (HTTP 402 + Bearer key, MCP, Stripe checkout, x402, RSL per-crawl), the exact 402 retry loop, what is always free, and the recommended path per use case. Same data as /api/payment.json.

  Connector

• thread.heartbeat

  Setix: the Clearinghouse for the AI Economy

  Advance `agents.last_online_slot` for the caller. Adjacent surface to the §7/§8.5 transport QUIC Heartbeat frame: MCP-bridge callers invoke this periodically (~10s on idle) to signal presence. Caller signs Ed25519 over SHA256("setix.heartbeat.v1" || agent_id(32) || signed_slot_u64_le(8)); bridge looks up agents.pubkey from agent_id (forgery defense), verifies sig, enforces |currentSlot - signed_slot| <= HEARTBEAT_FRESHNESS_SLOTS=150 (~60s) freshness gate, then UPDATE agents.last_online_slot = GREATEST(...). Monotonic; within-window replay is harmless. Unblocks I263 BUYER_OFFLINE_DURING_ACTIVE_ESCROW sweep + I261/I261a dispute-window correction. Returns {accepted, agent_id_hex, last_online_slot}.

  Connector

• scan_site

  agent-ready-kit

  Use this when you need to assess how AI-callable a site is. Runs 19 checks (robots.txt, agent card, MCP server card, MCP liveness, llms.txt, sitemap, link headers, markdown negotiation, content signals, skill integrity, WebMCP bridge, RFC 9727 API catalog, OAuth discovery + protected-resource, auth.md, DNS-AID, Web Bot Auth, agentic-commerce), returns a level 0-5 plus per-check pass/fail with evidence and remediation pointers. Live HTTP — runs in ~3-5 seconds.

  Connector

• authority_receive_neon_402_alert

  tollbooth-authority-newengland

  Inbound: an operator reports its Neon store is 402-locked. Called MCP-to-MCP by the operator's runtime the instant it catches a Neon HTTP 402 on its own database. Verifies the operator controls ``npub`` (inline Schnorr bound to this tool's wire name), records a durable latest-state row, and fires a best-effort owner-notification DM. This is how the Authority learns the store is dark BEFORE a patron files a complaint.

  Connector

• mcp_search

  Find MCP - Agentage MCP Directory

  Search the agentage MCP directory - a public catalog of Model Context Protocol servers crawled from the official registry - for servers matching a keyword, optionally narrowed by type, category, language, or license. Use this FIRST whenever the user wants to discover, find, compare, or pick an MCP server ("is there an MCP for X", "which MCP servers do Y"). Results are ranked by text relevance to the query first, then by popularity, so the best match is on top. Returns a page of lean cards (slug, title, description, category, transport, match_score - text relevance the ranking is based on, details_url). To read one server's full packages, tools, and install command, call mcp_get with the slug from a result; open a card's details_url for the human detail page. Valid category, language, and license values come from the mcp_categories tool, not from guesswork - call it before filtering and pass its labels verbatim, or the call is rejected. Read-only - never installs or runs anything.

  Connector

• product_api

  1inch MCP

  [Requires authentication] This tool needs OAuth. If it returns an authentication error, prompt the user to connect/authenticate this MCP server (OAuth), then retry. Call any 1inch product API endpoint using the authenticated user's credentials (base URL is the unified gateway, e.g. https://api.1inch.com). Optional: if your client can read MCP resources, file://1inch-mcp/guides/api-index has live Swagger links and extra gateway notes (mirrors business.1inch.com/portal/llms.txt). Common chain IDs: Ethereum=1, BNB=56, Polygon=137, Arbitrum=42161, Optimism=10, Base=8453, Avalanche=43114, Gnosis=100, zkSync=324, Linea=59144, Sonic=146, Unichain=130, Cronos=25, Monad=10143, Solana=501 (where applicable). Gateway products (use these path prefixes with this tool): - Portfolio: /portfolio/portfolio/v5.0/... — example path="/portfolio/portfolio/v5.0/general/current_value", query={"addresses":"0x..."}; token metrics path="/portfolio/portfolio/v5.0/tokens/metrics", query={"addresses":"0x...","timerange":"1year"} - Balance: /balance/v1.2/{chainId}/... — example path="/balance/v1.2/1/balances/0x..." - Spot Price: /price/v1.1/{chainId} — example path="/price/v1.1/1", method="POST", body={"tokens":["0x..."],"currency":"USD"} - Token: /token/v1.4/{chainId}/... — example path="/token/v1.4/1/search", query={"query":"USDC"} (prefer v1.4; older v1.2 chain search is deprecated in OpenAPI) - Token Details: /token-details/v1.0/details/{chain}/{tokenAddress} — example path="/token-details/v1.0/details/1/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48" - Gas Price: /gas-price/v1.6/{chainId} — example path="/gas-price/v1.6/1" - Swap (Classic): /swap/v6.1/{chainId}/... — example path="/swap/v6.1/1/quote", query={"src":"0x...","dst":"0x...","amount":"..."} (exact query names per OpenAPI) - Orderbook: /orderbook/v4.1/{chainId}/... — example path="/orderbook/v4.1/1/all", query={"page":"1","limit":"10"} - Fusion (Intent): /fusion/orders/v2.0/..., /fusion/quoter/v2.0/..., /fusion/relayer/v2.0/... — example path="/fusion/quoter/v2.0/1/quote/receive" with required query params from spec - Fusion+ (Cross-chain): /fusion-plus/orders/..., /fusion-plus/quoter/..., /fusion-plus/relayer/... — example path="/fusion-plus/quoter/v1.2/quote/receive" with required params; equivalent routes also exist under /cross-chain/orders|quoter|relayer - History: /history/v2.0/history/{address}/events — example path="/history/v2.0/history/0x.../events", query={"chainId":"1","limit":"50","tokenAddress":"0x..."} (optional tokenAddress filters by contract; response shape uses items[].details.txHash — not raw event logs) - Traces: /traces/v1.0/chain/{chainId}/block-trace/{blockNumber}/tx-hash/{txHash} — example path="/traces/v1.0/chain/1/block-trace/18000000/tx-hash/0x..." (not /transaction/{hash}) - NFT: /nft/v2/... — example path="/nft/v2/byaddress", query={"chainIds":"1","address":"0x..."} - Charts: /charts/v1.0/chart/line/{token0}/{token1}/{period}/{chainId} — example path="/charts/v1.0/chart/line/0x.../0x.../24H/1" (period: 24H, 1W, 1M, 1Y, AllTime; not a separate timerange query) - Domains: /domains/... — example path="/domains/v2.0/lookup", query={"name":"vitalik.eth"} - Aqua (strategy analytics): /aqua/v1.0/strategies/... — example path="/aqua/v1.0/strategies/opened", query={"limit":"100"}; maker stats path="/aqua/v1.0/strategies/makers/0x.../stats". Prefer the dedicated "aqua" tool when Unleash flag mcp-service.tool.aqua is enabled; otherwise use product_api for raw HTTP. - Tx Gateway: /tx-gateway/... — example path="/tx-gateway/v1.1/1/broadcast", method="POST", body={...} - Web3 RPC: /web3/{chainId}/... — JSON-RPC over HTTP POST to an EVM (or Solana 501) node; Gateway exposes e.g. 1,10,25,56,100,130,137,143,146,324,501,8453,42161,43114,59144 — confirm availability for your org/plan. Example path="/web3/1", method="POST", body={"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]} Gotchas: Portfolio gateway path repeats "portfolio" (/portfolio/portfolio/v5.0/...) because the gateway strips the first segment. Spot Price returns WEI in native currency unless you set currency. Token list responses are large; prefer search. Token Details does not support native ETH pseudo-address 0xeeee...eeee; use WETH. Balance responses may include zero balances—filter client-side. For limit order flows (build, sign, create, cancel), prefer the "orderbook" tool. For swap execution, prefer the "swap" tool. Use product_api for direct REST access to any endpoint.

  Connector

• get_catalog_stats

  MyMCPTools

  Aggregate health of the whole MCP population: verdict breakdown, share of probeable servers actually serving, transport mix, handshake latency percentiles, tool counts and probe freshness. This is the 'how healthy is MCP right now?' headline number.

  Connector

• get_lending_application_status

  droplinked

  Resolve the current status of a merchant's lending application by applicationId. Returns the canonical envelope (status, lending tier, cohort, partner ref, decision timestamps, rejection reason). Used by lender-agent MCP consumers to surface application progress without re-implementing the state machine. Gracefully degrades to `found=false` on 404 / transport error.

  Connector