Skip to content

Taifoon coordination layer MCP server

io.taifoon/coordination-layertaifoon.iostreamable-httpv1.2.0Scanned

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

15 tools: 1 can delete or cancel things, 13 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 13 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 14
  • Can send data out · 3
  • 6 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Taifoon coordination layer MCP server can do

The Taifoon coordination layer MCP server is published by taifoon.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (1 tool: taifoon_orderbook) and create or change data (13 tools: taifoon_register, taifoon_account, taifoon_find, taifoon_demand and 9 more). 1 tool only reads.

1 tool reads private data (taifoon_vault); 14 tools bring in text other people can write (taifoon_register, taifoon_account, taifoon_find and 11 more); 3 tools can send data out of your system (taifoon_demand, taifoon_chain and taifoon_grid). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 6 findings (annotation-conflict and long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 1Claude Code: deny
  • taifoon_orderbookUses the Taifoon orderbook (spot ETH-USDG on Robinhood Chain): account, deposit route, orders, withdrawals, settlement records.Reads text others writeNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Orderbook venue
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 13Claude Code: ask
  • taifoon_accountReads your tenant, what your key rents and its usage, and runs your reseller side (child keys with your markup, your earnings).Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "taifoon_account" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Your account
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • taifoon_buyBuys one call of a skill the layer sells per call (x402): the best-ranked seller answers.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 Taifoon at 0.0012 USDC (x402); plan.steps, sold per call by Taifoon at 0.0012 USDC (x402); risk.address, sold per call by Taifoon at 0.0012 USDC (x402); agent.directory, sold per call by Taifoon at 0.002 USDC (x402); inference.metered, sold per call by Taifoon at 0.001512 USDC (x402); market.price, sold per call by Taifoon at 0.001714 USDC (x402); mech.predict, sold per call by Taifoon at 0.002848 USDC (x402); tee.typed.compile, sold per call by Taifoon at 0.00122 USDC (x402).

    Annotations the server declares

    • title: Buy a call
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • taifoon_chainReads blocks, transactions, logs, accounts and protocol state from the layer's own index and coord RPC.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "taifoon_chain" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read chain data
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • taifoon_demandPosts work in plain words and lets the layer match, hire, grade and settle it; reads demands.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "post": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe description's first verb is "post": it sends or publishes something to other people.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Post a need
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • taifoon_findFinds agents, capabilities and resold skills for a job, ranked.Reads text others write2 findings

    Why it is in this group

    • The name "taifoon_find" says "find": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,030 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...re flows from the harvest; readiness — what one agent still needs to be hireable."

      What this check looks for
    • Warn

      The server marks "taifoon_find" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "taifoon_find" says "find": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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; search — one index in plain words (q): agents across markets (vertical:agents, facet venue), classes, venues, operations, programs, strategies; each row with what to read and the next call; outlets — from what you sell (need) to where to list it: the classes, the venues in ranked order, and the series of calls you send yourself; prices — Taifoon Search: what a task class is worth per venue — the ask band, the paid band and the buyer price (the one price rule, _UNDERCUT_v3_: 20 % under the cheapest matching seller, never under (seller + venue fees) × 1.2); query class=, venue=; compare — Taifoon Search: which venue pays most for a class — the sides ranked by paid median, then USD paid; query class= (required); book — Taifoon Search: the market book — every venue's ask and bid per resource, each match priced by the one scheme; query resource=, buy=, sell=, chain=, state= (the edges need a live key); listings — Taifoon Search: the venues an agent should list on, ranked by expected USD a week for its classes, each with the venue's own incentive and the listing's state; path id= (a registered agent) or query classes=a,b for a card not yet registered; flows — ready-to-run hire flows from the harvest; readiness — what one agent still needs to be hireable.

    Annotations the server declares

    • title: Find who can do a job
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • taifoon_gradeGrades work with calibrated answers on your own TypeSafe key, and reads the judge's decisions.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Grade a delivery
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • taifoon_gridBuys and sells measured compute and RPC on the Taifoon Grid: AI, GPU and TEE calls, hiring resources, joining with your own, earnings.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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; builders — join the Early Builder Program whitelist: get the message, sign it, send it; 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.

    Annotations the server declares

    • title: Grid compute and resources
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • taifoon_hireHires a chosen agent end to end: terms, offer, delivery over its own protocol, assurance and coverage pools, settlement plan, lifecycle.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Hire an agent
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • taifoon_opCall 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).Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "call": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Op
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • taifoon_proveProves blocks, transactions, logs and transfers under the Taifoon superroot.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Prove a chain fact
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • taifoon_registerCreates a tenant with a free key (tfr_free_…, shown once), or a free RPC key with its gateway URL and allowance.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a key
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • taifoon_sellLists you as a seller: register your agent by its card, enrich it, read the offers sent to you, register a protocol for decoding.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "taifoon_sell" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "list": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Sell on the layer
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • taifoon_vaultReads a tenant vault and builds the owner-signed acts that control it.Reads private dataReads text others write1 finding

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe name "taifoon_vault" says "vault": it reads secrets.
    • private-dataThe description's first sentence says "read" and "vault": it reads secrets.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "taifoon_vault" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Vault
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • taifoon_observeReads the live network, the stream and protocol order state: sellers online, RPC health, stuck orders, projects, Lambda Studio, Twigster.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Observe the layer
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

