mcpbeat Sign in

FOGA node MCP Server

by garyyang-finchip Your server? Claim it
answering

FOGA node is answering right now. Last checked 6 min ago. 974 installs a week from npm. It exposes 13 tools. Last commit 6 Nov 2026.

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

Installs per day peak 522 · avg 32
a month agotoday
Uptime history 4 days of history
4 days agonow
100.0%
Uptime 24h
92 of 92 checks
13
Tools
read from the server
460 ms
Response time
average over 24h
974
Installs / week
npm and PyPI

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 4 November 2026. No other catalogue keeps this.

6 Nov a tool changed version5 times that day
5 Nov a tool changed version2 times that day
4 Nov a tool changed version
and 5 more, back to 4 November 2026

What the code does

We read the source, 22 h ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command prover/build-predicate.mjs:36, src/genesis/zk.ts:125, [пакет] prover/build-predicate.mjs:36 и ещё 2 
  execFileSync(cmd, args, { stdio: "inherit", ...opts });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add foga --transport http https://foga.finchip.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://foga.finchip.ai/mcp
~/.codex/config.toml
[mcp_servers.foga]
url = "https://foga.finchip.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "foga": {
      "url": "https://foga.finchip.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "foga": {
      "type": "http",
      "url": "https://foga.finchip.ai/mcp"
    }
  }
}

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

tender
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 check and a simulation of the first call, a decision record, nothing sent.
skill
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.
cell
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
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
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
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
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 use it.
safety
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
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.
world
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.

Endpoints

URLTransportStateLatencyChecked
https://foga.finchip.ai/mcp streamable-http answering 448 ms 6 min ago

Alternatives to FOGA node

same job, measured the same way
agentgate
by ciceroyang

Read-only evidence for the tools agents run: MCP server records, coverage and policy.

79 installs/wk local only
AKKO MCP server for Trino
by ab2dridi

Read-only MCP server for Trino: queries run as the verified user, and Trino's own policies decide.

1 116 installs/wk local only
Rokha
by rokha

Search a registry of agent skills and MCP servers, then run them for real. No install, traced.

30 tools answering
Phlow MCP Server
by qompass

MCP server for the phlow agent runtime: bounded planner-coder-reviewer agent workflows.

local only
jev-ultrafast-mcp
by jiawei686

Hand browser work off to a server-side agent: read the page as a table, act, then verify.

169 installs/wk local only
NetBox MCP
by mhajder

MCP server for NetBox DCIM/IPAM with read-only and dry-run modes

240 installs/wk local only
E
Eclipse Deep Field MCP
by cyan-eclipse-technologies-llc

The governed database layer for agents — every store in one look, under policy: read-only by

local only
Plugolis
by plugolis

Search the Plugolis directory of MCP servers and step-by-step fixes for common MCP errors.

45 installs/wk local only

FOGA node — questions

Answers built from our own checks of this server.

What can FOGA node do?
It exposes 13 tools, read directly from the server on our last check. Among them: cell_status, docs_status, identity_resolve, kya_check, propagation_kit, safety_status and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is FOGA node mostly used for?
Its tools cluster around tender and skill. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is FOGA node working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 460 ms. The bar chart above shows every period we have measured.
How do I connect FOGA node?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does FOGA node need an API key?
No. FOGA node completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is FOGA node?
It answers our handshake in 460 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use FOGA node?
The npm package @finchip.ai/foga was installed 974 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is FOGA node open source?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at foga.finchip.ai, which runs on its operator's own terms.