FOGA node
by FastDrop
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy. Official MCP Registry: io.github.garyyang-finchip/foga@0.6.0-alpha.7. Remote endpoint: https://foga.finchip.ai/mcp
Problem it solves
Discoverable MCP server listed in the official MCP Registry.
How it's different
Remote MCP endpoint ingested from the official registry and probed by FastDrop.
Ingested from the official MCP Registry
FastDrop pulled this entry from the official MCP Registry as io.github.garyyang-finchip/foga and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed
and the description is not theirs.
If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.
Claim this listingTools this endpoint exposes
Read directly from the endpoint on 3 Nov 2026. Not supplied by the maker.
world_describeThe world this cell lives in: id, chain, network, the contracts by id, the bundle hash, and the latest doctor summary when a report sits next to the world file.
identity_resolveThe ten-ERC view of an address: ERC-8004 agent, ERC-8434 state in the reference and backing registries, ERC-8444 agent record, KYA level under the cell's standing scheme, ERC-8468 status when the addr
tender_listTenders minted within the lookback window (ERC-8414 TaskUpdated events), newest first; by default only those still open (funded, not cancelled, completions left, deadlines ahead).
tender_inspectOne tender's terms, acceptance authority, escrow, deadlines, task document (when the task URI is a data: URI) and submissions.
skill_listThe skill tokens a holder has: the cell's own from its configuration (verified against the chain), another holder's from the token's Transfer events in the lookback window.
skill_inspectOne skill token's commitment (mdHash, packageHash, version), owner, URI and ARD record.
cell_statusThe node's own cell: account and roles, anchor state in each registry, binding verdict, held and offered skills, policy summary; for the operator also the budget books, open operations and running job
kya_checkAn account's level under a KYA scheme as resolved by the registry for the given issuers (the cell's standing scheme and issuers by default).
Is this tool yours?
Claim this listing, then prove you own the domain with one DNS record: once it matches, the listing is yours right away.
Sign in to claim this listingSimilar launches
Matched on shared tags and the tools their MCP servers actually expose.
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Reviews
Sign in to leave a review.
No reviews yet.
Comments
Sign in to join the discussion.
No comments yet - start the discussion.