FOGA node

io.github.garyyang-finchip/fogaVersion 1.0.9

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

Status

Responds386 msNov 14, 2026, 14:51 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:51 UTC
Latency: 386 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://foga.finchip.ai/mcpResponds386 msNov 14, 2026, 14:51 UTC

No sign-in

Claude Code

claude mcp add --transport http foga https://foga.finchip.ai/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: foga
Remote MCP server URL: https://foga.finchip.ai/mcp

Cursor

{
  "mcpServers": {
    "foga": {
      "url": "https://foga.finchip.ai/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"foga","type":"http","url":"https://foga.finchip.ai/mcp"}'

Streamable HTTP

npm: @finchip.ai/foga 1.0.9

Package only

npm (npx)

claude mcp add foga -- npx -y @finchip.ai/foga@1.0.9

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

17 tools

Tools of FOGA node
	Description		Read-only	Idempotent	Open world
`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.	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.	No	Yes	Yes	Yes
`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.	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.	No	Yes	Yes	Yes
`flow_roles`The participation registry's four-valued evaluation of a subject's roles in a channel at the current clock, the summary of role bits it reports, and the subject's bindings there (basis, interval, state). The subject is an address (its eip155-address reference), a canonical subject string or a bytes32 reference; the channel defaults to the market, then to the cell's own channel.	The participation registry's four-valued evaluation of a subject's roles in a channel at the current clock, the summary of role bits it reports, and the subject's bindings there (basis, interval, state). The subject is an address (its eip155-address reference), a canonical subject string or a bytes32 reference; the channel defaults to the market, then to the cell's own channel.	No	Yes	Yes	Yes
`flow_status`The cell's own channel (its id, paradigm, authority, state and transport bindings, the roles the cell holds in it, what it anchored and disclosed), the market it joins (the channel, its paradigm and authority, the roles the cell was admitted to — the historical roles the registry evaluates — and its current eligibility for them), and the registries of the world. A role SATISFIED is a role bound in the registry; it is not a judgment of the cell.	The cell's own channel (its id, paradigm, authority, state and transport bindings, the roles the cell holds in it, what it anchored and disclosed), the market it joins (the channel, its paradigm and authority, the roles the cell was admitted to — the historical roles the registry evaluates — and its current eligibility for them), and the registries of the world. A role SATISFIED is a role bound in the registry; it is not a judgment of the cell.	No	Yes	Yes	Yes
`identity_resolve`The multi-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.	The multi-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.	No	Yes	Yes	Yes
`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).	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).	No	Yes	Yes	Yes
`meditate_status`What the maintenance registry holds for the cell — enrollment, state version and root, per-layer commitments, timeliness (FRESH, DUE, OVERDUE), the activity signal, the policy in force — and what the node keeps beside it: the registered documents' version, the last cycle, a cycle in progress. FRESH means a routine completed within its interval; the cycle record says what was checked.	What the maintenance registry holds for the cell — enrollment, state version and root, per-layer commitments, timeliness (FRESH, DUE, OVERDUE), the activity signal, the policy in force — and what the node keeps beside it: the registered documents' version, the last cycle, a cycle in progress. FRESH means a routine completed within its interval; the cycle record says what was checked.	No	Yes	Yes	Yes
`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 twelve 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 use it.	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 twelve 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 use it.	No	Yes	Yes	Yes
`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.	The ERC-8468 verdict on a cell account (the node's own by default): verdict, reasons, restrictions, the presented bindings and their states.	No	Yes	Yes	Yes
`skill_inspect`One skill token's commitment (mdHash, packageHash, version), owner, URI and ARD record.	One skill token's commitment (mdHash, packageHash, version), owner, URI and ARD record.	No	Yes	Yes	Yes
`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.	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.	No	Yes	Yes	Yes
`spec_read`The texts the cell acts under: the FOGA cell safety specification it adopted (v1 at birth before 1.0.0, v2 since), its own policy block, the compatibility matrix of the twelve standards, and the schema of the cell configuration.	The texts the cell acts under: the FOGA cell safety specification it adopted (v1 at birth before 1.0.0, v2 since), its own policy block, the compatibility matrix of the twelve standards, and the schema of the cell configuration.	No	Yes	Yes	Yes
`spec_status`Which version of the FOGA cell specification the cell's account enforces (the binding it presents), which later version the runtime adopted (a second binding, when the cell was born before that version), the registry's verdict on the presented bindings, and this build's current version with its content hash — so a counterparty can tell a FOGA-Cell-v2 cell from one still under version 1.	Which version of the FOGA cell specification the cell's account enforces (the binding it presents), which later version the runtime adopted (a second binding, when the cell was born before that version), the registry's verdict on the presented bindings, and this build's current version with its content hash — so a counterparty can tell a FOGA-Cell-v2 cell from one still under version 1.	No	Yes	Yes	Yes
`tender_inspect`One tender's terms, acceptance authority, escrow, deadlines, task document (when the task URI is a data: URI) and submissions.	One tender's terms, acceptance authority, escrow, deadlines, task document (when the task URI is a data: URI) and submissions.	No	Yes	Yes	Yes
`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).	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).	No	Yes	Yes	Yes
`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 demander's SUBMIT role in the tender market when the policy requires it (ERC-8489, four-valued), the budget. Writes a decision record; sends nothing. Dry run: every check and a simulation of the first call, a decision record, nothing sent.	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 demander's SUBMIT role in the tender market when the policy requires it (ERC-8489, four-valued), the budget. Writes a decision record; sends nothing. Dry run: every check and a simulation of the first call, a decision record, nothing sent.	No	No	Yes	Yes
`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.	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.	No	Yes	Yes	Yes

Details

Registry status: Active
Published: Nov 13, 2026
Updated: Nov 13, 2026
Website: https://foga.finchip.ai/⁠ (opens in a new tab)
Repository: https://github.com/garyyang-finchip/foga⁠ (opens in a new tab)
Categories (suggested): SecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing