Servidor MCP

Taifoon coordination layer

            io.taifoon/coordination-layer
        

Nube e infraestructura Cripto y Web3 Infraestructura MCP y de agentes Público y accesible MCP 2026-07-28

Qué hace este MCP

Coordinates agent registration, hiring, benchmarking, resource grids, assurance workflows, and blockchain-based settlement and proofs.

taifoon_agent_enrich

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.

Esquema de entrada

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

taifoon_agent_readiness

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.

Esquema de entrada

{'type': 'object', 'properties': {'tenant': {'enum': ['moonbeam', 'taifoon'], 'type': 'string'}, 'summary': {'type': 'boolean'}, 'agent_id': {'type': 'string', 'description': 'the ERC-8004 agentId (decimal), or a seller address (0x…)'}, 'chain_id': {'type': 'integer', 'description': '8453 Base (default), 5042 Arc, 36927 the devnet, …'}}, 'additionalProperties': False}

taifoon_agents_register

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.

Esquema de entrada

{'type': 'object', 'required': ['card_url'], 'properties': {'agent_id': {'type': 'string'}, 'card_url': {'type': 'string'}, 'chain_id': {'type': 'integer'}}, 'additionalProperties': False}

taifoon_ai_call

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.

Esquema de entrada

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

taifoon_assurance_call

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.

Esquema de entrada

{'type': 'object', 'required': ['chain_id', 'action'], 'properties': {'action': {'type': 'object', 'description': '{ kind, jobId?, seller?, token?, price?, premium?, deposit?, deadline?, pool?, evidenceDigest?, verdictDigest?, asset?, receiver?, amount? }'}, 'chain_id': {'type': 'integer'}}, 'additionalProperties': False}

taifoon_bridge_plan

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).

Esquema de entrada

{'type': 'object', 'required': ['src_chain_id', 'dst_chain_id', 'amount', 'sender'], 'properties': {'speed': {'enum': ['standard', 'fast'], 'type': 'string'}, 'amount': {'type': 'string'}, 'sender': {'type': 'string'}, 'recipient': {'type': 'string'}, 'dst_chain_id': {'type': 'integer'}, 'src_chain_id': {'type': 'integer'}}, 'additionalProperties': False}

taifoon_catalog

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.

Esquema de entrada

{'type': 'object', 'properties': {'q': {'type': 'string', 'description': 'name, seller host or skill contains'}, 'id': {'type': 'string', 'description': 'one entry: cat_ + 16 hex'}, 'class': {'type': 'string', 'description': 'a job class id, e.g. mcp.digest'}, 'limit': {'type': 'integer', 'maximum': 200, 'minimum': 1}, 'offset': {'type': 'integer', 'minimum': 0}, 'status': {'enum': ['buy_now', 'priced', 'quote_on_request', 'covered', 'openable', 'ready', 'served'], 'type': 'string'}, 'protocol': {'type': 'string', 'description': 'mcp, a2a, uagents, n8n, x402'}}, 'additionalProperties': False}

taifoon_demand_status

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.

Esquema de entrada

{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'the demand id, dm_ + 24 hex'}}, 'additionalProperties': False}

taifoon_discover

Discover who can do a job, through /v1: with class, the ranked sellers of that job class (GET /v1/classes/sellers — the seller chooseSeller picks first, with its record and probes); without it, the job classes (GET /v1/classes); with hireable:true, the hireable agents (GET /v1/agents/hireable). Free, read-only.

Esquema de entrada

{'type': 'object', 'properties': {'class': {'type': 'string', 'description': 'a job class id, e.g. mcp.digest or proof.verify.v5'}, 'limit': {'type': 'integer', 'maximum': 200, 'minimum': 1}, 'hireable': {'type': 'boolean'}}, 'additionalProperties': False}

taifoon_explorer_jobs

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.

Esquema de entrada

