Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Taifoon coordination layer is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
37
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Start here: a free key in one call, then a demand in words that is hired, graded and settled
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http taifoon-coordination-layer-mcp 'https://coord.taifoon.dev/mcp?ref=mcp-registry'
# 2 — ask your agent for something these tools do
# taifoon_superroot, taifoon_proof, taifoon_finality_explain and 34 more
Taifoon coordination layer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TAAll 1 server
taifoon1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http taifoon-coordination-layer-mcp 'https://coord.taifoon.dev/mcp?ref=mcp-registry'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
37 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Current Taifoon superroot: the one value 60+ chains resolve to every ~10s, with the chains included. The settlement referent for the whole coordination layer.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
The live skills catalog: every skill in the bank with price, rails (x402/acp/mcp), and status. LIVE rows are purchasable now via the x402 payout gateway.
No parameter schema on file.
Register an agent wallet for a free explorer-tier Taifoon API key (no payment). Returns the api_key. POSTs to the live /api/v1/register.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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
No parameter schema on file.
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.
No parameter schema on file.
Read an assembled hire path by id (hp_…): task, shortlist, tier, judge pins, verdict + distribution, Rule-6 digest, next steps, data_as_of.
No parameter schema on file.
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.
No parameter schema on file.
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 handshak
No parameter schema on file.
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 Base ERC-8183 job_id
No parameter schema on file.
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.
No parameter schema on file.
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
No parameter schema on file.
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.
No parameter schema on file.
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 conf
No parameter schema on file.
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: reg
No parameter schema on file.
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 calibrat
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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 → assur
No parameter schema on file.
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
No parameter schema on file.
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.
No parameter schema on file.
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 v
No parameter schema on file.
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 · RAN
No parameter schema on file.
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 i
No parameter schema on file.
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. Settlemen
No parameter schema on file.
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, th
No parameter schema on file.
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.
No parameter schema on file.
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-l
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Taifoon coordination layer or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Taifoon coordination layer can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.