FET112
REMOTE · WWW.FET112.COM
Security intelligence for AI agents monitoring Ethereum before actions.
Available components
Last scanned (22 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Security
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 30 Oct 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 63
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 4 Nov 2026 · Probed https://www.fet112.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fet112.duckdns.org | CN=YE1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 66ccda6e52178b7f0a6c8d7eb76aeec003d |
| SANs: fet112.com, fet112.duckdns.org, www.fet112.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 www.fet112.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fet112.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 502 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.fet112.com/mcp | HTTP error | 502 | |
| http (plaintext) | http://www.fet112.com/mcp | Inconclusive | 404 |
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 →
fet112.analytics_catalog Native analytics capabilities ~35
Discover supported native metrics, exact semantics, aggregations, coverage requirements and executable query examples. No model or chain RPC calls.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fet112.analytics_query Native analytical query ~186
Execute a validated read-only native Fetch query: sums, extrema, weighted means, groupings, rollups and comparable UTC windows. Read analytics_catalog first. Missing coverage is an error, never zero. Top rankings cannot be combined across buckets. Amount maxima do not identify transaction hashes. Inspect integrity and consumer_policy; no native security or anomaly decision.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregation | string | – | – |
| chain_id | string | – | – |
| compare | string | – | – |
| dimension_filter | string|null | – | – |
| end_date | string|null | – | – |
| grain | string | – | – |
| group_by | array | – | – |
| limit | integer | – | – |
| metric | string | yes | – |
| order | string | – | – |
| period | string | yes | – |
| rollup | boolean | – | – |
| schema | string | – | – |
| start_date | string|null | – | – |
No output schema declared.
No examples provided.
fet112.network_state_attestation Native Fetch state attestation ~110
Attest observed native fetchhub-4 gas, transactions and blocks for the latest available finalized hour (four 15-minute windows). Signed coverage, source cursor, issue/expiry times and explicit fresh/stale/partial/unavailable observation status. No Ethereum data, native security verdict, anomaly assessment or live chain RPC. Optional content_hash retrieves an exact retained document; archive is process-local (up to 128 documents, one hour, lost at restart).
| Name | Type | Req | Description |
|---|---|---|---|
| content_hash | string | – | – |
No output schema declared.
No examples provided.
fet112.network_state_keys Native state signing key discovery ~29
Discover current Ed25519 public key and fingerprint. Discovery is not an independent trust anchor.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fet112.network_status FET112 Network Status ~56
Return FET112's current machine-facing network status. The verdict is copied from SecurityReportV1 for configured Fetch/ASI contracts on Ethereum (chain_id=1). Do not apply it to native fetchhub-4 traffic.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fet112.pre_action_check FET112 Pre-Action Check ~82
Deterministic pre-flight over the current watched Ethereum security environment. V1 commits the intended action but does not classify destination, amount, asset, business authorization or simulate the transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| amount | string | yes | – |
| asset | string | yes | – |
| destination | string | yes | – |
| metadata | object | – | – |
No output schema declared.
No examples provided.
fet112.recent_incidents FET112 Recent Incidents ~56
Return bounded recent incidents associated with the current signed report context.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string|null | – | – |
| limit | integer | – | – |
| severity | string|null | – | – |
| since_height | integer|null | – | – |
No output schema declared.
No examples provided.
fet112.security_report FET112 Signed Security Report ~43
Return the current signed SecurityReportV1 for configured Fetch/ASI contracts on Ethereum (chain_id=1). It does not evaluate native fetchhub-4 traffic.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fet112.staking_context Native Fetch Staking Flow ~116
Observed native Fetch staking FLOW on fetchhub-4 for today or yesterday UTC, using finalized 15-minute buckets and comparable historical periods. Returns exact afet strings, coverage and source cursor. This is NOT total staked balance, a statistical anomaly assessment, or a security verdict. Signature status is explicit in integrity.signed. Errors mean unavailable evidence, never zero flow. Defaults: today, 7 baseline days.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_days | integer | – | – |
| period | string | – | – |
| schema | string | – | – |
No output schema declared.
No examples provided.
fet112.transaction_activity Native Fetch Transactions and Success ~121
Native fetchhub-4 transactions included in blocks for today or yesterday UTC. Returns successful/failed/total counts, success percentage and average TPS over contiguous finalized 15-minute buckets. Empty periods with valid coverage have zero TPS and a NOT_APPLICABLE/null success percentage. Missing evidence returns an error, never zero activity. Not peak TPS, capacity, messages, or mempool attempts. Signature status is explicit in integrity.signed; no statistical anomaly or security verdict. Default: today.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | – |
| schema | string | – | – |
No output schema declared.
No examples provided.
fet112.transaction_comparison Native Fetch Same-Interval Comparison ~110
Compare native fetchhub-4 transactions TODAY and YESTERDAY over exactly the same elapsed UTC interval, ending at today's latest authoritative finalized cutoff. Both windows come from one SQLite snapshot. Returns counts, success rates, exact count difference and percentage change; unavailable coverage returns ErrorV1. No significance test, anomaly decision, cause attribution, forecast or native-chain security assessment. Follow consumer_policy. Inspect integrity.signed and verify the quantitative attestation before claiming verification.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | string | – | – |
No output schema declared.
No examples provided.
fet112.verify_attestation Verify FET112 Attestation ~60
Verify an arbitrary SecurityReportV1/attestation pair offline, optionally against a trusted FET112 key fingerprint.
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | object | yes | – |
| report | object | yes | – |
| trusted_key_fingerprint | string|null | – | – |
No output schema declared.
No examples provided.
fet112.verify_network_state_attestation Verify native state attestation ~52
Verify canonical signed payload, pinned identity, expiry and source age independently. No live chain canonicality check.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | yes | – |
| trusted_key_fingerprint | string|null | – | – |
No output schema declared.
No examples provided.
fet112.verify_quantitative_context Verify Native Quantitative Context ~64
Verify the separate native quantitative Ed25519 attestation and full consumer policy. Supply a trusted fingerprint to verify identity; does not evaluate chain canonicality, freshness or security.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| trusted_key_fingerprint | string|null | – | – |
No output schema declared.
No examples provided.
How do I install the FET112 MCP server?
FET112 is a hosted endpoint at https://www.fet112.com/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 · www.fet112.com
claude mcp add --transport http com-fet112-fet112 'https://www.fet112.com/mcp'
What is the FET112 MCP server?
FET112 is an MCP server listed in the public MCP registry as com.fet112/fet112. Security intelligence for AI agents monitoring Ethereum before actions. This page covers its hosted endpoint (https://www.fet112.com/mcp).
Is the FET112 MCP server safe to use?
FET112 scores 18 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 FET112 MCP server expose?
FET112 exposes 14 tools: fet112.network_state_attestation, fet112.verify_network_state_attestation, fet112.network_state_keys, fet112.analytics_catalog, fet112.analytics_query, and 9 more. Their descriptions and schemas cost roughly 1,120 tokens of context every time the server is loaded.
Does the FET112 MCP server require authentication?
Its publisher declares no required credentials for FET112. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the FET112 MCP server still maintained?
FET112 is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.