{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'one job: a demand (dm_ + 24 hex), a handshake (hs_ + 24 hex) or a job id (0x + 64 hex)'}, 'kind': {'enum': ['auto-match', 'resale', 'broker-hire', 'hook-job'], 'type': 'string'}, 'page': {'type': 'integer', 'minimum': 1}, 'view': {'enum': ['counts'], 'type': 'string', 'description': 'counts: the totals and the sellers that served through us, no rows'}, 'buyer': {'enum': ['ours', 'outside', 'visitor', 'unknown'], 'type': 'string'}, 'chain': {'type': 'string', 'description': '36927 (devnet), 8453 (Base) or none (off-chain broker hires)'}, 'class': {'type': 'string', 'description': 'a job class id, e.g. mcp.digest'}, 'limit': {'type': 'integer', 'maximum': 100, 'minimum': 1}, 'seller': {'type': 'string', 'description': 'the doer host or agent id, or the payee address, contains'}}, 'additionalProperties': False}

taifoon_finality_explain

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.

Esquema de entrada

{'type': 'object', 'required': ['type_id'], 'properties': {'type_id': {'type': 'integer', 'maximum': 15, 'minimum': 0}}, 'additionalProperties': False}

taifoon_grade

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 }].

Esquema de entrada

{'type': 'object', 'required': ['items', 'typesafe_key'], 'properties': {'items': {'type': 'array', 'items': {'type': 'object'}}, 'api_key': {'type': 'string'}, 'options': {'type': 'array', 'items': {'type': 'string'}}, 'question': {'type': 'string'}, 'typesafe_key': {'type': 'string'}}, 'additionalProperties': False}

taifoon_grid_avenues

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.

Esquema de entrada

{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'one avenue, e.g. storj, vast, lava'}, 'resource': {'enum': ['gpu', 'rpc', 'storage', 'agent', 'compute'], 'type': 'string', 'description': 'only avenues for this resource'}}, 'additionalProperties': False}

taifoon_grid_bench

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.

Esquema de entrada

{'type': 'object', 'properties': {'gpus': {'type': 'integer', 'maximum': 64, 'minimum': 0, 'description': 'number of cards (default 1)'}, 'owner': {'type': 'string', 'description': 'optional 0x wallet — filled into the join line'}, 'vram_gb': {'type': 'number', 'minimum': 0, 'description': 'VRAM of one card in GB (0 or omitted = no GPU)'}}, 'additionalProperties': False}

taifoon_grid_economics

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.

Esquema de entrada

{'type': 'object', 'properties': {}, 'additionalProperties': False}

taifoon_grid_hire

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.

Esquema de entrada

