World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 30/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 8/8 | The cloud endpoint answered at the last check |
| Usage score | 50/100 |
Quality: Passed 5/5 basic checks (shown, not used for ordering) · Momentum: 240 (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install FOGA node. Follow https://mcp.popnx.com/i/garyyang-finchip-foga.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (foga.finchip.ai) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
FOGA nodehttps://foga.finchip.ai/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsFOGA node
Use FOGA node and tell me what you can do for me, then show me one thing✓ If Claude says it is using FOGA node or shows a FOGA node tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
FOGA nodehttps://foga.finchip.ai/mcpStart a new chat and pick FOGA node from your plugins before typing
Use FOGA node and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using FOGA node or shows a FOGA node tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user foga https://foga.finchip.ai/mcpYou should see FOGA node listed as connected
Use FOGA node and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using FOGA node or shows a FOGA node tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use FOGA node and tell me what you can do for me, then show me one thing✓ If Cursor says it is using FOGA node or shows a FOGA node tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use FOGA node and tell me what you can do for me, then show me one thing✓ If VS Code says it is using FOGA node or shows a FOGA node tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://foga.finchip.ai/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user foga https://foga.finchip.ai/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"foga": {
"url": "https://foga.finchip.ai/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"foga": {
"type": "http",
"url": "https://foga.finchip.ai/mcp"
}
}
}Claude Code
claude mcp add --scope user foga -- npx -y @finchip.ai/foga node mcp --configClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"foga": {
"command": "npx",
"args": [
"-y",
"@finchip.ai/foga",
"node",
"mcp",
"--config"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"foga": {
"command": "npx",
"args": [
"-y",
"@finchip.ai/foga",
"node",
"mcp",
"--config"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"foga": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@finchip.ai/foga",
"node",
"mcp",
"--config"
]
}
}
}FOGA_OPERATOR_KEY_FILE envFOGA_RPC_URL envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @finchip.ai/fogaBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Tool names and descriptions exactly as the server reported them on Nov 15, 2026. The maker wrote them, not us; we show them as plain text.
world_describeThe 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_resolveThe 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_listTenders 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_inspectOne tender's terms, acceptance authority, escrow, deadlines, task document (when the task URI is a data: URI) and submissions.
skill_listThe 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_inspectOne skill token's commitment (mdHash, packageHash, version), owner, URI and ARD record.
cell_statusThe 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_checkAn 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_statusThe ERC-8468 verdict on a cell account (the node's own by default): verdict, reasons, restrictions, the presented bindings and their states.
spec_readThe 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_kitThe 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 cho
tender_precheck_simulateEvery 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 wh
docs_statusThe 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_statusWhat 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
flow_statusThe 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
flow_rolesThe 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 subjec
spec_statusWhich 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 v
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account garyyang-finchip, which owns the repo
Code last changed 6 days ago
Uses Apache-2.0
Responded in 406 ms (HTTP 200)
No sign-in needed
Read 17 tool descriptions and found no hidden instructions to the AI
No entries on OSV.dev for @finchip.ai/foga@1.0.9
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/garyyang-finchip-foga)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed 6 days ago, and the latest version (1.0.9) reached the registry 6 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one FOGA node | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
FOGA is a reference autonomous agent built on twelve Ethereum ERC drafts written by the same author:
| ERC | Title | Role in a cell |
|---|---|---|
| ERC-8338 | Token-Bound Executable Skills | what a cell can execute (hash-verified skill packages) |
| ERC-8414 | Token-Bound Task Tenders | the work a cell takes or offers (escrowed tenders) |
| ERC-8419 | Know-Your-Agent (KYA) Framework | how a cell proves facts about itself (attested and ZK-proved assertions) |
| ERC-8434 | Agent Identity (AID) | the address-anchored identity and liveness of a cell |
| ERC-8436 | Agent Collective Decision Framework (ACDF) | how cells decide together (authorized K-of-N decisions with finality) |
| ERC-8444 | Agentic Resource Discovery (ARD) Onchain | how cells, skills and tasks are found |
| ERC-8447 | Swarm AI Framework (SAI) | how cells organize into purpose-bound swarms |
| ERC-8454 | AIFi Unit Framework (AUF) | the economic boundary and measurement of a cell or swarm |
| ERC-8468 | Agent Safety Framework (ASF) | the safety specifications a cell adopts and the interventions it must honor |
| ERC-8471 | AI Dispute Resolution Framework (ADRF) | how claims about a cell's conduct are filed, ruled on and enacted |
| ERC-8490 | Agent Meditation Mechanism (AMM) | a cell's own maintenance: four layer state documents, a state version, a timeliness per layer (docs/meditation.md) |
| ERC-8489 | Agent Information Flow Paradigm (AIFP) | a cell's information flows: its own channel, its publications anchored, the market it is admitted to by its identity (docs/flows.md) |
ERC-8004 (Trustless Agents) is a required dependency: ERC-8419, ERC-8434 and ERC-8447 bind to its Identity Registry. ERC-8490 and ERC-8489 entered as extensions (0.8.0, 0.9.0; docs/extending.md) and are part of the base set since 1.0.0: the twelve-covenant cell is what FOGA-Cell-v2, the second version of the cell's safety specification, describes (docs/specification.md).
The project delivers three things from one kernel: the Finch OG Agent (the first running instance), the FOGA node software anyone can run with their own identity, model and wallet, and a public access layer (MCP, A2A, HTTP/CLI). It is built in phases; this repository has completed Phase 2c: the genesis on a public chain, on top of the Phase 2 genesis (T0–T9) and the Phase 1 world layer.
foga.probe/2, the genesis T0–T9 exercising both covenants and the doctor's layer 5 judging all twelve; 4b (0.9.0–0.9.1, 2026-11-09) — the cell's information flows (ERC-8489) as an extension: its own channel, its publications anchored, the market's admission by identity, four-valued roles; the OG bootstrapped Sepolia's flows (the family foga, the default market) and the packaged Sepolia world carries them; 4a (0.8.0–0.8.2, 2026-11-09) — the cell's own maintenance (ERC-8490) as an extension: a manual, recoverable, recomputable cycle, then the watcher that runs the cycles that fall due; 3e-1 (0.7.0, 2026-11-06) — foga join: a cell that lives on a public chain in one command, its card, work over the chain; Phase 3 done (0.6.0, 2026-11-05) — the OG live at foga.finchip.ai, the MCP registry listing, the Sepolia Loop D with an outside agent; 3d-2 (the wallet, signed callers, the documents on chain, preflight, A2A, Sourcify), 3d-1 (quickstart, an outside agent's Loop D), 3c (Loop D with a model), 3b (MCP and HTTP), 3a (the kernel as a node) all done4c (1.0.0, 2026-11-10). The twelve-covenant cell. ERC-8489 and ERC-8490, extensions in 0.8 and 0.9, are part of the base set: FOGA_COVENANTS names twelve covenants and ERC-8004, a world that lacks one says so (world.missing), and the local and Sepolia worlds carry all of it. FOGA-Cell-v2 is the second version of the cell's ERC-8468 safety specification (docs/specification.md): version 1's four clauses, enforced by the account as before, and three the runtime enforces — the state kept and maintained (ERC-8490), the self-description anchored in the cell's own channel (ERC-8489), a part in a shared context taken only under its rules through the account, a verifier's outcome reported as obtained. A cell born under 1.0.0 binds to version 2 and its account's requirement names it; a cell born before — its requirement fixed at deployment to version 1 — adopts version 2 as a second, runtime-enforced binding through its account (foga cell adopt), the account keeps enforcing version 1 through the binding it presents, a successor body (foga cell migrate) fixes version 2 in its own; the card, the manifest, spec_status and the preflight say which version the account enforces and which the runtime adopted. foga.probe/2 adds both covenants to the deterministic probe (the channels a subject is the authority of, its anchors, its market roles; its enrollment, state version and each layer's timeliness at the block), and foga cell skill update moves a held token to the program's new package (ERC-8338 updateSkill, the record re-committed, the lineage kept; since 1.0.2 a joined cell's own copy of the package is refreshed from the program's, so its token moves too). 1.0.3 takes up the first outside review: FogaCellAccount revision 3 asks for the owner before the operator, so a one-key cell moves its own assets (cell migrate, identity_transfer); a simulation changes nothing in any capability; the probe worker reaches the RPC on Node 25. 1.0.4 and 1.0.5 take up the first Windows runs: the skill worker starts there (the worker's path was a URL pathname), the card names the ERC-8004 registry, and the birth writes its flow documents (a file name was taken by splitting a path on /). 1.0.6 adds the release check (.github/workflows/release-check.yml): the tarball installed and run as a user runs it — demo --genesis T9, quickstart --exit — on Linux, macOS and Windows (PowerShell and Git Bash), on Node 22, 24 and 26, and on demand against a published version (docs/mcp.md, "The package"). 1.0.7 reads a tender's submission count and entries as one (anvil under automine can answer a call ahead of its block tag; the walk starts over from a fresh count). 1.0.8 has a join resume a birth interrupted after the account was deployed instead of taking the account for a birth (the birth's start and end are facts in the store). The genesis T0–T9 exercises both covenants end to end — the two specification versions, every cell's enrollment and channel, the supersede and the event cycle, the flow gate flipping when the demander is admitted, the stop reaching the upkeep and the flows, the successor's fresh enrollment and its channel naming the predecessor's as parent — 197 checks, 215 operations; the doctor's layer 5 judges all twelve from that evidence with nothing NotTested (deployments/local.genesis.example.json, local.doctor.example.json). 138 tests.
4a, first slice (0.8.0, 2026-11-09). A cell that lives for months changes — the program, its dependencies, its skills, its terms, its work, its store — and ERC-8490 (the Agent Meditation Mechanism, written by the same author) gives that change a registered shape: four layer state documents the cell keeps, commitments and a state version in a registry, a timeliness per layer. It enters FOGA as the eleventh covenant and an extension (docs/extending.md's five places; docs/meditation.md): the registry is in the plan and the local world (48 contracts), the upstream Sepolia instance is attached, World.covenants() lists ERC-8490 under world.extensions, the doctor covers it at layers 1–3 and says NotTested at layer 5 until a scenario exercises it; the base set is unchanged. src/core/amm.ts is the kernel's view — hashing held to the ERC's published vectors byte for byte (test/amm.test.ts) — and foga meditate run is the cycle (src/node/meditation.ts, meditation-cycle.ts, src/tools/meditation.ts): the routines run locally (the account's roles and allow-list, the skills' packages against their tokens, the store checked and compacted, the tenders in flight and the documents against the chain, the window's decisions), the four documents are rebuilt from the cell's *stable* state, one report goes through the account under the operator's new maintenance scope, and the version moves only when a commitment changed; what the node may not do alone becomes a candidate in the record, never an adoption. Every phase is a fact with the record and the report frozen, so an interrupted cycle resumes with the same calldata, a report mined while the node was away is reconciled before a new cycle begins, and anyone given the record and the documents re-derives every hash on chain. The kernel now tells pending from failed (OperationPending; the catalog keeps the job running at a pending gate and the same request resumes it) and a plan sizes its own fee reserve (gasPerStep). A cell born on a world with the registry enrolls at birth with the guardian as controller; a running cell is extended in place — foga cell extend --covenants 8490 adds the registry to its world file, opens the scope and enrolls, no migration. One authorization path: the account's; a one-key cell's owner pairs are opened for it alone and closed when the roles separate. meditate_status is a public read that says what FRESH means — a routine completed in time, not a certificate. Live the same day: the OG and a joined cell extended in place on Sepolia, their first cycles reported and recomputed from the served records (0.8.1 fixed what they showed). The second slice (0.8.2) is the watcher: with maintenance.auto on, the node runs a cycle when a required layer falls DUE or OVERDUE (a controller's demand among them) or when the runtime or memory-skills document drifted — over those layers alone, so each keeps its rhythm — bounded by the check pace, one cycle at a time, a cooldown that only an OVERDUE layer passes, and the budget; the same meditate_run, the same records, as the caller watcher. Not yet: the twelve-covenant base set (4c). 119 tests.
4b (0.9.0, 2026-11-09). A cell speaks about itself and takes part in a market, and ERC-8489 (the Agent Information Flow Paradigm, written by the same author) gives both a registered shape: a paradigm (the rules of a context: carriers, operators, thirteen dimensions, which role is acquired by which predicate), a channel that adopts one, role bindings, four-valued checks, anchors and disclosure records. It enters as the twelfth covenant and the second extension (docs/flows.md): the seven upstream contracts and FOGA's own FogaIdentityVerifier (the identity predicate: the subject's account owns an ERC-8004 identity and its ERC-8434 anchor is ACTIVE — the subject bound first, the registries fixed at deployment) are in the plan and the local world (56 contracts), the upstream Sepolia instances are attached, src/core/aifp.ts is the kernel's view (subject references, the JCS paradigm id, the predicate encoding and the descriptor validation held to the ERC's vectors, test/aifp.test.ts). FOGA registers two paradigms per world in the family foga: foga:cell-source/v1 (source + archive: one publisher, open observation, a pulled, immutable archive) and foga:tender-market/v1 (the public market — no intake label, since submissions are public; SUBMIT and RESPOND by the identity predicate; the TaskToken's events as the transport, without delivery records). A cell opens its own channel at birth with the account as authority and grants itself SUBMIT; every docs_publish anchors the publication (publish, then supersede; the same content never twice) and, with a public URL, records its disclosure to the public; flow_admit previews the identity predicate and admits the cell to the market, or refuses by the outcome the registry would obtain — NOT_SATISFIED, UNDETERMINABLE, VERIFIER_ERROR — never f