42 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write14
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__coordination-layer__taifoon_vault"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:14 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
14
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 14 tools that change things (1 destructive, 13 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://coord.taifoon.dev/mcp?ref=mcp-registry: tools/list returned 15 tools to an anonymous client, including taifoon_orderbook (destructive), taifoon_register (write), taifoon_account (write), taifoon_find (write), taifoon_demand (write) and 9 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 13 to 14

Findings

Matches of fixed checks, with the text they matched.

5 warn1 info
  • The server marks "taifoon_account" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "read": a word for reading.

    What this check looks for
  • The server marks "taifoon_find" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "taifoon_find" says "find": a word for reading.

    What this check looks for
  • The server marks "taifoon_chain" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "read": a word for reading.

    What this check looks for
  • The server marks "taifoon_vault" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "read": a word for reading.

    What this check looks for
  • The server marks "taifoon_sell" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "list": a word for reading.

    What this check looks for
  • The description is 2,030 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...re flows from the harvest; readiness — what one agent still needs to be hireable."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools6 changed.~6 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 13 -> 14.View diff
    • Tools that change things, listed without credentials: 13 to 14
  3. Tools3 changed.~3 changedView diff

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__coordination-layer__taifoon_observe"
    ],
    "ask": [
      "mcp__coordination-layer__taifoon_register",
      "mcp__coordination-layer__taifoon_account",
      "mcp__coordination-layer__taifoon_find",
      "mcp__coordination-layer__taifoon_demand",
      "mcp__coordination-layer__taifoon_hire",
      "mcp__coordination-layer__taifoon_grade",
      "mcp__coordination-layer__taifoon_prove",
      "mcp__coordination-layer__taifoon_chain",
      "mcp__coordination-layer__taifoon_vault",
      "mcp__coordination-layer__taifoon_grid",
      "mcp__coordination-layer__taifoon_sell",
      "mcp__coordination-layer__taifoon_buy",
      "mcp__coordination-layer__taifoon_op"
    ],
    "deny": [
      "mcp__coordination-layer__taifoon_orderbook"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as coordination-layer. Review it before you use it.

Capability tags behind 14 rules
  • mcp__coordination-layer__taifoon_register untrusted-input
  • mcp__coordination-layer__taifoon_account untrusted-input
  • mcp__coordination-layer__taifoon_find untrusted-input
  • mcp__coordination-layer__taifoon_demand untrusted-input, outbound
  • mcp__coordination-layer__taifoon_hire untrusted-input
  • mcp__coordination-layer__taifoon_grade untrusted-input
  • mcp__coordination-layer__taifoon_prove untrusted-input
  • mcp__coordination-layer__taifoon_chain untrusted-input, outbound
  • mcp__coordination-layer__taifoon_vault private-data, untrusted-input
  • mcp__coordination-layer__taifoon_orderbook untrusted-input
  • mcp__coordination-layer__taifoon_grid untrusted-input, outbound
  • mcp__coordination-layer__taifoon_sell untrusted-input
  • mcp__coordination-layer__taifoon_buy untrusted-input
  • mcp__coordination-layer__taifoon_op untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.taifoon/coordination-layer/verify?hash=915ee939b1d11e888a346b6b03553f95a0ff91c5c7544cbb790b7a2b94a86e65" | jq -e '.changed == false'

Pinned hash 915ee939b1d1, from Nov 18, 2026, 15:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.taifoon/coordination-layer/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.taifoon/coordination-layer
[![Anlyon Radar](https://radar.anlyon.com/badge/io.taifoon/coordination-layer.svg)](https://radar.anlyon.com/servers/io.taifoon/coordination-layer)

Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.

Taifoon coordination layer MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Taifoon coordination layer MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 14 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Taifoon coordination layer MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: taifoon_orderbook.

Can the Taifoon coordination layer MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Taifoon coordination layer MCP server have?

15 tools: 1 destructive, 13 write, 1 read. taifoon_orderbook, taifoon_register, taifoon_account, taifoon_find, taifoon_demand, taifoon_hire, taifoon_grade, taifoon_prove and 7 more.

Does the Taifoon coordination layer MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Taifoon coordination layer MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): taifoon_demand, taifoon_chain and taifoon_grid.

Has the Taifoon coordination layer MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.