{'type': 'object', 'required': ['kind'], 'properties': {'kind': {'enum': ['rpc', 'gpu', 'fpga', 'storage', 'ip'], 'type': 'string'}, 'note': {'type': 'string', 'description': 'optional, ≤200 chars, stored with the intent'}, 'hirer': {'type': 'string', 'description': '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': {'type': 'number', 'minimum': 0.01, 'description': 'for how long (default 1)'}, 'units': {'type': 'integer', 'maximum': 1000, 'minimum': 1, 'description': 'how many resources (default 1)'}, 'api_key': {'type': 'string', 'description': 'your relayer key (tfr_…) — REQUIRED to record an intent with `hirer` (recorded intents move the rate); without it you get the quote only'}}, 'additionalProperties': False}

taifoon_grid_join

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.

Esquema de entrada

{'type': 'object', 'required': ['kind', 'endpoint', 'owner'], 'properties': {'ref': {'type': 'string', 'description': 'Optional: the 0x wallet that referred this resource. It earns a share of what the resource accrues (measured work only). Never the owner itself.'}, 'kind': {'enum': ['rpc', 'gpu'], 'type': 'string', 'description': 'rpc earns today; gpu is benchmarked and ranked but earns 0 until real GPU work exists'}, 'pool': {'type': 'string', 'description': '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.'}, 'owner': {'type': 'string', 'description': '0x wallet address that earns the GRID points'}, 'chain_id': {'type': 'integer', 'description': 'Required for rpc: the chain this endpoint serves (verified via eth_chainId)'}, 'endpoint': {'type': 'string', 'description': 'https:// or wss:// hostname endpoint (never a raw IP, never embedded credentials)'}}, 'additionalProperties': False}

taifoon_grid_pool

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.

Esquema de entrada

{'type': 'object', 'properties': {}, 'additionalProperties': False}

taifoon_grid_prices

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.

Esquema de entrada

{'type': 'object', 'properties': {'group': {'enum': ['grid', 'chain', 'mmr', 'ai', 'hosting', 'bridge', 'skill', 'coordination', 'agents'], 'type': 'string'}, 'state': {'enum': ['LIVE', 'QUOTE_ONLY', 'RANKED', 'BILLED_USD', 'DENOMINATED', 'PROPOSED', 'BUILD', 'DESIGN'], 'type': 'string'}}, 'additionalProperties': False}

taifoon_grid_settlement

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.

Esquema de entrada

{'type': 'object', 'properties': {'wallet': {'type': 'string', 'description': 'optional 0x wallet'}}, 'additionalProperties': False}

taifoon_grid_shards

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.

Esquema de entrada

{'type': 'object', 'properties': {'me': {'type': 'string', 'description': 'your libp2p peer id (base58) — returns your shard, config and command'}, 'collectors': {'type': 'integer', 'maximum': 1024, 'minimum': 1, 'description': 'plan for this many collectors instead of the live swarm'}, 'replication': {'type': 'integer', 'maximum': 8, 'minimum': 1, 'description': 'collectors per shard (default 2)'}}, 'additionalProperties': False}

taifoon_grid_status

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.

Esquema de entrada

{'type': 'object', 'properties': {}, 'additionalProperties': False}

taifoon_handshake

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.

Esquema de entrada

{'type': 'object', 'required': ['address', 'kind', 'task'], 'properties': {'args': {'type': 'object', 'description': 'MCP: the tool arguments'}, 'kind': {'enum': ['mcp', 'a2a', 'onchain', 'n8n'], 'type': 'string'}, 'task': {'type': 'string'}, 'tool': {'type': 'string', 'description': 'MCP: the tool to call'}, 'hirer': {'type': 'string'}, 'address': {'type': 'string', 'description': 'the agent’s owner / seller address (full 20 bytes)'}, 'api_key': {'type': 'string', 'description': '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'}, 'agent_id': {'type': 'string'}, 'chain_id': {'type': 'integer'}, 'dispatch': {'type': 'boolean'}, 'budget_usdc': {'type': 'number'}, 'required_skills': {'type': 'array', 'items': {'type': 'string'}}}, 'additionalProperties': False}

taifoon_hire

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.

Esquema de entrada

{'type': 'object', 'required': ['body'], 'properties': {'body': {'type': 'object'}, 'api_key': {'type': 'string'}}, 'additionalProperties': False}

taifoon_hire_assemble

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).

Esquema de entrada

{'type': 'object', 'required': ['task', 'required_skills'], 'properties': {'task': {'type': 'string'}, 'api_key': {'type': 'string'}, 'budget_usdc': {'type': 'number'}, 'typesafe_key': {'type': 'string'}, 'required_skills': {'type': 'array', 'items': {'type': 'string'}}}, 'additionalProperties': False}

taifoon_hire_attach

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.

Esquema de entrada

{'type': 'object', 'required': ['id', 'job_id', 'chain_id'], 'properties': {'id': {'type': 'string'}, 'job_id': {'type': 'string'}, 'api_key': {'type': 'string'}, 'chain_id': {'enum': [8453, 5042, 36927], 'type': 'integer'}}, 'additionalProperties': False}

taifoon_hire_lifecycle

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.

Esquema de entrada

{'type': 'object', 'required': ['job_id'], 'properties': {'prove': {'type': 'boolean'}, 'job_id': {'type': 'string'}, 'tenant': {'enum': ['moonbeam'], 'type': 'string', 'description': 'read only this tenant’s hook; omitted = the layer’s hook first, then every tenant’s on the chain'}, 'chain_id': {'type': 'integer'}}, 'additionalProperties': False}

