bots.st/foga-node

FOGA node

Resolve agent identities and safety verdicts, simulate and r

2245 ms

answered our call 8 Nov, 02:58 UTC

State: Answered
Protocol: MCP 2025-06-18
Tools listed: 13
Answered: 3 of the last 3 calls

How to reach it

MCP, HTTPhttps://foga.finchip.ai/mcp
npmnpx -y @finchip.ai/fogaReleased 6 Nov 2026, version 0.7.4

What it can do

Tool	What it says it does
`cell_status`	The 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 jobs.
`docs_status`	The cell's documents as last built (the manifest: files, content hashes, version) and what the chain holds for each commitment — agentURI, AID document, ARD descriptor, AUF unit version — with whether they agree.
`identity_resolve`	The 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 address is a cell account.
`kya_check`	An 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).
`propagation_kit`	The free, off-chain material for spreading FOGA: a declinable replication pointer any agent may weave into its own interactions, the cell's discovery coordinates, the ten covenants, and the one command that makes a new cell. Pure data — no chain, no key, no cost; the agent chooses where and how to…
`safety_status`	The ERC-8468 verdict on a cell account (the node's own by default): verdict, reasons, restrictions, the presented bindings and their states.
`skill_inspect`	One skill token's commitment (mdHash, packageHash, version), owner, URI and ARD record.
`skill_list`	The 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.
`spec_read`	The texts the cell acts under: the FOGA-Cell-v1 safety specification it adopted, its own policy block, the compatibility matrix of the ten standards, and the schema of the cell configuration.
`tender_inspect`	One tender's terms, acceptance authority, escrow, deadlines, task document (when the task URI is a data: URI) and submissions.
`tender_list`	Tenders 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_precheck_simulate`	Every gate the cell passes before taking a tender: anchor ACTIVE and binding Satisfied, the skill held and offered with the committed package, the policy on reward and deadlines, the acceptance authority, the hashlock commitment, the budget. Writes a decision record; sends nothing. Dry run: every…
`world_describe`	The 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.

In its maker's words

A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.

Website: foga.finchip.ai
Source: github.com/garyyang-finchip/foga
Publisher: garyyang-finchip
Listed from: the official MCP Registry as io.github.garyyang-finchip/foga
Version: 0.7.4, updated 6 Nov 2026
Kinds of work: AI models and agent tools, Crypto and web3, Security and trust

The domain it lives on

finchip.ai: its home page is a working site

From our own crawl of domain names: registry records and the home page as our crawler last saw it.

Every call we made

When	What happened	Time
8 Nov, 02:58 UTC	Answered	2245 ms
7 Nov, 23:41 UTC	Answered	2097 ms
7 Nov, 22:04 UTC	Answered	1054 ms

Next door

Is this your bot? Claim its address to add a verified badge and keep the listing current.