FOGA node
REMOTE · FOGA.FINCHIP.AI · 2 COMPONENTS
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
Available components
Last scanned (3 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1104 tokens (~58/item across 19 items; 13 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.6.0-alpha.7 → 0.6.0 functional
- 3 Nov 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://foga.finchip.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=foga.finchip.ai | CN=YE2,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 624537a05e193b7831a96dd7cea308cf434 |
| SANs: foga.finchip.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of foga.finchip.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| finchip.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://foga.finchip.ai/mcp | Verified | 200 | |
| http (plaintext) | http://foga.finchip.ai/mcp | HTTPS enforced | 308 | https://foga.finchip.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cell_status The cell's status ~49
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | – |
| accountVersion | number | yes | – |
| agentId | – | yes | – |
| budget | – | yes | – |
| guardian | string | yes | – |
| liveness | array | yes | – |
| name | string | yes | – |
| open | – | yes | – |
| operator | string | yes | – |
| owner | string | yes | – |
| policy | object | yes | – |
| safety | object | yes | – |
| skills | object | yes | – |
No examples provided.
docs_status Documents: built and on chain ~56
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | yes | – |
| manifest | – | yes | – |
| onChain | object | yes | – |
| pending | array | yes | – |
| readBack | array | yes | – |
No examples provided.
identity_resolve Resolve an identity ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| agent | – | yes | – |
| aid | string | yes | – |
| isContract | boolean | yes | – |
| liveness | array | yes | – |
| record | – | yes | – |
| safety | – | yes | – |
| standing | – | yes | – |
No examples provided.
kya_check Check a KYA level ~70
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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| issuers | array | – | – |
| minLevel | integer | – | – |
| schemeId | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| assertionId | string | yes | – |
| expiresAt | number | yes | – |
| issuers | array | yes | – |
| level | number | yes | – |
| meets | boolean|null | yes | – |
| schemeId | string | yes | – |
No examples provided.
propagation_kit Propagation kit ~78
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| cell | object | yes | – |
| covenants | array | yes | – |
| discovery | object | yes | – |
| endpoints | object | yes | – |
| program | object | yes | – |
| replication | object | yes | – |
| schema | string | yes | – |
| skills | array | yes | – |
No examples provided.
safety_status Safety status ~46
The ERC-8468 verdict on a cell account (the node's own by default): verdict, reasons, restrictions, the presented bindings and their states.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| bindings | array | yes | – |
| reasons | array | yes | – |
| restrictions | array | yes | – |
| verdict | string | yes | – |
No examples provided.
skill_inspect Inspect a skill ~39
One skill token's commitment (mdHash, packageHash, version), owner, URI and ARD record.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| mdHash | string | yes | – |
| name | string|null | yes | – |
| owner | string | yes | – |
| packageHash | string | yes | – |
| record | – | yes | – |
| skillURI | string | yes | – |
| tokenId | string | yes | – |
| version | number | yes | – |
No examples provided.
skill_list List skills ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| holder | string | – | – |
| lookbackBlocks | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| holder | string | yes | – |
| offered | array | yes | – |
| skills | array | yes | – |
No examples provided.
spec_read Read a rule text ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| mediaType | string | yes | – |
| name | string | yes | – |
| text | string | yes | – |
No examples provided.
tender_inspect Inspect a tender ~45
One tender's terms, acceptance authority, escrow, deadlines, task document (when the task URI is a data: URI) and submissions.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceAuthority | string | yes | – |
| asset | string | yes | – |
| cancelled | boolean | yes | – |
| completions | number | yes | – |
| demander | string | yes | – |
| escrowWei | string | yes | – |
| maxCompletions | number | yes | – |
| rewardWei | string | yes | – |
| settleBy | number | yes | – |
| submissions | array | yes | – |
| submitBy | number | yes | – |
| task | – | yes | – |
| taskHash | string | yes | – |
| taskURI | string | yes | – |
| tdHash | string | yes | – |
| tokenId | string | yes | – |
| version | number | yes | – |
No examples provided.
tender_list List tenders ~72
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).
| Name | Type | Req | Description |
|---|---|---|---|
| includeClosed | boolean | – | – |
| limit | integer | – | – |
| lookbackBlocks | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| fromBlock | number | yes | – |
| tenders | array | yes | – |
| toBlock | number | yes | – |
No examples provided.
tender_precheck_simulate Pre-check a tender (dry run) ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| decisionId | number|null | – | – |
| eligible | boolean | yes | – |
| gate | string | – | – |
| jobId | string|null | – | – |
| reason | string | – | – |
| result | object | – | – |
No examples provided.
world_describe Describe the world ~46
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleHash | string | yes | – |
| chainId | number | yes | – |
| contracts | object | yes | – |
| doctor | – | yes | – |
| network | string | yes | – |
| worldId | string | yes | – |
No examples provided.
How do I install the FOGA node MCP server?
FOGA node is a hosted endpoint at https://foga.finchip.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · foga.finchip.ai
claude mcp add --transport http garyyang-finchip-foga 'https://foga.finchip.ai/mcp'
What is the FOGA node MCP server?
FOGA node is an MCP server listed in the public MCP registry as io.github.garyyang-finchip/foga. A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy. This page covers its hosted endpoint (https://foga.finchip.ai/mcp).
Is the FOGA node MCP server safe to use?
FOGA node scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FOGA node MCP server expose?
FOGA node exposes 13 tools: world_describe, identity_resolve, tender_list, tender_inspect, skill_list, and 8 more. Their descriptions and schemas cost roughly 782 tokens of context every time the server is loaded.
Does the FOGA node MCP server require authentication?
No. We connected to FOGA node without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FOGA node MCP server still maintained?
FOGA node is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.