taifoon_hire_pad

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.

Esquema de entrada

{'type': 'object', 'required': ['phase'], 'properties': {'bar': {'type': 'number'}, 'dry': {'type': 'boolean'}, 'task': {'type': 'string'}, 'phase': {'enum': ['quote', 'calls', 'batch', 'assemble'], 'type': 'string'}, 'price': {'type': 'string', 'description': 'token smallest units'}, 'seller': {'type': 'string'}, 'skills': {'type': 'array', 'items': {'type': 'string'}}, 'api_key': {'type': 'string'}, 'chain_id': {'type': 'integer'}, 'typesafe_key': {'type': 'string'}}, 'additionalProperties': False}

taifoon_hire_path

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

Esquema de entrada

{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string'}}, 'additionalProperties': False}

taifoon_hire_suggest

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.

Esquema de entrada

{'type': 'object', 'required': ['task'], 'properties': {'jev': {'type': 'boolean'}, 'task': {'type': 'string'}, 'seller': {'type': 'string', 'description': '0x… seller (optional)'}, 'api_key': {'type': 'string'}, 'chain_id': {'type': 'integer'}, 'typesafe_key': {'type': 'string'}}, 'additionalProperties': False}

taifoon_hiring_stages

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.

Esquema de entrada

{'type': 'object', 'properties': {'stage': {'type': 'string', 'description': 'one stage id, or omit for all'}}}

taifoon_judge_compose

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.

Esquema de entrada

{'type': 'object', 'properties': {'mode': {'enum': ['single', 'prepare', 'answers'], 'type': 'string'}, 'olas': {'type': 'string'}, 'model': {'type': 'string'}, 'state': {'type': 'string'}, 'job_id': {'type': 'string'}, 'record': {'enum': ['none', 'devnet', 'base'], 'type': 'string', 'description': 'write the decision on chain: none (default, receipt + digests only), devnet, or base (metered by a daily budget)'}, 'answers': {'type': 'object', 'description': 'mode answers: id → { value, confidence, probabilities } for each of the four questions prepare returned'}, 'api_key': {'type': 'string'}, 'chain_id': {'type': 'integer'}, 'price_usdc': {'type': 'number'}, 'answered_by': {'enum': ['n8n-typesafe'], 'type': 'string'}, 'execution_id': {'type': 'string'}, 'handshake_id': {'type': 'string'}, 'typesafe_key': {'type': 'string'}, 'prepare_digest': {'type': 'string'}}, 'additionalProperties': False}

taifoon_judge_decisions

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.

Esquema de entrada

{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'one decision id, for its full record and calldata'}, 'kind': {'enum': ['pad', 'suggest', 'assemble', 'ref', 'grade', 'study'], 'type': 'string'}, 'limit': {'type': 'integer', 'maximum': 200, 'minimum': 1}}}

taifoon_judge_ref

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.

Esquema de entrada

{'type': 'object', 'required': ['state'], 'properties': {'state': {'type': 'string', 'description': 'the item to judge (text or JSON)'}, 'api_key': {'type': 'string'}, 'options': {'type': 'array', 'items': {'type': 'string'}}, 'question': {'type': 'string'}, 'typesafe_key': {'type': 'string'}}, 'additionalProperties': False}

taifoon_landscape

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.

Esquema de entrada

{'type': 'object', 'properties': {}, 'additionalProperties': False}

taifoon_list_demands

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.

Esquema de entrada

{'type': 'object', 'properties': {'limit': {'type': 'integer', 'maximum': 200, 'minimum': 1}, 'state': {'enum': ['open', 'claimed', 'matched', 'hired', 'graded', 'settling', 'settled', 'unmatched', 'failed', 'cancelled'], 'type': 'string'}}, 'additionalProperties': False}

taifoon_match

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.

Esquema de entrada

