Skip to content

FOGA node MCP server

io.github.garyyang-finchip/fogagaryyang-finchipstreamable-httpv1.0.9Scanned

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

17 tools: 4 change things and 13 only read.

Tools: 0 delete, 0 irreversible, 4 write, 13 read.
  • Reads private data · 4
  • Reads text others write · 17
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the FOGA node MCP server can do

The FOGA node MCP server is published by the GitHub account garyyang-finchip. It has 17 tools. It can create or change data (4 tools: kya_check, propagation_kit, tender_precheck_simulate and flow_roles), but cannot delete data. 13 tools only read.

4 tools read private data (world_describe, tender_inspect, docs_status and 1 more); 17 tools bring in text other people can write (world_describe, identity_resolve, tender_list and 14 more); 1 tool can send data out of your system (flow_roles). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 1.0.9.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Changes things 4Claude Code: ask
  • 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 (b…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.channelId): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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 covena…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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, t…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 13Show 13 read-only tools
  • 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 operat…Reads text others writeNo findings

    Why it is in this group

    • The name "cell_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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 ve…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "docs_status" says "status": a word for reading.

    What it can reach

    • private-dataThe name "docs_status" says "status" and "doc": it reads documents.
    • private-dataThe description's first sentence says "document": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "uri": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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…Reads text others writeNo findings

    Why it is in this group

    • The name "flow_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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-846…Reads text others writeNo findings

    Why it is in this group

    • The name "identity_resolve" says "resolve": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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 f…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "meditate_status" says "status": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • safety_statusThe ERC-8468 verdict on a cell account (the node's own by default): verdict, reasons, restrictions, the presented bindings and their states.Reads text others writeNo findings

    Why it is in this group

    • The name "safety_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The ERC-8468 verdict on a cell account (the node's own by default): verdict, reasons, restrictions, the presented bindings and their states.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • skill_inspectOne skill token's commitment (mdHash, packageHash, version), owner, URI and ARD record.Reads text others writeNo findings

    Why it is in this group

    • The name "skill_inspect" says "inspect": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "uri": it reads web pages, which anyone can write.
    Description, as the server wrote it
    One skill token's commitment (mdHash, packageHash, version), owner, URI and ARD record.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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.Reads text others writeNo findings

    Why it is in this group

    • The name "skill_list" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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 stan…Reads text others writeNo findings

    Why it is in this group

    • The name "spec_read" says "read": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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 bor…Reads text others writeNo findings

    Why it is in this group

    • The name "spec_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • tender_inspectOne tender's terms, acceptance authority, escrow, deadlines, task document (when the task URI is a data: URI) and submissions.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "tender_inspect" says "inspect": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "uri": it reads web pages, which anyone can write.
    Description, as the server wrote it
    One tender's terms, acceptance authority, escrow, deadlines, task document (when the task URI is a data: URI) and submissions.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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).Reads text others writeNo findings

    Why it is in this group

    • The name "tender_list" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "world_describe" says "describe": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

68 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write17
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__foga__flow_roles"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://foga.finchip.ai/mcp: tools/list returned 17 tools to an anonymous client, including kya_check (write), propagation_kit (write), tender_precheck_simulate (write), flow_roles (write)

    What this check looks for

Posture changes

  1. Nov 11, 2026
    • Tools that change things, listed without credentials: 3 to 4

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 4.View diff
    • Tools that change things, listed without credentials: 3 to 4
  2. Tools1 added, 3 changed.+1 added~3 changedView diff
  3. Tools2 added, 1 changed.+2 added~1 changedView diff
  4. Tools1 added.+1 addedView diff

Install

Pinned to version 1.0.9. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__foga__world_describe",
      "mcp__foga__identity_resolve",
      "mcp__foga__tender_list",
      "mcp__foga__tender_inspect",
      "mcp__foga__skill_list",
      "mcp__foga__skill_inspect",
      "mcp__foga__cell_status",
      "mcp__foga__safety_status",
      "mcp__foga__spec_read",
      "mcp__foga__docs_status",
      "mcp__foga__meditate_status",
      "mcp__foga__flow_status",
      "mcp__foga__spec_status"
    ],
    "ask": [
      "mcp__foga__kya_check",
      "mcp__foga__propagation_kit",
      "mcp__foga__tender_precheck_simulate",
      "mcp__foga__flow_roles"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as foga. Review it before you use it.

Capability tags behind 17 rules
  • mcp__foga__world_describe private-data, untrusted-input
  • mcp__foga__identity_resolve untrusted-input
  • mcp__foga__tender_list untrusted-input
  • mcp__foga__tender_inspect private-data, untrusted-input
  • mcp__foga__skill_list untrusted-input
  • mcp__foga__skill_inspect untrusted-input
  • mcp__foga__cell_status untrusted-input
  • mcp__foga__kya_check untrusted-input
  • mcp__foga__safety_status untrusted-input
  • mcp__foga__spec_read untrusted-input
  • mcp__foga__propagation_kit untrusted-input
  • mcp__foga__tender_precheck_simulate untrusted-input
  • mcp__foga__docs_status private-data, untrusted-input
  • mcp__foga__meditate_status private-data, untrusted-input
  • mcp__foga__flow_status untrusted-input
  • mcp__foga__flow_roles untrusted-input, outbound
  • mcp__foga__spec_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.garyyang-finchip/foga/verify?hash=79b988c51538fce0c36ef10bd73413efb5aa0998dae1b88967999177334c32aa" | jq -e '.changed == false'

Pinned hash 79b988c51538, from Nov 13, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.garyyang-finchip/foga/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.garyyang-finchip/foga
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.garyyang-finchip/foga.svg)](https://radar.anlyon.com/servers/io.github.garyyang-finchip/foga)

Source: MCP Registry · repository. Synced Nov 13, 2026, 14:17 UTC.

FOGA node MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the FOGA node MCP server safe?

No scan can promise that. What its definitions show: 17 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the FOGA node MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the FOGA node MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the FOGA node MCP server have?

17 tools: 4 write, 13 read. kya_check, propagation_kit, tender_precheck_simulate, flow_roles, world_describe, identity_resolve, tender_list, tender_inspect and 9 more.

Does the FOGA node MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the FOGA node MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): flow_roles.

Has the FOGA node MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.