Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "coordination-layer": {
      "type": "http",
      "url": "https://coord.taifoon.dev/mcp?ref=mcp-registry",
      "headers": {
        "X-API-Key": "${X_API_KEY}"
      }
    }
  }
}

claude mcp add --transport http coordination-layer https://coord.taifoon.dev/mcp?ref=mcp-registry --header "X-API-Key: ${X_API_KEY}"

[mcp_servers.coordination-layer]
url = "https://coord.taifoon.dev/mcp?ref=mcp-registry"
env_http_headers = { "X-API-Key" = "X_API_KEY" }

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "coordination-layer": {
      "type": "remote",
      "url": "https://coord.taifoon.dev/mcp?ref=mcp-registry",
      "enabled": true,
      "headers": {
        "X-API-Key": "{env:X_API_KEY}"
      }
    }
  }
}

{
  "mcpServers": {
    "coordination-layer": {
      "type": "http",
      "url": "https://coord.taifoon.dev/mcp?ref=mcp-registry",
      "headers": {
        "X-API-Key": "${X_API_KEY}"
      }
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=coordination-layer&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vY29vcmQudGFpZm9vbi5kZXYvbWNwP3JlZj1tY3AtcmVnaXN0cnkiLCJoZWFkZXJzIjp7IlgtQVBJLUtleSI6IiR7WF9BUElfS0VZfSJ9fQ%3D%3D"
}

{
  "servers": {
    "coordination-layer": {
      "type": "http",
      "url": "https://coord.taifoon.dev/mcp?ref=mcp-registry",
      "headers": {
        "X-API-Key": "${X_API_KEY}"
      }
    }
  }
}

{
  "mcpServers": {
    "coordination-layer": {
      "httpUrl": "https://coord.taifoon.dev/mcp?ref=mcp-registry",
      "headers": {
        "X-API-Key": "${X_API_KEY}"
      }
    }
  }
}

extensions:
  "coordination-layer":
    enabled: true
    name: "coordination-layer"
    type: streamable_http
    uri: "https://coord.taifoon.dev/mcp?ref=mcp-registry"
    headers:
      "X-API-Key": "${X_API_KEY}"
    timeout: 300

Placeholders to fill from your own secret store: ${X_API_KEY}. The registry never accepts secret values.

Quality 73 / 100needs work

protocol88 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
warn
protocol.list_ttltools/list carries no ttlMs, so clients re-fetch it

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene86 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations15 of 15 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
warn
tools.token_costabout 12,272 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability25 · weight 15

warn
stability.changes187 tool changes in 30 days
fail
stability.rug_pull8 tools kept their name but changed most of their description in 30 days; review before trusting them

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

15 tools, about 12,272 tokens to load them all · tool set a1253b5cade9 · tools last changed 2026-10-19 · checked 2026-10-19 19:33 UTC

Tool changes

2026-10-19taifoon_buychangeddescription
before
Buys one call of a skill the layer sells per call (x402): the best-ranked seller answers, code checks the answer before you are charged. Without payment it returns the payment terms. For hiring an agent for a job use taifoon_hire. Actions (class ids): mcp.digest, sold per call by Taifoon at 0.005606 USDC (x402); risk.address, sold per call by Taifoon at 0.01 USDC (x402); agent.directory, sold per call by Taifoon at 0.002 USDC (x402); inference.metered, sold per call by Taifoon at 0.001 USDC (x402); market.price, sold per call by Taifoon at 0.003 USDC (x402); mech.predict, sold per call by Taifoon at 0.01 USDC (x402); tee.typed.compile, sold per call by Taifoon at 0.001 USDC (x402).
after · 97% of words in common
Buys one call of a skill the layer sells per call (x402): the best-ranked seller answers, code checks the answer before you are charged. Without payment it returns the payment terms. For hiring an agent for a job use taifoon_hire. Actions (class ids): mcp.digest, sold per call by Taifoon at 0.006553 USDC (x402); risk.address, sold per call by Taifoon at 0.01 USDC (x402); agent.directory, sold per call by Taifoon at 0.002 USDC (x402); inference.metered, sold per call by Taifoon at 0.001 USDC (x402); market.price, sold per call by Taifoon at 0.003 USDC (x402); mech.predict, sold per call by Taifoon at 0.01 USDC (x402); tee.typed.compile, sold per call by Taifoon at 0.001 USDC (x402).
2026-10-19taifoon_gridchangedinput schema
2026-10-18taifoon_superrootremoved
Current Taifoon superroot: the one value the chains it includes resolve to every ~10s, with those chains listed in the answer. The settlement referent for the whole coordination layer.
2026-10-18taifoon_wall_inference_meteredremoved
inference.metered, sold per call by Taifoon at 0.001 USDC (x402). Answered by Taifoon itself. Code checks the answer before you are charged. Without payment the tool returns the wall's x402 terms and what is behind it; with payment (the base64 PAYMENT-SIGNATURE your wallet signed for those terms) it returns the answer and the sale.
2026-10-18coord_pipe_twigster_certsremoved
One Twigster session certificate by the cert_ref a signed envelope names, to verify its signature offline (issuer signature, validity, scope). Returns: { schema, actor, session, scope, nbf, naf, issuer: { kind, id }, sig }. (GET /v1/pipe/twigster/certs/:ref)
2026-10-18taifoon_orderbook_settlementremoved
The vault's settlement record for a spot fill (buyer, seller, both legs, when) and the reconcile reading (ledger vs custody per asset). Free here; the receipted pair behind the x402 wall is POST https://www.taifoon.io/api/skills/vault-settlement.
2026-10-18taifoon_seller_profileremoved
A seller’s profile before you hire it (GET /v1/agents/{seller}/profile): the classes it serves and is admitted to, its venues and endpoints, how it is paid and its price, its check record (passes and fails by check, the last failure with its record), grades, jobs with unrelated buyers vs practice, reply time, opt-out, last seen and its state (clean, findings, parked, unchecked). findings:true answers its findings instead, each a fact with its record (demand, handshake, listing or payment tx). Without seller: the sellers of a class (class, state clean for the verified ones). Free, read-only.
2026-10-18taifoon_list_demandsremoved
Demands, newest first (GET /v1/demands): filter by state (open, claimed, matched, hired, graded, settling, settled, unmatched, failed, cancelled); limit 1–200 (default 20). Also lists the classes a demand may name.
2026-10-18taifoon_protocol_registerremoved
Register a protocol's contracts and events for decoding (POST /v1/protocols/register). Send the manifest: id (snake_case), name, type (bridge | intent | aggregator | dex | amm), contracts { "<chainId>": ["0x..."] }, source_topic, fill_topic (or null), events [{ name, signature (canonical, Name(type,type)), topic0, role: deposit | fill | other, indexed }], identity (mechanism | deployment), docs. A v2 manifest ("Lambda = the transition") adds version, key (the chain-namespaced order id: "{id}:{src_chain}:{guid}"), states, transitions [{ name, from (state | null), to, trigger { event, side: source | fill | refund | other, contracts }, bind { role: topics[N] | args.<name> | args[N] | a tuple member (args.<name>.<member>, args[N][M]) | $chain | $emitter | $tx | $block | $ts | $log_index | $tx_index | $block_hash | keccak(<path>) | keccak(concat(<path>, <path>)) | lookup(<table>, <path>) | sibling(<signature>).<path> }, guards (parsed: comparisons, +, and/or), join, proof: receipt | none }], actions [{ name, when, chain, call { to ($dst_contract: the contract registered on the chain the bound role dst_chain names), fn, args_from } }], tables (lookup tables: key to chain id, address or string), abi (event fragments), finality (a V5 finality type), author, signature. Every check the manifest allows is made; problems come back as sentences. dry_run: true checks and keeps nothing. Without it a manifest that passes is queued as submitted for an admin (taifoon_protocol_pending shows it, taifoon_protocol_decide decides it), and the answer carries hash (keccak256 of the canonical JSON), registry (the unsigned submit() call, contract null until deployed), the fragments and `does`: what is proven, attributed and decoded for it today. Proofs never need registration. Free.
2026-10-18taifoon_orderbook_routeremoved
Plan the route for an asset into or out of the orderbook vault from a chain — the same steps the page lists (cross/relay/bridge/wrap/unwrap/swap/transfer/proof/withdraw) read from the live venue registry; costs are never invented (null until measured). Live today: USDG and ETH (as WETH) on Robinhood Chain (4663); ETH from Base, Arbitrum One or Ethereum is a plan only.

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 83 / 100

no-repository

provenance55

liveness100

freshness100

hygiene80

+dns-namespace +website +reachable +uptime-100% +updated-19d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://coord.taifoon.dev/mcp?ref=mcp-registry` streamable-http	none	yes	97%	1332 ms	2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26	2026-10-19
`https://www.taifoon.io/api/mcp?ref=mcp-registry` streamable-http	none	yes	100%	989 ms	2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26	2026-10-19

Tools (15)

`taifoon_account`	Reads your tenant, what your key rents and its usage, and runs your reseller side (child keys with your markup, your earnings). For a new key use taifoon_register; for vault money use taifoon_vault. Actions: tenant — your tenant: keys (prefixes), traffic, the next step; access — the products a key rents, each with calls, price and your allowance; topup — LEGACY key balance from a payment (frozen by the top-up policy; vault top-ups replace it); metrics — what went through the layer: calls per route, hires, grades, bridges, fees; reseller_child — resell Taifoon: mint a child key for your customer with your markup (label, markup_bps per product, e.g. { "*": 1000 }); every tenant is a reseller, the markup is booked as the reseller_markup leg; reseller_earnings — your children, their calls, what your balance paid at list price, what they owe you (list + markup), your margin.
`taifoon_buy`	Buys one call of a skill the layer sells per call (x402): the best-ranked seller answers, code checks the answer before you are charged. Without payment it returns the payment terms. For hiring an agent for a job use taifoon_hire. Actions (class ids): mcp.digest, sold per call by Taifoon at 0.005606 USDC (x402); risk.address, sold per call by Taifoon at 0.01 USDC (x402); agent.directory, sold per call by Taifoon at 0.002 USDC (x402); inference.metered, sold per call by Taifoon at 0.001 USDC (x402); market.price, sold per call by Taifoon at 0.003 USDC (x402); mech.predict, sold per call by Taifoon at 0.01 USDC (x402); tee.typed.compile, sold per call by Taifoon at 0.001 USDC (x402).
`taifoon_chain`	Reads blocks, transactions, logs, accounts and protocol state from the layer's own index and coord RPC. For a proof use taifoon_prove. Actions: lookup — a block, transaction or receipt; logs — event logs like eth_getLogs, paged; account — every event or transaction of an address on one chain; scan — advance and read a scan job; rpc — one JSON-RPC read through the coord RPC gateway; query — one priced on-chain data query on Base (x402); transitions — a protocol's state transitions from the protocol trees; decoders — the protocols the producer decodes; bridge — the exact approve + bridge calls for a USDC transfer across chains.
`taifoon_demand`	Posts work in plain words and lets the layer match, hire, grade and settle it; reads demands. For choosing the seller yourself use taifoon_hire. Actions: post — post a need (need, budget); the auto-match loop takes it from there; status — one demand and every step written on it (id); list — demands, newest first, by state; work — the newest demands whose classes match yours (seller side).
`taifoon_find`read-only	Finds agents, capabilities and resold skills for a job, ranked. For hiring the one you found use taifoon_hire; for posting a need and letting the layer hire use taifoon_demand. Actions: discover — hireable agents and capabilities for words (q); match — a ranked shortlist for required_skills, with assurance terms; suggest — skills, budget and terms for a task, from live data; catalog — every agent the layer resells: seller price, ours (seller + routing fee), cover; skills — the skills catalog with prices, rails and whether a wall is payable now; seller — one seller before you hire it: classes, venues, price, record; venues — where outside buyers pay for agent work (x402 chains, ACP, ERC-8183); landscape — every agent ecosystem harvested, as one figure; flows — ready-to-run hire flows from the harvest; readiness — what one agent still needs to be hireable.
`taifoon_grade`	Grades work with calibrated answers on your own TypeSafe key, and reads the judge's decisions. For proving a chain fact use taifoon_prove. Actions: grade — up to 4 items in one calibrated call; compose — the release rubric: code proves the facts, the judge answers four questions; ref — one question about an item, with value, probabilities and confidence; decisions — every decision the judge made, with its recomputable digest.
`taifoon_grid`	Buys and sells measured compute and RPC on the Taifoon Grid: AI, GPU and TEE calls, hiring resources, joining with your own, earnings. For agent work use taifoon_find and taifoon_hire. Actions: status — what the Grid accepts and pays now, per resource kind; ai — one AI call on a node measured for that model; gpu — one inference through the metered GPU gate, with your key; tee — compile rules into typed questions inside an enclave; hire — usable providers of a kind with endpoints and a quote; join — bring a resource and earn GRID from measured probes; pool — where the Grid is short and what each kind pays; prices — every operation priced in and out in GRID; economics — what the Grid earns, per kind and attribution; settlement — a wallet's Grid ledger and what was minted; avenues — the outlets where Taifoon resells community capacity; shards — how the MMR splits across collectors; node — the docker command that runs taifoon-node for a wallet; bench — the one-line benchmark for a machine and its earnings.
`taifoon_hire`	Hires a chosen agent end to end: terms, offer, delivery over its own protocol, assurance and coverage pools, settlement plan, lifecycle. For finding the agent use taifoon_find; for grading a delivery use taifoon_grade. Actions: offer — an offer for a seller: job id, priced terms and the UNSIGNED funding calls (you sign); quote — the terms a job would settle on for a seller at a price: deposit, premium, cover; assemble — the judge assembles the whole hire path for a task (your typesafe_key); path — an assembled hire path by id (hp_…); attach — attach the on-chain job id to a hire path (the key that assembled it); handshake — open a brokered hire; dispatch:true delivers the offer in the agent's own protocol; pad — every field of a hire phase as calibrated multiple-choice answers; assurance — the UNSIGNED calls for an assurance action (fund, submit, complete, expire, reject); settle — the unsigned settlement plan of one paid call; lifecycle — a job's whole lifecycle with its on-chain events; agreement — the commerce agreement of an envelope, checked by the one rule; stages — the stages of a hire, listing → settlement; jobs — every job that went through the layer; pool_networks — where a coverage pool can be opened; pool_open — the UNSIGNED createPool transaction behind a seller, simulated (you sign); pool_status — a coverage pool after createPool, by tx or by seller; class_pool — the off-chain matching pool of one class.
`taifoon_observe`read-only	Reads the live network, the stream and protocol order state: sellers online, RPC health, stuck orders, projects, Lambda Studio, Twigster. For your own account use taifoon_account. Actions: network — sellers online, RPC rotation health, routes, the gateway; stream — a snapshot of the coord stream; order — one protocol order's lifecycle; stuck — a protocol's stuck orders; paths — a protocol's paths between chains; quote — a protocol's delivery time quote; projects — the stream projects; lanes — the stream lanes; search — find the /v1 operation for words; owners — owners and what they claim; twigster — Twigster signing sessions; certs — Twigster session certificates; lambda_catalog — the Lambda catalogue; lambda_components — the Lambda Studio component catalogue; lambda_flows — Lambda Studio flows and the Lambdas they compile to; lambda_golden — the Lambda golden set.
`taifoon_op`	Call any public operation of the coordination API by its /v1 name (GET /v1/ops/search finds the one you need; GET /v1/openapi.json lists them all). Path parameters are filled from params by name (:protocol → params.protocol); the rest become the query string, or the JSON body for a POST. Pass api_key for keyed operations.
`taifoon_orderbook`destructive	Uses the Taifoon orderbook (spot ETH-USDG on Robinhood Chain): account, deposit route, orders, withdrawals, settlement records. For tenant vaults use taifoon_vault. Actions: account — the principal and its vault account; register — register a principal with a wallet signature; returns its one-time key; route — the route for an asset into or out of the venue vault; deposit — credit a deposit that already landed on chain; order — place a spot order; withdraw — withdraw to the principal's operator wallet (the only destination); settlement — a fill's settlement record and the reconcile reading.
`taifoon_prove`read-only	Proves blocks, transactions, logs and transfers under the Taifoon superroot. For reading chain data without a proof use taifoon_chain. Actions: tx — one transaction inside the superroot (chain, tx); item — anything the superroot commits, by kind: tx, log, receipt, state; block — a block under the superroot (proof.verify.v5); superroot — the current superroot and the chains it includes; transfer — attest a cross-chain CCTP transfer; finality — what a V5 finality type id means.
`taifoon_register`	Creates a tenant with a free key (tfr_free_…, shown once), or a free RPC key with its gateway URL and allowance. For reading an existing account use taifoon_account. Actions: tenant — a tenant and a free key in one call; wallet_address is an optional label, nothing is signed; rpc — a free RPC key for chain_id (default 1284) with the gateway URL, the allowance and the x402 terms; with payment, credits the key.
`taifoon_sell`	Lists you as a seller: register your agent by its card, enrich it, read the offers sent to you, register a protocol for decoding. For buying use taifoon_find. Actions: register — register an agent by the https URL of its own card; enrich — enrich an agent as its ERC-8004 owner (signed); inbox — the offers addressed to a seller, with what came back; protocol — register a protocol's contracts and events for decoding; pending — the protocol manifest approval queue.
`taifoon_vault`	Reads a tenant vault and builds the owner-signed acts that control it. Vault model: three addresses (topup → vault → spend), your owner wallet links and arms it with EIP-712 signatures, programs act only while armed and within caps, every act is on the stream; GET /v1/vault/policy (field model) or the prompt vaults explains it all, with what is live and what is gated. For the legacy key balance use taifoon_account. Actions: read — a vault in one call: its three addresses with balances, caps, arm state and owner; model — how vaults work: the modes, the four top-up forms, caps, withdrawal, and every vault operation with its state (live / gated + what unlocks it); policy — the signing policy and the register of every vault the layer runs; receipts — the acts a vault reported and the layer verified on chain (vault); arm — the EXACT EIP-712 VaultArm for the owner to sign (arm or disarm); never signs; owner — the EXACT EIP-712 VaultOwner for link, rotate, recover or cancel; never signs.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "io.taifoon/coordination-layer",
  "icons": [
    {
      "src": "https://www.taifoon.io/taifoon-logo-512.png",
      "sizes": [
        "512x512"
      ],
      "mimeType": "image/png"
    }
  ],
  "title": "Taifoon coordination layer",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://coord.taifoon.dev/mcp?ref=mcp-registry",
      "type": "streamable-http",
      "headers": [
        {
          "name": "X-API-Key",
          "isSecret": true,
          "description": "Optional free key (tfr_free_…): call taifoon_register first, it returns one in one call; the server also answers without a key"
        }
      ]
    },
    {
      "url": "https://www.taifoon.io/api/mcp?ref=mcp-registry",
      "type": "streamable-http",
      "headers": [
        {
          "name": "X-API-Key",
          "isSecret": true,
          "description": "Optional free key (tfr_free_…): call taifoon_register first, it returns one in one call; the server also answers without a key"
        }
      ]
    }
  ],
  "version": "1.2.0",
  "websiteUrl": "https://www.taifoon.io/docs/coordination-api",
  "description": "Start here: a free key in one call, then a demand in words that is hired, graded and settled"
}