FOGA node

MCP server · hosted · installable · v0.6.0-alpha.7 · io.github.garyyang-finchip/foga

Online · tested 1h agoNEW · 2h agoSeen in the registry 1h ago

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

What it does

FOGA node is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.

From the publisher's description, Electra Index matched it to one capability: procurement. That makes it a candidate for tasks such as manage procurement.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES

Local installYES

Live checkOnline · 13 tools

Version0.6.0-alpha.7

Packagesnpm

PriceNot in the registry

First seen03 Nov 2026

Last checked1h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)

Hosted endpoint

https://foga.finchip.ai/mcp streamable-http

In Claude Code: claude mcp add --transport http foga-node https://foga.finchip.ai/mcp

Install package

NPM @finchip.ai/foga v0.6.0-alpha.7 · runs locally (stdio)

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Live check

Electra Index connected to the hosted endpoint 1h ago

ONLINE FOGA node answered an MCP connection on 03 Nov 2026 and introduced itself as foga 0.6.0-alpha.7 (MCP protocol 2025-06-18).

13 tools offered to AI assistants

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 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.
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-v1 safety specification it adopted, its own policy block, the compatibility matrix of the ten 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 ten covenants, and the one command that makes a new cell. Pure data — no
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

Show 1 more

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.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Tasks it helps with

Share of each task's required capabilities it covers

Manage procurement

Procurement

33%

Similar tools

Listed for the same task: manage procurement

Whatic IC DatasheetsREMOTELOCAL
IC datasheet search: parametric part finding, spec lookup, price comparison — grounded in real PDFs
McpStamp Credit Notes and Purchase OrdersREMOTELOCAL
Purchase orders for suppliers: VAT line items, a delivery date, an A4 PDF, mark received
Boring APIREMOTELOCAL
Deterministic data tools: price list diff, PDF tables, feed validation, data mapping, table diff
SharpSyn (your account)REMOTELOCAL
Your SharpSyn account: quote requests and answers, price history, library; RFQs on confirm
Ny ProcurementREMOTELOCAL
New York State Procurement MCP — State contract awards & procurement (keyless)
OcrspaceREMOTELOCAL
OCR.space MCP — wraps the OCR.space API (ocr.space) for image/PDF → text OCR

Ready-made AI agents

An MCP server is a connector you add to your own assistant. These are finished products that do the same job for you:

Zip35
On quote · Prices & score →
Xelix32
On quote · Prices & score →
Cato32
On quote · Prices & score →
Tacto32
On quote · Prices & score →

All AI agents to manage procurement, ranked →

Facts & evidence

Each fact shows where it was seen and when.

Fact	Value	Evidence	Source	Last confirmed
Install package	@finchip.ai/foga	DECLARED	SRC-001 Official MCP Registry	1h ago
Hosted endpoint	https://foga.finchip.ai/mcp	DECLARED	SRC-001 Official MCP Registry	1h ago
Package registries	npm	DECLARED	SRC-001 Official MCP Registry	1h ago
Local install (package)	yes	DECLARED	SRC-001 Official MCP Registry	1h ago
Remote access (hosted)	yes	DECLARED	SRC-001 Official MCP Registry	1h ago
Website	https://foga.finchip.ai	DECLARED	SRC-001 Official MCP Registry	1h ago
Repository	https://github.com/garyyang-finchip/foga	DECLARED	SRC-001 Official MCP Registry	1h ago
Registry status	active	DECLARED	SRC-001 Official MCP Registry	1h ago
Version	0.6.0-alpha.7	DECLARED	SRC-001 Official MCP Registry	1h ago
MCP server	yes	DECLARED	SRC-001 Official MCP Registry	1h ago

Change history

NEW03 Nov 2026
first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Is FOGA node still online?

Free alerts · no account▲ 0

Do you run FOGA node? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor FOGA nodeLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Questions about FOGA node

How do I connect FOGA node?

Use the hosted endpoint https://foga.finchip.ai/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does FOGA node offer?

When Electra Index connected on 03 Nov 2026, it listed 13 tools: world_describe, identity_resolve, tender_list, tender_inspect, skill_list, skill_inspect, cell_status, kya_check and more. The full list is in "Live check" above.

Is FOGA node online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.

What can I use FOGA node for?

Based on its description, it is most relevant to: manage procurement.