NestDaddy

FOGA node

io.github.garyyang-finchip/foga · v1.0.8

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

Connect Remote server

Terminal
claude mcp add --transport http foga https://foga.finchip.ai/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "foga": {
      "url": "https://foga.finchip.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "foga": {
      "type": "http",
      "url": "https://foga.finchip.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://foga.finchip.ai/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 17 found in our last check

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

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

  • 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_inspect

    One tender's terms, acceptance authority, escrow, deadlines, task document (when the task URI is a data: URI) and submissions.

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

  • skill_inspect

    One skill token's commitment (mdHash, packageHash, version), owner, URI and ARD record.

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

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

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

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

  • 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 ch…

  • 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 w…

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

  • 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 cycl…

  • 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 registr…

  • 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 subje…

  • 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…

Headers

NameDescription
Authorization
Optional, secret
Bearer <api key> for a caller the node's operator granted; without it the public reads and builds

Details

Endpointhttps://foga.finchip.ai/mcp (Streamable HTTP)
Package@finchip.ai/[email protected] (NPM, stdio)
First published13 Nov 2026
Last updated13 Nov 2026
Registry nameio.github.garyyang-finchip/foga

More ai and media servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.