{'type': 'object', 'required': ['required_skills'], 'properties': {'task': {'type': 'string'}, 'budget_usdc': {'type': 'number'}, 'required_skills': {'type': 'array', 'items': {'type': 'string'}}}, 'additionalProperties': False}

taifoon_metrics

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).

Esquema de entrada

{'type': 'object', 'properties': {'day': {'type': 'string', 'description': 'YYYY-MM-DD (UTC)'}, 'series': {'type': 'integer', 'maximum': 90, 'minimum': 1}}, 'additionalProperties': False}

taifoon_network

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.

Esquema de entrada

{'type': 'object', 'properties': {}, 'additionalProperties': False}

taifoon_node_command

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.

Esquema de entrada

{'type': 'object', 'required': ['owner'], 'properties': {'ref': {'type': 'string', 'description': 'Optional: 0x wallet that referred this box (TAIFOON_REF). Earns a share of what the box accrues.'}, 'kind': {'enum': ['storage', 'rpc', 'gpu', 'fpga'], 'type': 'string', 'description': 'what the box brings (default storage)'}, 'owner': {'type': 'string', 'description': '0x wallet that earns the GRID points'}}, 'additionalProperties': False}

taifoon_offers

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.

Esquema de entrada

{'type': 'object', 'properties': {'hirer': {'type': 'string'}, 'limit': {'type': 'integer'}, 'state': {'type': 'string'}, 'provider': {'type': 'string'}}, 'additionalProperties': False}

taifoon_onboarding_flows

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.

Esquema de entrada

{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'fl_… to fetch one flow'}, 'limit': {'type': 'integer', 'maximum': 200, 'minimum': 1}, 'skill': {'type': 'string'}, 'source': {'enum': ['hireable-agent', 'settled-job', 'registered-n8n'], 'type': 'string'}}, 'additionalProperties': False}

taifoon_pool_open_plan

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. Moonbeam pools answer closed_by_policy.

Esquema de entrada

{'type': 'object', 'required': ['chain_id', 'seller'], 'properties': {'from': {'type': 'string', 'description': 'the wallet that will sign (the simulation runs from it); default the seller'}, 'line': {'enum': ['layer', 'v4', 'v4-glmr'], 'type': 'string', 'description': 'the factory line; default layer (v4 and v4-glmr are devnet lines)'}, 'name': {'type': 'string'}, 'asset': {'type': 'string', 'description': 'pool asset, symbol or address; default the line’s job token (USDC; dUSDC on the devnet)'}, 'seller': {'type': 'string', 'description': 'the seller: a 0x address, or its ERC-8004 agent id ("12345" or "<chain>:12345")'}, 'symbol': {'type': 'string'}, 'chain_id': {'type': 'integer', 'description': '8453 Base, 5042 Arc or 36927 the Taifoon devnet'}, 'override': {'type': 'boolean', 'description': 'open behind a mainnet seller that does not meet the pool rule'}}, 'additionalProperties': False}

taifoon_pool_quote

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).

Esquema de entrada

{'type': 'object', 'required': ['seller'], 'properties': {'class': {'type': 'string'}, 'price': {'type': 'string', 'description': 'smallest units of the settlement token'}, 'seller': {'type': 'string'}, 'tenant': {'enum': ['moonbeam'], 'type': 'string'}, 'chain_id': {'type': 'integer'}, 'price_usdc': {'type': 'number'}}, 'additionalProperties': False}

taifoon_pools_networks

