Connect Taifoon coordination layer and your agent gets 15 tools, among them taifoon_account, taifoon_buy, taifoon_chain. It answers at https://coord.taifoon.dev/mcp?ref=mcp-registry over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 27 September 2026; the last check, on 12 November 2026, succeeded.
Cross-chain V5 proofs, ERC-8004/8183 hiring, graded settlement and Grid tools over streamable HTTP
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 (pref Inputs: action, range, tile, api_key, view, window |
taifoon_buy | Buys one call of a skill the layer sells per call (x402): the best-ranked seller answers. 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 Taifoo Inputs: action, input, payment |
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 — e Inputs: action, kind, chain_id, id, txs, full_proof |
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 — o Inputs: action, need, catalog_id, class, input, price_units |
taifoon_find | 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 Inputs: action, q, class, hireable, limit, required_skills |
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 Inputs: action, items, question, options, typesafe_key, api_key |
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, p Inputs: action, model, prompt, provider, hirer, chain_id |
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 o Inputs: action, body, api_key, seller, price, price_usdc |
taifoon_observe | 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, rout Inputs: action, api_key, protocol, key, reason, src |
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 becom Inputs: op, method, params, body, api_key |
taifoon_orderbook | 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 Inputs: action, api_key, name, operator, signed_at, signature |
taifoon_prove | 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 Inputs: action, chain_id, tx_hash, kind, log_index, protocol |
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 a Inputs: action, wallet_address, agent_id, chain_id, usdc, plan |
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 — Inputs: action, card_url, chain_id, agent_id, data, nonce |
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 a Inputs: action, vault, params, api_key, armed, days |
Every block below points at https://coord.taifoon.dev/mcp?ref=mcp-registry. Pick your client and copy.
claude mcp add --transport http taifoon-coordination-layer https://coord.taifoon.dev/mcp?ref=mcp-registry
{
"mcpServers": {
"taifoon-coordination-layer": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://coord.taifoon.dev/mcp?ref=mcp-registry"]
}
}
}{
"mcpServers": {
"taifoon-coordination-layer": {
"url": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
}
}
}{
"servers": {
"taifoon-coordination-layer": {
"type": "http",
"url": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
}
}
}{
"context_servers": {
"taifoon-coordination-layer": {
"url": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
}
}
}{
"mcpServers": {
"taifoon-coordination-layer": {
"serverUrl": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
}
}
}{
"mcpServers": {
"taifoon-coordination-layer": {
"url": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
}
}
}name: Taifoon coordination layer
version: 0.0.1
schema: v1
mcpServers:
- name: Taifoon coordination layer
type: streamable-http
url: https://coord.taifoon.dev/mcp?ref=mcp-registry{
"mcpServers": {
"taifoon-coordination-layer": {
"httpUrl": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
}
}
}{
"mcpServers": {
"taifoon-coordination-layer": {
"type": "http",
"url": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
}
}
}{
"mcpServers": {
"taifoon-coordination-layer": {
"url": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
}
}
}goose://extension?url=https%3A%2F%2Fcoord.taifoon.dev%2Fmcp%3Fref%3Dmcp-registry&type=streamable_http&id=taifoon-coordination-layer&name=Taifoon%20coordination%20layer
It answered our last check on 12 November 2026 in 1295 ms. Over 4 checks since 27 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
15, as returned by the server's own tools/list on 17 November 2026: taifoon_account, taifoon_buy, taifoon_chain, taifoon_demand, taifoon_find, taifoon_grade, taifoon_grid, taifoon_hire, and 7 more.
It answered our last check on 12 November 2026 in 1295 ms. Over 4 checks since 27 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://coord.taifoon.dev/mcp?ref=mcp-registry. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.taifoon. Endpoint host: coord.taifoon.dev. ARD identifier: urn:air:io.taifoon:mcp:coordination-layer.
First indexed 27 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.