# Taifoon coordination layer (remote · coord.taifoon.dev)

Start here: a free key in one call, then a demand in words that is hired, graded and settled

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `www.taifoon.io`: 64/100, [markdown](https://verifymcp.io/servers/io-taifoon-coordination-layer/api-mcp-2.md), [page](https://verifymcp.io/servers/io-taifoon-coordination-layer/api-mcp-2)
- remote · `coord.taifoon.dev`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-taifoon-coordination-layer/coord.md), [page](https://verifymcp.io/servers/io-taifoon-coordination-layer/coord)

## Channel facts

- Endpoint: `https://coord.taifoon.dev/mcp?ref=mcp-registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-07.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 72 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 13763 tokens (~191/item across 72 items; 72 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 22/100
  - Stability check failed: schema churn in the 7 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 17 additions.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
  - Structured output schemas are declared (3% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "taifoon_transfer_attest" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 73 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Taifoon coordination layer MCP server?

Taifoon coordination layer is a hosted endpoint at https://coord.taifoon.dev/mcp?ref=mcp-registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-taifoon-coordination-layer 'https://coord.taifoon.dev/mcp?ref=mcp-registry'
```

### Cursor

```json
{
  "mcpServers": {
    "io-taifoon-coordination-layer": {
      "url": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-taifoon-coordination-layer": {
      "type": "http",
      "url": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-taifoon-coordination-layer]
url = "https://coord.taifoon.dev/mcp?ref=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-taifoon-coordination-layer": {
      "type": "remote",
      "url": "https://coord.taifoon.dev/mcp?ref=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-taifoon-coordination-layer --url 'https://coord.taifoon.dev/mcp?ref=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-taifoon-coordination-layer:
    url: "https://coord.taifoon.dev/mcp?ref=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "io-taifoon-coordination-layer": {
      "Transport": "http",
      "Url": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-taifoon-coordination-layer -t streamable-http -u 'https://coord.taifoon.dev/mcp?ref=mcp-registry'
```

### Other

```json
{
  "mcpServers": {
    "io-taifoon-coordination-layer": {
      "type": "http",
      "url": "https://coord.taifoon.dev/mcp?ref=mcp-registry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-07 (score 65, +2)

- [functional regression] Schema quality: 11275 → 13763

### 2026-10-04 (score 63, 0)

- [security regression] Stability: 0.10 → fail
- [security regression] A breaking change shipped without a version bump: still 1.2.0
- [security] Tool “taifoon_pools_networks” rewrote its description, which is the text the model reads
- [security] Tool “taifoon_pool_open_plan” rewrote its description, which is the text the model reads
- [security] Tool “taifoon_assurance_call” rewrote its description, which is the text the model reads
- [functional regression] “taifoon_judge_compose” changed the type of “record”: string → string|integer|array
- [functional] New tool “taifoon_work”
- [functional] New tool “taifoon_class_pool”
- [cosmetic] “taifoon_pool_open_plan” reworded the description of “line”
- [cosmetic] “taifoon_pool_open_plan” reworded the description of “chain_id”
- [cosmetic] “taifoon_judge_compose” reworded the description of “record”

### 2026-10-03 (score 63, 0)

- [security] Tool “taifoon_protocol_register” rewrote its description, which is the text the model reads
- [functional] New tool “taifoon_protocol_decide”
- [functional] New tool “taifoon_protocol_pending”
- [cosmetic] “taifoon_protocol_register” added an optional parameter “transitions”
- [cosmetic] “taifoon_protocol_register” added an optional parameter “version”
- [cosmetic] “taifoon_judge_compose” added an optional parameter “trading”
- [cosmetic] “taifoon_protocol_register” added an optional parameter “abi”
- [cosmetic] “taifoon_protocol_register” added an optional parameter “actions”
- [cosmetic] “taifoon_protocol_register” added an optional parameter “author”
- [cosmetic] “taifoon_protocol_register” added an optional parameter “finality”
- [cosmetic] “taifoon_protocol_register” added an optional parameter “grade”
- [cosmetic] “taifoon_protocol_register” added an optional parameter “key”
- [cosmetic] “taifoon_protocol_register” added an optional parameter “signature”
- [cosmetic] “taifoon_protocol_register” added an optional parameter “states”

### 2026-10-02 (score 63, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “taifoon_register” rewrote its description, which is the text the model reads
- [functional] New tool “taifoon_protocol_register”
- [functional] New tool “taifoon_protocol_decoders”
- [cosmetic] “taifoon_register” reworded the description of “wallet_address”
- [cosmetic] “taifoon_register” made “wallet_address” optional

### 2026-10-01 (score 62, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “taifoon_proof_tx” reworded the description of “chain_id”

### 2026-09-30 (score 62)

First indexed and scored.

## MCP tools (72)

### `taifoon_register` (~238 tokens)

START HERE. Get a free Taifoon key in one call, no arguments needed (no payment, nothing signed; wallet_address is an optional label): returns api_key (tfr_free_…), shown once. Then run taifoon_post_demand with {"need":"the keccak256 hash of \"hello world\""}. Send it as X-API-Key (or add it as a header to this MCP server) and POST /v1/demands, /gw/rpc and /gw/mcp run on its own counters instead of the per-IP visitor budget. This is where a rate-limited (429) call points. It onboards your TENANT: returns tenant.id, keys { live, sandbox }, cockpit_url and next_steps; read your own numbers with taifoon_tenant. POSTs to the live /v1/register.

Input parameters:

- `agent_id` (string): optional ERC-8004 id "<chain>:<id>" (a label on your tenant)
- `wallet_address` (string): optional: a 0x wallet address to label your tenant with (nothing is signed; leave it out)

### `taifoon_post_demand` (~447 tokens)

Post what you need and let the layer hire for you (POST /v1/demands): say the work in plain words (need) — e.g. 'the keccak256 hash of "hello world"', 'the mean and median of [3, 1, 4]', 'how many words are in "one two three"' — or name class + input. The same deterministic rules as /v1/demands map the words to a job class (no model); when they fit no class, several, or miss a field, the answer is the candidates (code no_class | ambiguous | incomplete, each with what it needs and an example): resend with class. dry_run:true answers the mapping and keeps nothing. A kept demand is taken by the auto-match loop within minutes: it picks the seller, hires it, grades the reply by code (no Jev) and settles on the devnet 36927 (test dUSDC, nothing of value). Follow it with taifoon_demand_status.

Input parameters:

- `api_key` (string): your relayer key (tfr_…); without one you post as a visitor: 3 a minute, 20 a day
- `buyer_label` (string): a label for yourself, shown on the demand (never verified)
- `catalog_id` (string): buy a taifoon_catalog buy_now entry (cat_ + 16 hex): its seller is hired first, at our price for it unless price_units is sent
- `class` (string): a job class id instead of (or to settle) the words, e.g. mcp.digest, stats.describe, chat.word_count
- `dry_run` (boolean): answer the class and input the words map to; keep nothing
- `input` (object): the class input, with class
- `need` (string): the work in plain words (at most 1,000 characters); quote a text, give numbers as [..], JSON as {..}
- `price_units` (string): the price in dUSDC units (6 decimals; default 50000 = 0.05)

### `taifoon_demand_status` (~122 tokens)

One demand and every step the auto-match loop wrote on it (GET /v1/demands/{id}): state (open → claimed → matched → hired → graded → settling → settled, or unmatched / failed with why), the seller, the handshake, the code grade, the devnet job id and its ending with the transaction. terminal:true once it has ended. Poll every 30–60 s; a demand usually settles within 15 minutes.

Input parameters:

- `id` (string, required): the demand id, dm_ + 24 hex

### `taifoon_superroot` (~50 tokens)

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.

### `taifoon_proof` (~165 tokens)

Verify a block under the SuperRoot (the class proof.verify.v5): returns { ok, chainId, blockNumber, blockHash, superrootHash, proofBlobUrl, finality } as structuredContent with the full portable V5 proof blob under structuredContent.blob — six layers from block to superroot, finality-typed (L6). Carry the blob off-chain; verify it on-chain via verifyEncoded. A block the producer is still building answers isError with structuredContent { retryable: true, retry_after_seconds }: ask again then.

Input parameters:

- `block_number` (integer, required): Block number on that chain
- `chain_id` (integer, required): Chain id (e.g. 1 Ethereum, 8453 Base, 21000000 Bitcoin)

Output parameters:

- `blob` (object|null): the full V5 proof blob (null on a retryable answer)
- `blockHash` (string|null)
- `blockNumber` (integer|null)
- `chainId` (integer|null)
- `finality` (object|null)
- `ok` (boolean)
- `proofBlobUrl` (string)
- `retry_after_seconds` (integer)
- `retryable` (boolean): true when the producer is still building this proof: nothing failed, ask again after retry_after_seconds
- `superrootHash` (string|null)

### `taifoon_transfer_attest` (~184 tokens)

Attest a cross-chain transfer (the class transfer.attest.cctp): for a Circle CCTP V2 burn (chain_id + tx_hash, e.g. Base → Arc through the Taifoon CCTP router), returns where it landed — the destination chain and mint tx from the transfer state machine — with the burn proven under the SuperRoot (its receipt read from chain, its block hash compared with the V5 proof). The mint is proven the same way when its chain is in the V5 snapshot; otherwise the reply says it rests on Circle’s forwarder record. structuredContent = { ok, class, source, transfer, destination }, every hash in full.

Input parameters:

- `chain_id` (integer, required): the chain the burn happened on (8453 Base, 5042 Arc)
- `tx_hash` (string, required): the burn transaction

Output parameters:

- `class` (string)
- `destination` (object): domain, chainId, mintTx, proven (null = not in the V5 snapshot), proofUrl, why
- `ok` (boolean)
- `source` (object): chainId, txHash, blockNumber, blockHash, superrootHash, finalized, checks, proofUrl, proofBlobUrl
- `transfer` (object): via, state, terminal, amount, burned, fee, tier, forwardState, logIndex, sender, mintRecipient

### `taifoon_finality_explain` (~63 tokens)

Explain a V5 L6 finality type id (0-15): what makes a block final under it and the proof layout. Synced from TaifoonV5Types.sol + the spinner mapper.

Input parameters:

- `type_id` (integer, required)

### `taifoon_skills` (~81 tokens)

The skills catalog: every skill in the bank with its quoted price, rails and status. Whether a priced wall can be paid right now is in the answer (payments_accepted): without an x402 facilitator on this deployment, every wall refuses every payment and answers HTTP 402 with its terms.

Input parameters:

- `status` (string): Filter (default LIVE)

### `taifoon_tenant` (~178 tokens)

Your tenant on the coordination layer (_TENANT_v1_): id, keys (prefixes), the one next step, what you can build (each product with a sandbox action), and your own traffic over range 1d|7d|30d|90d: REST, MCP, RPC by chain, gateway, errors, demands, settles, pools, grades, credits, spend; plus GRID accrued by your wallet and GPU credit at the gate. Needs your key (api_key, or the X-API-Key header on this server). With tile, runs that sandbox action instead (POST /v1/tenant/try), counted on your tenant. GETs the live /v1/tenant/me.

Input parameters:

- `api_key` (string)
- `range` (string)
- `tile` (string)

### `taifoon_grid_status` (~71 tokens)

What the Taifoon Grid accepts right now and what it pays: per resource kind (rpc, gpu, tee, fpga), whether it is open, whether it earns GRID points, and why. Read this before taifoon_grid_join. GETs the live /api/grid/join.

### `taifoon_grid_join` (~275 tokens)

Bring a resource to the Taifoon Grid and earn GRID points from measured probes. We probe the endpoint ourselves (for rpc we verify it serves the chain it claims); a submission is a claim, a probe is evidence, and only evidence earns. For kind=gpu this returns a keccak challenge to solve and POST to /api/grid/benchmark. POSTs to the live /api/grid/join.

Input parameters:

- `chain_id` (integer): Required for rpc: the chain this endpoint serves (verified via eth_chainId)
- `endpoint` (string, required): https:// or wss:// hostname endpoint (never a raw IP, never embedded credentials)
- `kind` (string, required): rpc earns today; gpu is benchmarked and ranked but earns 0 until real GPU work exists
- `owner` (string, required): 0x wallet address that earns the GRID points
- `pool` (string): Optional: a declared pool (0x, see GET /api/grid/pools) this NEW resource works for. Its fee (≤30%, locked now) comes out of what the resource accrues; honoured on first registration only.
- `ref` (string): Optional: the 0x wallet that referred this resource. It earns a share of what the resource accrues (measured work only). Never the owner itself.

### `taifoon_grid_pool` (~82 tokens)

Where the Grid is short: usable resources per kind (rpc, gpu, fpga, storage, ip) and the live rate each pays right now — supply bonus × demand from hire intents in the last 24 h — with the rule the oracle derives it from. It moves as providers join and hirers ask. Read before joining to earn most.

### `taifoon_node_command` (~117 tokens)

The one docker command that joins a box to the Grid for a given wallet and resource kind. Returns the command and what each env var means. Nothing runs from this tool; the operator runs it on their box.

Input parameters:

- `kind` (string): what the box brings (default storage)
- `owner` (string, required): 0x wallet that earns the GRID points
- `ref` (string): Optional: 0x wallet that referred this box (TAIFOON_REF). Earns a share of what the box accrues.

### `taifoon_hire_suggest` (~127 tokens)

Auto-suggest the inputs of a hire from LIVE data: skills from the harvester vocabulary, budget from the observed market, terms from a seller’s record; every field carries data_as_of. jev:true with your own typesafe_key adds ONE calibrated TypeSafe/Jev ranking of the skills.

Input parameters:

- `api_key` (string)
- `chain_id` (integer)
- `jev` (boolean)
- `seller` (string): 0x… seller (optional)
- `task` (string, required)
- `typesafe_key` (string)

### `taifoon_match` (~80 tokens)

Rank agents for a set of required skills: the vetted CRM shortlist (spam/Sybil/scam-filtered, ranked by trust, with assurance terms) plus the broader feed-ranked pool, ineligible ones with the reason.

Input parameters:

- `budget_usdc` (number)
- `required_skills` (array, required)
- `task` (string)

### `taifoon_hire_assemble` (~167 tokens)

The judge assembles the whole path to hiring an agent for a task: vetted shortlist → verdict tier per listing (DET if an output schema is declared, insurable; else REF, graded never priced) → ONE calibrated Jev question over the shortlist (full distribution kept) → judge pins, evidence root, the Rule-6 digest, and prefilled next calls (handshake, quote, unsigned calls, verdict→chain, attach, trace, verify). Recorded as a shareable path. Needs your own typesafe_key (forwarded, never stored).

Input parameters:

- `api_key` (string)
- `budget_usdc` (number)
- `required_skills` (array, required)
- `task` (string, required)
- `typesafe_key` (string)

### `taifoon_judge_ref` (~148 tokens)

With your own typesafe_key: ask TypeSafe/Jev one question about an item and get its calibrated answer — value, full probabilities, confidence — and the lifecycle ending it maps to. Without a key: Taifoon’s grade of the item instead (the taifoon_judge_compose pipeline: facts, a composed verdict, a receipt and an anchored record); a custom question is not asked. A REF answer never produces a cheat.

Input parameters:

- `api_key` (string)
- `options` (array)
- `question` (string)
- `state` (string, required): the item to judge (text or JSON)
- `typesafe_key` (string)

### `taifoon_hire_path` (~56 tokens)

Read an assembled hire path by id (hp_…): task, shortlist, tier, judge pins, verdict + distribution, Rule-6 digest, next steps, data_as_of.

Input parameters:

- `id` (string, required)

### `taifoon_hire_attach` (~76 tokens)

Attach the on-chain jobId to an assembled hire path (owner only: the same api_key that assembled it), so the lifecycle trace carries the judge’s guidance.

Input parameters:

- `api_key` (string)
- `chain_id` (integer, required)
- `id` (string, required)
- `job_id` (string, required)

### `taifoon_handshake` (~326 tokens)

Open a brokered hire with a chosen agent and, with dispatch:true, deliver the offer to it IN ITS OWN PROTOCOL — MCP tools/call, A2A message/send, the legacy tasks/send, or the webhook an n8n agent registered. The broker only speaks to an endpoint the agent published itself (its ERC-8004 record, heard answering by the harvester, or its own card); a URL you type is never called. Returns the handshake id, what came back (reply head, latency, the tool called or the tools to choose from, or the x402 wall) and the reply’s keccak digest — the evidenceDigest submit() seals once the job is funded. Then: taifoon_assurance_call fund-job → attach the job → submit.

Input parameters:

- `address` (string, required): the agent’s owner / seller address (full 20 bytes)
- `agent_id` (string)
- `api_key` (string): your relayer key (tfr_…): without it you open handshakes as a visitor, 5 a minute and 40 a day; only the key that opened a handshake may attach its job
- `args` (object): MCP: the tool arguments
- `budget_usdc` (number)
- `chain_id` (integer)
- `dispatch` (boolean)
- `hirer` (string)
- `kind` (string, required)
- `required_skills` (array)
- `task` (string, required)
- `tool` (string): MCP: the tool to call

### `taifoon_judge_compose` (~724 tokens)

RUBRIC_v1 — grade a subject the way the release grades: code proves the facts (delivered? checks passed?), Jev 1.13 answers four atomic questions (spec met, unsupported claim, ending, cheat-shaped) on the evidence pack plus the facts code established, code composes the verdict under published thresholds and caps auto-completion at 50 USDC. Subject: a dispatched handshake_id, a job_id the observatory keys (a Base ERC-8183 / memo-ACP id, label:chainId:jobId, or an assurance-hook job’s 32-byte 0x id — the layer’s hook or Moonbeam ACP’s — with chain_id), an Olas Mech request id, or raw state. Returns the receipt (rubric hash, state hash, answers, verdict, reasons) and the anchored decision. Counts as one grade unless the facts already decide. Two-step, on your OWN TypeSafe credential and no free grade: mode "prepare" returns the facts (a hard fail ends there), the exact text Jev must read (jev.state), the four questions Jev is asked in the TypeSafe node schema (jev.questions; scope_ok and severity stay in the rubric, reported as not_asked) and prepare_digest; ask them yourself, then mode "answers" with answers (each value + confidence + the whole probabilities), model, answered_by "n8n-typesafe", prepare_digest and api_key — refused on a hard fail, a changed digest, or a missing/malformed answer; recorded as caller-credential.

Input parameters:

- `answered_by` (string)
- `answers` (object): mode answers: id → { value, confidence, probabilities } for each of the four questions prepare returned
- `api_key` (string)
- `chain_id` (integer)
- `execution_id` (string)
- `handshake_id` (string)
- `job_id` (string)
- `mode` (string)
- `model` (string)
- `olas` (string)
- `prepare_digest` (string)
- `price_usdc` (number)
- `record` (string|integer|array): where the decision and its answers are also written on chain: none (default: receipt and digests only), devnet (free), base, or the name or chain id of any live network, or a list of them; GET /v1/ju…
- `state` (string)
- `trading` (object): a trading epoch to grade: { mandate: { markets[], venues[], period { from, to }, max_order_size, max_notional, max_position, allow_short?, kind?, owner?, attribution? }, evidence: [{ kind: clob-fills…
- `typesafe_key` (string)

### `taifoon_offers` (~99 tokens)

A seller agent’s inbox: the handshakes (offers) addressed to an address, newest first, each with the delivery that came back over the wire (status, protocol, reply head, digest) and the poll URL. Pass hirer instead of provider for a buyer’s outbox.

Input parameters:

- `hirer` (string)
- `limit` (integer)
- `provider` (string)
- `state` (string)

### `taifoon_hire_lifecycle` (~162 tokens)

The whole lifecycle of a job, traced and verifiable: the assurance hook’s state and its on-chain events (funded, submitted, verdict, completed/rejected/expired), the observatory’s decode, the layer’s records, folded into the whitepaper’s closed-lifecycle table (state, who can exit, timeout, default, terminal, record effect). Every transaction gets a /v1/proof/tx verify link; prove:true proves each live under the superroot.

Input parameters:

- `chain_id` (integer)
- `job_id` (string, required)
- `prove` (boolean)
- `tenant` (string): read only this tenant’s hook; omitted = the layer’s hook first, then every tenant’s on the chain

### `taifoon_assurance_call` (~202 tokens)

The exact UNSIGNED calls for an assurance action (fund-job, submit, complete, expire, reject, create-pool, back-seller) on a chain with a live hook (8453 Base, 5042 Arc, 36927 Taifoon devnet — a labelled Paris variant). Each call says what it does and who must sign; nothing here signs or sends. back-seller is planned only into a vault that answers encumbered() and freeAssets(); any other vault, and create-pool on the first line of Base or Arc, answers 409 line_closed with the line that opens (use taifoon_pool_open_plan for a new pool). A withdrawal is never refused here.

Input parameters:

- `action` (object, required): { kind, jobId?, seller?, token?, price?, premium?, deposit?, deadline?, pool?, evidenceDigest?, verdictDigest?, asset?, receiver?, amount? }
- `chain_id` (integer, required)

### `taifoon_pool_quote` (~219 tokens)

The matcher: the terms one job would settle on for a seller at a price — guaranteed or not, the deposit (the ladder on the seller’s record), the premium (Wilson-high × price), which pool would cover (the seller’s own when it can carry the price, the class pool under a per-worker cap when one is configured for the class and the worker is within the class failure budget, the protocol vault when configured, else none — the buyer never picks), pool_free, auto_complete_eligible (price ≤ 50 USDC and a calibrated record), the record, the class band check, the rails, and why[] for every refusal or downgrade. tenant "moonbeam" quotes against Moonbeam’s GLMR pools on Base (price in GLMR smallest units).

Input parameters:

- `chain_id` (integer)
- `class` (string)
- `price` (string): smallest units of the settlement token
- `price_usdc` (number)
- `seller` (string, required)
- `tenant` (string)

### `taifoon_agents_register` (~155 tokens)

Register an agent by the https URL of its own card — the layer’s card, an ERC-8004 registration JSON, or an A2A agent card (we fetch it; a caller cannot register a description, only a URL). Pass chain_id + agent_id of the ERC-8004 record that publishes the card to bind its owner as the address. Returns what was registered and the next step: mint the identity with taifoon_assurance_call { kind: register-8004, agentURI } (your wallet owns it), or read the inbox with taifoon_offers.

Input parameters:

- `agent_id` (string)
- `card_url` (string, required)
- `chain_id` (integer)

### `taifoon_hire_pad` (~211 tokens)

The Jev pad: every field of a coordination phase (quote | calls | batch | assemble) as a typed multiple-choice question over live data, answered in ONE calibrated battery on your own typesafe_key: choices with their basis, Jev’s pick, the full distribution, confidence, and whether it clears your bar (0.8 default). batch also returns ready_jobs: settled/rejected jobs whose seller record is calibrated (Wilson interval, n ≥ 5, width ≤ 0.35). dry:true returns the choices without spending a call. Jev fills in the numbers; you sign them.

Input parameters:

- `api_key` (string)
- `bar` (number)
- `chain_id` (integer)
- `dry` (boolean)
- `phase` (string, required)
- `price` (string): token smallest units
- `seller` (string)
- `skills` (array)
- `task` (string)
- `typesafe_key` (string)

### `taifoon_hiring_stages` (~106 tokens)

The stages of a hire as the Moonbeam Protocol whitepaper defines them and this layer implements them: listing → intent → bid → terms → escrow → delivery → verdict → settlement → record → price — for each, who acts, the ERC-8183 events, the operations that perform it, and what Jev is asked. Read this first to know which tool belongs to which stage.

Input parameters:

- `stage` (string): one stage id, or omit for all

### `taifoon_judge_decisions` (~109 tokens)

Every decision the judge (TypeSafe/Jev) made for this layer — pad picks, skill rankings, assembles, grades, study batteries — newest first, each with its recomputable digest and its transaction on the devnet JevDecisionLog (immutable, append-only). Filter by kind; ask for the genome frames.

Input parameters:

- `id` (string): one decision id, for its full record and calldata
- `kind` (string)
- `limit` (integer)

### `taifoon_landscape` (~106 tokens)

Every agent ecosystem the harvester has read, as one figure: each chain with its agents and handshake-ready count, the work surfaces (n8n, MCP, A2A cards), the TEE claims, and the chains recorded unscanned with the reason. Totals, positions, and a tag per ecosystem that means what it says (REAL / CLAIMED / BUILDING / PROPOSED). Read this to know where agents are before you hire or register.

### `taifoon_onboarding_flows` (~124 tokens)

Ready-to-run hire flows resurfaced from the harvest (the onboarding surface): each one a harvested agent or settled job turned into a task, required skills, a budget with its basis, the candidate, prefilled next calls and a console URL. Filter by skill or source; fetch one by id. Built by the delivery loop, TTL 7 days, stamped data_as_of.

Input parameters:

- `id` (string): fl_… to fetch one flow
- `limit` (integer)
- `skill` (string)
- `source` (string)

### `taifoon_agent_readiness` (~215 tokens)

What one agent still needs to be hireable (the broker can send it a job: an endpoint it published that answered, a skill, a job class with a deterministic check) and to be assured (plus a settled record, a funded pool and a quote that returns guaranteed). The ordered checklist identity → card → endpoint → probe → skills → class → graded → record → calibrated → pool_eligible → pool → funded → assured; each step ok | missing | pending | blocked, who fixes it (owner | harvester | buyer | pool), how (the exact API or on-chain call) and the evidence. Pass summary:true for the funnel over every harvested agent instead.

Input parameters:

- `agent_id` (string): the ERC-8004 agentId (decimal), or a seller address (0x…)
- `chain_id` (integer): 8453 Base (default), 5042 Arc, 36927 the devnet, …
- `summary` (boolean)
- `tenant` (string)

### `taifoon_agent_enrich` (~195 tokens)

Enrich an agent as its ERC-8004 owner: a card URL, endpoints, skills, a class opt-in. Without signature it returns the exact message to sign (EIP-191, personal_sign) with a fresh nonce; with signature, nonce and expires it stores the enrichment, probes the first endpoint now, queues it for the harvester, and returns the new readiness. Only the on-chain owner’s signature is accepted; a nonce works once.

Input parameters:

- `agent_id` (string, required)
- `chain_id` (integer)
- `data` (object, required): { card_url?, endpoints?: [{ url, kind: mcp|a2a|a2a-legacy|x402|webhook }], skills?: [tags], classes?: [class ids], name?, description? }
- `expires` (integer)
- `nonce` (string)
- `signature` (string)

### `taifoon_grid_economics` (~75 tokens)

What sharing a resource earns, per kind, at the live scarcity bonus: GRID per hour and per day for one resource, the USDC equivalent at the peg the oracle publishes (rule.gridUsdc), and the rule that derives it. Unknown (null) when the oracle does not answer — never zero.

### `taifoon_grid_shards` (~178 tokens)

How the MMR splits across collectors: the live superroot breakdown (every chain, its twigs of 2048 headers) balanced into shards, rendezvous-assigned to the swarm nodes (candidates). Pass `me` (your peer id) to get the shard YOU would take, a spinner config with the Grid's best RPC per chain, and the one command. `collectors` plans for a synthetic count. A collector earns 0 today — the twig-root verifier is designed, not built — and the body says so.

Input parameters:

- `collectors` (integer): plan for this many collectors instead of the live swarm
- `me` (string): your libp2p peer id (base58) — returns your shard, config and command
- `replication` (integer): collectors per shard (default 2)

### `taifoon_grid_prices` (~148 tokens)

Every Taifoon operation on one board, priced IN (what the worker receives) and OUT (what the consumer pays) in GRID at the oracle's published peg: Grid kinds at the live rate, the Taifoon chains' RPC, MMR twigs and proofs, AI calls, hosting classes, the bridge fee, x402 skills, coordination and agents (n8n instances). Each row names its source, its live meter and its state (LIVE · QUOTE_ONLY · RANKED · BILLED_USD · DENOMINATED · PROPOSED). Filter with group or state.

Input parameters:

- `group` (string)
- `state` (string)

### `taifoon_ai_call` (~212 tokens)

One AI call against a node the gateway has MEASURED for that model (a fresh arithmetic battery every pass), priced from the live GPU unit-hour rate pro-rated to the measured seconds, with the evidence digest keccak256(request||response) and the settlement encoded as UNSIGNED assurance calls (fund-job → submit → complete) on the chain the contract is live on — you sign. Give `hirer` to record the intent. Without a prompt it lists the measured nodes and the rate.

Input parameters:

- `chain_id` (integer): settlement chain (default 8453, Base — where the assurance contract is live)
- `hirer` (string): optional 0x wallet; records the intent in the Grid ledger
- `model` (string): the model the node must serve (e.g. hypernova-60b, littlelamb)
- `prompt` (string): your prompt (one user message)
- `provider` (string): optional: a specific measured endpoint from the providers list

### `taifoon_grid_hire` (~259 tokens)

Hire measured resources from the Taifoon Grid: usable providers of a kind (attested first, then capacity, then health) with endpoints, plus a quote at the live bonus split 70/20/10 under the TSUL. Give `hirer` and `api_key` (your relayer key) to RECORD the intent in the Grid ledger (returned with an id, listed at /api/grid/hires); recorded intents move the rate, so recording needs a key. Settlement is not deployed — a quote reserves nothing.

Input parameters:

- `api_key` (string): your relayer key (tfr_…) — REQUIRED to record an intent with `hirer` (recorded intents move the rate); without it you get the quote only
- `hirer` (string): your 0x address or agent id — when given, the intent is RECORDED in the Grid ledger (a record, not a settlement) and returned with an id
- `hours` (number): for how long (default 1)
- `kind` (string, required)
- `note` (string): optional, ≤200 chars, stored with the intent
- `units` (integer): how many resources (default 1)

### `taifoon_grid_bench` (~228 tokens)

Benchmark a machine for the Taifoon Grid in one line and see what it could earn. Returns the command to run ON the box (curl -fsSL https://www.taifoon.io/grid/bench.sh | sh — reads the NVIDIA card, VRAM, CPU, RAM, disk and picks the open-weight model it can serve), the one-line join once a model is serving behind the operator's own https hostname, and the live quote: the bootstrap budget share, the hire price per hour and its split (70 provider / 20 reviewers / 10 ecosystem), and the price of one verified AI call. Give vram_gb and gpus to get the model tier without running anything. Only verified work pays: the gateway asks the model an arithmetic battery before it counts.

Input parameters:

- `gpus` (integer): number of cards (default 1)
- `owner` (string): optional 0x wallet — filled into the join line
- `vram_gb` (number): VRAM of one card in GB (0 or omitted = no GPU)

### `taifoon_grid_settlement` (~111 tokens)

How Grid work is paid, read live: a wallet's ledger (measured work, reviews, supporter credits, referrals, pool cuts), what GridCredit has minted to it on Taifoon mainnet as soulbound GRID, what is still pending, its balance, the day's cap and what is left of it, and the next settler run (every 6 h). Without a wallet: the network totals and the rule.

Input parameters:

- `wallet` (string): optional 0x wallet

### `taifoon_grid_avenues` (~214 tokens)

Taifoon workflows for ALSO earning elsewhere from a Grid box: Vast.ai, Lava, dRPC, POKT, Storj, Akash, io.net, Clore, Salad, Olas, Virtuals ACP, Taifoon Hosting. Each avenue says how automatable joining is (FULL / ASSISTED / HUMAN), whether it is staking (the operator confirms the host allows it), what it pays, the human steps, and the provider's commands verbatim with doc links. Returns the one-line runner for the box: curl -fsSL https://www.taifoon.io/grid/avenue.sh | sh -s plan <id> (also: check all, run <id> with TAIFOON_AVENUE_RUN=yes). Signing steps are printed for the operator, never run. Filter by id or resource.

Input parameters:

- `id` (string): one avenue, e.g. storj, vast, lava
- `resource` (string): only avenues for this resource

### `taifoon_discover` (~196 tokens)

Discover who can do a job, through /v1: with q, the hireable agents and the capabilities those words find (GET /v1/capabilities/search?q=, e.g. q "market data" or "copy trading"); with class, the ranked sellers of that job class (GET /v1/classes/sellers — the seller chooseSeller picks first, with its record and probes); without either, the job classes (GET /v1/classes); with hireable:true, the hireable agents (GET /v1/agents/hireable). Free, read-only.

Input parameters:

- `class` (string): a job class id, e.g. mcp.digest or proof.verify.v5
- `hireable` (boolean)
- `limit` (integer)
- `q` (string): words for the work, e.g. "market data", "copy trading", "strategy backtest"

### `taifoon_hire` (~116 tokens)

Create an offer for a chosen seller (POST /v1/jobs): a job id, priced terms and the UNSIGNED calls that fund it — the hirer signs them in their own wallet; nothing is signed or sent here. body is the /v1/jobs request body (e.g. { chainId: 36927, seller, price_usdc, class, handshake_id }). Naming handshake_id needs the api_key that opened the handshake.

Input parameters:

- `api_key` (string)
- `body` (object, required)

### `taifoon_grade` (~121 tokens)

Grade up to 4 items with ONE calibrated TypeSafe/Jev call on YOUR OWN TypeSafe key (POST /v1/judge/grade; the key is forwarded, never stored; without it the route answers 403 byo_key). items: [{ id, state } | { id, handshake_id } | { id, jobId, chainId }].

Input parameters:

- `api_key` (string)
- `items` (array, required)
- `options` (array)
- `question` (string)
- `typesafe_key` (string, required)

### `taifoon_settle_plan` (~97 tokens)

The unsigned settlement plan of one paid call (POST /v1/settle): job id, terms and calls[] in order with who signs each. via:"us" names our JudgeAdapter as the evaluator (1 % fee, min 0.01; devnet 36927 today). body is the /v1/settle request body. Nothing is signed or sent.

Input parameters:

- `body` (object, required)

### `taifoon_bridge_plan` (~142 tokens)

Plan a USDC transfer across chains (POST /v1/transfer/plan): the exact approve + bridge calls through the CCTP fee router (10 bps, min 0.02 USDC), the fees and what arrives. Nothing is signed or sent. src_chain_id / dst_chain_id e.g. 8453 Base, 5042 Arc; amount in USDC smallest units (6 decimals).

Input parameters:

- `amount` (string, required)
- `dst_chain_id` (integer, required)
- `recipient` (string)
- `sender` (string, required)
- `speed` (string)
- `src_chain_id` (integer, required)

### `taifoon_proof_tx` (~155 tokens)

Prove one transaction is inside the Taifoon superroot (GET /v1/proof/tx/{chain}/{tx}): the block, the superroot that commits to it, is_finalized and the checks that were verified.

Input parameters:

- `chain_id` (integer, required): any chain the layer reads (GET /v1/rpc): 8453, 5042, 1, 56, 43114, 42161, 137, 10, 4663, 42220, 36927, 3692781, 2741, 196, 143, 100; another chain answers 404 chain_not_read
- `tx_hash` (string, required)

### `taifoon_access` (~196 tokens)

API access, one page of truth (GET /v1/access): the products one key rents (RPC, proofs, decoded events, the coordination API, grades), each with its calls, its price per 1,000 in GRID and USDC, its free allowance and limits, and what it measured over the last 24 h; the chains and methods of the RPC gateway; how a key is topped up. With view "key": your key’s permissions, budgets, balance and rate (GET /v1/access/key). With view "usage": what your key used per product family over window 1d | 7d | 30d | month (GET /v1/access/usage). key and usage need your key (api_key, or the X-API-Key header on this server).

Input parameters:

- `api_key` (string)
- `view` (string)
- `window` (string)

### `taifoon_access_topup` (~383 tokens)

Buy for your key, on any pay chain: a balance (Buy GRID: 100 GRID of service per 1 dollar; it pays calls past the free allowance, grades, records and gateway requests) or a monthly plan (builder-99, team-199, protocol-299: 30 days of metered use at a better rate, paid up front, nothing renews by itself). Step 1, the quote (GET /v1/access/quote): pass usdc (a whole number 1 to 500) or plan, and chain_id (8453 Base, 42161 Arbitrum One, 5042 Arc, 143 Monad: USDC; 4663 Robinhood Chain: USDG) → the unsigned token transfer to send from your own wallet, the message that wallet signs, the steps, and for_a_person (the page a person pays on). Step 2, with tx and signature (and the same chain_id, and plan when it is one): credit the key (POST /v1/access/topup or /v1/access/plan); a transaction credits once, and sending it again answers already: true. With tx and no signature: POST /v1/access/claim answers the messages that payment can be claimed with (a payment sent and not credited, for 7 days). Nothing is signed or sent by this tool. Needs your key. Your balance and plan: taifoon_access view "key".

Input parameters:

- `api_key` (string)
- `chain_id` (integer): the pay chain; absent = Base
- `plan` (string)
- `signature` (string): personal_sign of the quoted message by the wallet that sent the transfer
- `tx` (string): the hash of your transfer on that chain
- `usdc` (integer)

### `taifoon_rpc` (~228 tokens)

One JSON-RPC read through the Taifoon RPC gateway (POST /gw/rpc/{chainId}), the same on every chain: 8453, 5042, 1, 56, 43114, 42161, 137, 10, 4663, 42220, 36927, 3692781. Methods: the standard reads (blocks, transactions, receipts, eth_getLogs at most 10,000 blocks, eth_call, balances, code, nonces, gas, eth_chainId) and taifoon_getProof [{ tx } | { block }] (the proof from the layer’s indexes); writes are refused. The request goes to the chain’s measured rotation of endpoints and fails over to the next one. Free: 1,000 requests a day per key (100 without one); past it, from the key’s balance (GET /v1/access).

Input parameters:

- `api_key` (string)
- `chain_id` (integer, required)
- `method` (string, required)
- `params` (array)

### `taifoon_prove` (~221 tokens)

Prove anything the superroot commits, by kind: "tx" { chain_id, tx_hash } a transaction; "log" { chain_id, tx_hash, log_index } one event log with calldata for the on-chain verifier; "order" { protocol, key } an order’s whole lifecycle (key like erc8183:8453:81401); "transition" { protocol, seqs } given transitions of a protocol set, in order; "blocks" { chain_id, blocks } up to 256 blocks of a chain; "protocols" {} every protocol set inside the root. GETs /v1/proof/* and /v1/protocols/proven.

Input parameters:

- `api_key` (string)
- `blocks` (array)
- `chain_id` (integer)
- `key` (string)
- `kind` (string, required)
- `log_index` (integer)
- `protocol` (string)
- `seqs` (array)
- `tx_hash` (string)

### `taifoon_chain_lookup` (~282 tokens)

Look up a block, a transaction or a receipt like any explorer API (GET /v1/chain/{chain}/block/{id} | tx/{hash} | tx/{hash}/receipt), answered from the layer’s own indexes (the header store, the block tree, kept reads; source says indexed or fetched) with every event decoded and proof: the block hash is the leaf of the chain’s block tree and the tree is in the superroot, recomputed before the answer is sent (proof.verified). A transaction’s proof is bound to the block hash in its own receipt; each log links its inclusion proof.

Input parameters:

- `api_key` (string)
- `chain_id` (integer, required): any chain the layer reads: 8453, 5042, 1, 56, 43114, 42161, 137, 10, 4663, 42220, 36927, 3692781, 2741, 196, 143, 100
- `full_proof` (boolean): add the multiproof itself
- `id` (string, required): block: latest | finalized | a number | a block hash; tx and receipt: the 32-byte transaction hash
- `kind` (string, required)
- `txs` (boolean): block: add the transaction hashes

### `taifoon_chain_logs` (~195 tokens)

Event logs like eth_getLogs, paged (GET /v1/chain/{chain}/logs): the held headers’ blooms pick the blocks that may match and only those are read. Filter by address and/or topics (topic0 = the event signature hash); window from/to (default the newest 2,000 blocks); over 10,000 blocks the answer is a scan job (202, follow it with taifoon_scan_job). Each row says in_tree; proof covers the page.

Input parameters:

- `address` (string)
- `api_key` (string)
- `chain_id` (integer, required)
- `cursor` (integer)
- `from` (integer)
- `limit` (integer)
- `to` (integer)
- `topic0` (string)
- `topic1` (string)
- `topic2` (string)
- `topic3` (string)

### `taifoon_account_scan` (~188 tokens)

Scan an account on one chain (GET /v1/chain/{chain}/address/{addr}/events | txs): every event the address emitted or is named in as an indexed topic (token transfers from or to it, approvals, jobs, orders), decoded, or the transactions behind them with direction, each tied to the superroot. Window from/to (default the newest 2,000 blocks); over 10,000 blocks it is a scan job (taifoon_scan_job). A native transfer with no log is not in a logs bloom; coverage.sees says so.

Input parameters:

- `address` (string, required)
- `api_key` (string)
- `chain_id` (integer, required)
- `cursor` (integer)
- `from` (integer)
- `limit` (integer)
- `to` (integer)
- `view` (string)

### `taifoon_scan_job` (~96 tokens)

Advance and read a scan job (GET /v1/chain/{chain}/scans/{id}): one step per call, its progress and the rows so far; call again until job.done.

Input parameters:

- `api_key` (string)
- `chain_id` (integer, required)
- `cursor` (integer)
- `id` (string, required): sc_… from the 202
- `limit` (integer)

### `taifoon_transitions` (~150 tokens)

A protocol’s state transitions from the protocol trees (GET /v1/transitions/{protocol}), no chain read: one order’s lifecycle with its current state (key, e.g. erc8183:8453:81435) or a page of the history by sequence, each transition with its chain, block, transaction and log, and both proof steps recomputed (history in its root, protocol leaf in the superroot). taifoon_prove kind "protocols" lists the protocols.

Input parameters:

- `api_key` (string)
- `from_seq` (integer)
- `key` (string)
- `limit` (integer)
- `protocol` (string, required)

### `taifoon_protocol_decoders` (~111 tokens)

The protocols the producer decodes (GET /v1/protocols/decoders): each with its source and fill topic and the chains it watches; the chain tiers (how many chains are proven per transaction, how many the superroot commits, where the live list is); what registering a protocol changes today per layer (proofs, attribution, decoding) and what it does not; the manifest shape for taifoon_protocol_register; the manifests waiting for an operator. No key needed.

### `taifoon_protocol_register` (~674 tokens)

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.

Input parameters:

- `abi` (array)
- `actions` (array)
- `author` (string)
- `contracts` (object, required): chain id to list of 0x addresses
- `docs` (string)
- `dry_run` (boolean)
- `events` (array, required)
- `fee_bps` (integer)
- `fill_selector` (string|null)
- `fill_topic` (string|null)
- `finality` (string)
- `grade` (boolean): also grade the manifest: code verified the facts, Jev answers the rubric over them; spends one of your grades
- `id` (string, required)
- `identity` (string)
- `key` (string)
- `name` (string, required)
- `signature` (string|null)
- `sla_ms` (integer)
- `source_topic` (string, required)
- `states` (array)
- `supported_dst` (array)
- `transitions` (array)
- `type` (string, required)
- `version` (integer)

### `taifoon_protocol_pending` (~74 tokens)

The manifest approval queue (GET /v1/protocols/pending): submitted, approved, rejected and deprecated manifests. Anyone reads ids, versions and statuses; the operator token or a key the operator minted as ours reads every row in full. status narrows to one status.

Input parameters:

- `status` (string)

### `taifoon_protocol_decide` (~96 tokens)

Approve or reject a submitted manifest (POST /v1/protocols/{id}/approve | reject). Admin only: the operator token or a key the operator minted as ours; any other key is 403 ours_only. reject needs a reason. Approval returns the unsigned registry submit() call for the author.

Input parameters:

- `decision` (string, required)
- `id` (string, required)
- `reason` (string)

### `taifoon_metrics` (~98 tokens)

How much went through the coordination layer (GET /v1/metrics): calls per route and key class, handshakes, gateway λ steps, hires, grades, bridges and fees — per chain, ours vs customers, on-chain vs off-chain. series:N gives N days of headlines instead (GET /v1/metrics/series).

Input parameters:

- `day` (string): YYYY-MM-DD (UTC)
- `series` (integer)

### `taifoon_catalog` (~233 tokens)

Every hireable agent the coordination layer resells (GET /v1/catalog): per agent the seller’s own price, ours (seller + a minimal routing fee, fee.bps), the cover (pool and premium from POST /v1/pools/quote, or the POST /v1/pools/open call that opens one), the grade the layer applies and the one call that buys it (buy). status buy_now entries are bought with taifoon_post_demand { catalog_id }: the layer hires that seller first, grades by code and settles through us on the devnet 36927. id reads one entry. Free, read-only.

Input parameters:

- `class` (string): a job class id, e.g. mcp.digest
- `id` (string): one entry: cat_ + 16 hex
- `limit` (integer)
- `offset` (integer)
- `protocol` (string): mcp, a2a, uagents, n8n, x402
- `q` (string): name, seller host or skill contains
- `status` (string)

### `taifoon_explorer_jobs` (~325 tokens)

Every job that went through the Taifoon coordination layer (GET /v1/explorer/jobs): auto-match and catalog demands, broker hires and jobs on our assurance hooks on Base and the devnet. Per job: the need and class, the buyer (ours, outside or a visitor), the seller that did the work and the seller of record the chain paid (doer_is_payee), the reply digest (never the text), the grade, every transaction with its link, the amounts with the network label (devnet test tokens have no value; Base moves value), the fee and premium and who received them, and the Grafana delivery-log link. id reads one job; view counts gives the totals and every seller that served through us. Free, read-only.

Input parameters:

- `buyer` (string)
- `chain` (string): 36927 (devnet), 8453 (Base) or none (off-chain broker hires)
- `class` (string): a job class id, e.g. mcp.digest
- `id` (string): one job: a demand (dm_ + 24 hex), a handshake (hs_ + 24 hex) or a job id (0x + 64 hex)
- `kind` (string)
- `limit` (integer)
- `page` (integer)
- `seller` (string): the doer host or agent id, or the payee address, contains
- `view` (string): counts: the totals and the sellers that served through us, no rows

### `taifoon_list_demands` (~83 tokens)

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.

Input parameters:

- `limit` (integer)
- `state` (string)

### `taifoon_work` (~125 tokens)

The newest demands whose classes match yours (GET /v1/hooks/work): pass classes (ids of GET /v1/classes?view=language, e.g. mcp.digest, text.summarize) and the next_since of your last call as since. Each item names the demand, its classes and how well yours match. Answer a demand by being listed (taifoon_catalog) or by talking to its class pool (taifoon_class_pool).

Input parameters:

- `classes` (array, required)
- `since` (string): ISO time: only demands announced after it

### `taifoon_seller_profile` (~230 tokens)

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.

Input parameters:

- `class` (string): without seller: list the sellers of this class, e.g. mcp.digest
- `findings` (boolean): answer the findings with their records instead of the profile
- `limit` (integer)
- `seller` (string): its host (agent402.tools), <chain>:<agentId>, listing id (ls_…) or address
- `state` (string)

### `taifoon_venues` (~202 tokens)

Where outside buyers pay for agent work (GET /v1/venues): x402 on Base, Solana, Arbitrum, Robinhood Chain and Monad, Virtuals memo-ACP, ERC-8183 and BitAgent, each with USD paid a week, buyers, sellers, the classes its buyers pay for with their median price, the sellers whose buyers buy on a schedule, the admitted sellers there and the next action (hire, onboard a seller, build a flow); and the top 20 venue × class rows by paid volume. venue: one venue (x402-base …) or a marketplace (x402, virtuals). Free, read-only.

Input parameters:

- `venue` (string): a venue id (x402-base, x402-solana, x402-arbitrum, x402-robinhood, x402-monad, memoacp-base, erc8183-base, bitagent-base) or a marketplace id

### `taifoon_class_pool` (~91 tokens)

The off-chain matching pool of one class (GET /v1/classes/:class/pool): its members on every venue (A2A, MCP, x402, n8n, ERC-8004, Olas, Virtuals, Agentverse), open demands, listeners and what it did. No chain pool or cover is needed to match or talk.

Input parameters:

- `class` (string, required)

### `taifoon_pools_networks` (~116 tokens)

Where a coverage pool can be opened (GET /v1/pools/networks): every supported chain and line (Base 8453, Arbitrum One 42161, Arc 5042, Robinhood Chain 4663, Monad 143, the Taifoon devnet 36927) with its factory, hook, pool assets and live status. Moonbeam pools are listed as closed by policy; every other chain as not supported yet. Start here, then taifoon_pool_open_plan.

### `taifoon_pool_open_plan` (~414 tokens)

Open a coverage pool behind a seller (POST /v1/pools/open): returns the UNSIGNED createPool transaction { to, data, value, chainId }, simulated (eth_call + eth_estimateGas), with the gas, the fee and the pool address it will create — or the pool the seller already has (state exists). Creating a pool is permissionless, deposits nothing and costs gas only; you sign and send it with your own wallet, then call taifoon_pool_status with the tx hash. On mainnet the seller must meet the pool rule, or pass override: true. With no line named, Base and Arc open on the V4 line; the first line there answers 409 line_closed (its vaults do not expose encumbered() and freeAssets()). Moonbeam pools answer closed_by_policy.

Input parameters:

- `asset` (string): pool asset, symbol or address; default the line’s job token (USDC; dUSDC on the devnet)
- `chain_id` (integer, required): 8453 Base, 42161 Arbitrum One, 5042 Arc, 4663 Robinhood Chain (USDG), 143 Monad or 36927 the Taifoon devnet
- `from` (string): the wallet that will sign (the simulation runs from it); default the seller
- `line` (string): the factory line; default v4 on Base and Arc, layer on the devnet (v4-glmr is a devnet line). The first line (layer) on Base and Arc answers 409 line_closed: its vaults do not expose encumbered() and…
- `name` (string)
- `override` (boolean): open behind a mainnet seller that does not meet the pool rule
- `seller` (string, required): the seller: a 0x address, or its ERC-8004 agent id ("12345" or "<chain>:12345")
- `symbol` (string)

### `taifoon_pool_status` (~134 tokens)

After you broadcast createPool (GET /v1/pools/open/{chain}/{tx}, or GET /v1/pools/status by seller and asset): state pending | created | reverted | no_pool, the pool address from the PoolCreated log, confirmed on the factory (poolOf) and listed in GET /v1/pools. pending carries retry_after_seconds.

Input parameters:

- `asset` (string)
- `chain_id` (integer, required)
- `line` (string)
- `seller` (string): instead of tx_hash: the seller address
- `tx_hash` (string): the createPool transaction

### `taifoon_network` (~56 tokens)

The network, live (GET /v1/network): sellers online per job class with latency, the grid (RPC rotation health per chain), cross-chain routes with a live quote, the gateway’s steps today. No customer data.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-taifoon-coordination-layer/coord#diagnostics

## Score history

- 2026-10-07: 65
- 2026-10-04: 63
- 2026-10-03: 63
- 2026-10-02: 63
- 2026-10-01: 62
- 2026-09-30: 62

## Common questions

### What is the Taifoon coordination layer MCP server?

Taifoon coordination layer is an MCP server listed in the public MCP registry as io.taifoon/coordination-layer. Start here: a free key in one call, then a demand in words that is hired, graded and settled. This page covers its hosted endpoint (https://coord.taifoon.dev/mcp?ref=mcp-registry).

### Is the Taifoon coordination layer MCP server safe to use?

Taifoon coordination layer scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Taifoon coordination layer MCP server expose?

Taifoon coordination layer exposes 72 tools: taifoon_register, taifoon_post_demand, taifoon_demand_status, taifoon_superroot, taifoon_proof, and 67 more. Their descriptions and schemas cost roughly 12,933 tokens of context every time the server is loaded.

### Does the Taifoon coordination layer MCP server require authentication?

No. We connected to Taifoon coordination layer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Taifoon coordination layer MCP server still maintained?

Taifoon coordination layer is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://coord.taifoon.dev/mcp?ref=mcp-registry
- Website: https://www.taifoon.io/docs/coordination-api
- Changelog RSS feed: https://verifymcp.io/servers/io-taifoon-coordination-layer/coord.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-taifoon-coordination-layer/coord.json
- HTML version of this page: https://verifymcp.io/servers/io-taifoon-coordination-layer/coord