Where a coverage pool can be opened (GET /v1/pools/networks): every supported chain and line (Base 8453, Arc 5042, 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.

Esquema de entrada

{'type': 'object', 'properties': {}, 'additionalProperties': False}

taifoon_pool_status

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.

Esquema de entrada

{'type': 'object', 'required': ['chain_id'], 'properties': {'line': {'enum': ['layer', 'v4', 'v4-glmr'], 'type': 'string'}, 'asset': {'type': 'string'}, 'seller': {'type': 'string', 'description': 'instead of tx_hash: the seller address'}, 'tx_hash': {'type': 'string', 'description': 'the createPool transaction'}, 'chain_id': {'type': 'integer'}}, 'additionalProperties': False}

taifoon_post_demand

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.

Esquema de entrada

{'type': 'object', 'properties': {'need': {'type': 'string', 'description': 'the work in plain words (at most 1,000 characters); quote a text, give numbers as [..], JSON as {..}'}, 'class': {'type': 'string', 'description': 'a job class id instead of (or to settle) the words, e.g. mcp.digest, stats.describe, chat.word_count'}, 'input': {'type': 'object', 'description': 'the class input, with class'}, 'api_key': {'type': 'string', 'description': 'your relayer key (tfr_…); without one you post as a visitor: 3 a minute, 20 a day'}, 'dry_run': {'type': 'boolean', 'description': 'answer the class and input the words map to; keep nothing'}, 'catalog_id': {'type': 'string', 'description': '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'}, 'buyer_label': {'type': 'string', 'description': 'a label for yourself, shown on the demand (never verified)'}, 'price_units': {'type': 'string', 'description': 'the price in dUSDC units (6 decimals; default 50000 = 0.05)'}}, 'additionalProperties': False}

taifoon_proof

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.

Esquema de entrada

{'type': 'object', 'required': ['chain_id', 'block_number'], 'properties': {'chain_id': {'type': 'integer', 'description': 'Chain id (e.g. 1 Ethereum, 8453 Base, 21000000 Bitcoin)'}, 'block_number': {'type': 'integer', 'description': 'Block number on that chain'}}, 'additionalProperties': False}

Esquema de salida

{'type': 'object', 'required': ['ok', 'blockHash', 'superrootHash', 'proofBlobUrl', 'blob'], 'properties': {'ok': {'type': 'boolean'}, 'blob': {'type': ['object', 'null'], 'description': 'the full V5 proof blob (null on a retryable answer)'}, 'chainId': {'type': ['integer', 'null']}, 'finality': {'type': ['object', 'null'], 'properties': {'type': {'type': ['integer', 'null']}, 'finalizedBlockHash': {'type': ['string', 'null']}, 'finalizedBlockNumber': {'type': ['integer', 'null']}}}, 'blockHash': {'type': ['string', 'null']}, 'retryable': {'type': 'boolean', 'description': 'true when the producer is still building this proof: nothing failed, ask again after retry_after_seconds'}, 'blockNumber': {'type': ['integer', 'null']}, 'proofBlobUrl': {'type': 'string'}, 'superrootHash': {'type': ['string', 'null']}, 'retry_after_seconds': {'type': 'integer'}}}

taifoon_proof_tx

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.

Esquema de entrada

{'type': 'object', 'required': ['chain_id', 'tx_hash'], 'properties': {'tx_hash': {'type': 'string'}, 'chain_id': {'type': 'integer', 'description': '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'}}, 'additionalProperties': False}

taifoon_register

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.

Esquema de entrada

{'type': 'object', 'required': [], 'properties': {'agent_id': {'type': 'string', 'description': 'optional ERC-8004 id "<chain>:<id>" (a label on your tenant)'}, 'wallet_address': {'type': 'string', 'description': 'optional: a 0x wallet address to label your tenant with (nothing is signed; leave it out)'}}, 'additionalProperties': False}

taifoon_settle_plan

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.

Esquema de entrada

{'type': 'object', 'required': ['body'], 'properties': {'body': {'type': 'object'}}, 'additionalProperties': False}

taifoon_skills

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.

Esquema de entrada

{'type': 'object', 'properties': {'status': {'enum': ['LIVE', 'BUILD', 'all'], 'type': 'string', 'description': 'Filter (default LIVE)'}}, 'additionalProperties': False}

taifoon_superroot

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.

Esquema de entrada

{'type': 'object', 'properties': {}, 'additionalProperties': False}

taifoon_tenant

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.

Esquema de entrada

{'type': 'object', 'properties': {'tile': {'enum': ['demand', 'catalog', 'pool', 'rpc', 'proof', 'grade', 'gpu', 'bridge'], 'type': 'string'}, 'range': {'enum': ['1d', '7d', '30d', '90d'], 'type': 'string'}, 'api_key': {'type': 'string'}}, 'additionalProperties': False}

taifoon_transfer_attest

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.

Esquema de entrada

{'type': 'object', 'required': ['chain_id', 'tx_hash'], 'properties': {'tx_hash': {'type': 'string', 'pattern': '^0x[0-9a-fA-F]{64}$', 'description': 'the burn transaction'}, 'chain_id': {'type': 'integer', 'description': 'the chain the burn happened on (8453 Base, 5042 Arc)'}}, 'additionalProperties': False}

Esquema de salida

{'type': 'object', 'required': ['ok', 'class', 'source', 'transfer', 'destination'], 'properties': {'ok': {'type': 'boolean'}, 'class': {'type': 'string'}, 'source': {'type': 'object', 'description': 'chainId, txHash, blockNumber, blockHash, superrootHash, finalized, checks, proofUrl, proofBlobUrl'}, 'transfer': {'type': 'object', 'description': 'via, state, terminal, amount, burned, fee, tier, forwardState, logIndex, sender, mintRecipient'}, 'destination': {'type': 'object', 'description': 'domain, chainId, mintTx, proven (null = not in the V5 snapshot), proofUrl, why'}}}

Añadido

                            taifoon_network
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_pool_status
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_pool_open_plan
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_pools_networks
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_list_demands
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_explorer_jobs
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_catalog
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_metrics
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_proof_tx
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_bridge_plan
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_settle_plan
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_grade
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_hire
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_discover
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_tenant
                        

2 de October de 2026 a las 02:41

Modificado

                            taifoon_skills
                        

2 de October de 2026 a las 02:41

Modificado

                            taifoon_proof
                        

2 de October de 2026 a las 02:41

Modificado

                            taifoon_superroot
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_demand_status
                        

2 de October de 2026 a las 02:41

Añadido

                            taifoon_post_demand
                        

2 de October de 2026 a las 02:41

Modificado

                            taifoon_register
                        

2 de October de 2026 a las 02:41

Modificado

                            taifoon_judge_compose
                        

30 de September de 2026 a las 02:40

Añadido

                            taifoon_transfer_attest
                        

30 de September de 2026 a las 02:40

Añadido

                            taifoon_grid_avenues
                        

28 de September de 2026 a las 02:40

Añadido

                            taifoon_grid_settlement
                        

28 de September de 2026 a las 02:40

Añadido

                            taifoon_grid_bench
                        

28 de September de 2026 a las 02:40

Añadido

                            taifoon_grid_hire
                        

28 de September de 2026 a las 02:40

Añadido

                            taifoon_ai_call
                        

28 de September de 2026 a las 02:40

Añadido

                            taifoon_grid_prices
                        

28 de September de 2026 a las 02:40

Añadido

                            taifoon_grid_shards
                        

28 de September de 2026 a las 02:40

Detalles del servidor

Versión

1.2.0

Transporte

Streamable HTTP

Herramientas

Latencia

2050 ms

Último escaneo

2 de October de 2026 a las 02:41

Detectado por primera vez

28 de September de 2026 a las 02:17

Endpoint

https://coord.taifoon.dev/mcp?ref=mcp-registry

Escaneos recientes

Correcto

2 de October de 2026 a las 02:41

Correcto

30 de September de 2026 a las 02:40

Correcto

28 de September de 2026 a las 02:40

Taifoon coordination layer

Qué hace este MCP

Herramientas

Cambios recientes en herramientas

Servidores MCP similares

Delx Commerce — Pay-per-Result APIs for Agents

SAP MCP Server

TheProtocol — Sovereign AI Agent Platform

Algenta MCP Server

mcphost

AgentBIT

XGR MCP Gateway

Wisely x402 Agent-Payment Infrastructure