# FET112 (remote · www.fet112.com)

Security intelligence for AI agents monitoring Ethereum before actions.

- Trust score: 18/100 (low)
- Change this week: −47
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.fet112.com`: 18/100 (this document), [markdown](https://verifymcp.io/servers/com-fet112-fet112/www.md), [page](https://verifymcp.io/servers/com-fet112-fet112/www)

## Channel facts

- Endpoint: `https://www.fet112.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 502.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-fet112-fet112 'https://www.fet112.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-fet112-fet112": {
      "url": "https://www.fet112.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-fet112-fet112": {
      "type": "http",
      "url": "https://www.fet112.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-fet112-fet112]
url = "https://www.fet112.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-fet112-fet112": {
      "type": "remote",
      "url": "https://www.fet112.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-fet112-fet112 --url 'https://www.fet112.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-fet112-fet112:
    url: "https://www.fet112.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-fet112-fet112": {
      "Transport": "http",
      "Url": "https://www.fet112.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-fet112-fet112 -t streamable-http -u 'https://www.fet112.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-fet112-fet112": {
      "type": "http",
      "url": "https://www.fet112.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-30 (score 18, −47)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-29 (score 65, +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.

### 2026-10-27 (score 64, +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.

### 2026-10-26 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 63)

First indexed and scored.

## MCP tools (14)

### `fet112.network_state_attestation` (~110 tokens)

Native Fetch state attestation

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).

Input parameters:

- `content_hash` (string)

### `fet112.verify_network_state_attestation` (~52 tokens)

Verify native state attestation

Verify canonical signed payload, pinned identity, expiry and source age independently. No live chain canonicality check.

Input parameters:

- `document` (object, required)
- `trusted_key_fingerprint` (string|null)

### `fet112.network_state_keys` (~29 tokens)

Native state signing key discovery

Discover current Ed25519 public key and fingerprint. Discovery is not an independent trust anchor.

### `fet112.analytics_catalog` (~35 tokens)

Native analytics capabilities

Discover supported native metrics, exact semantics, aggregations, coverage requirements and executable query examples. No model or chain RPC calls.

### `fet112.analytics_query` (~186 tokens)

Native analytical query

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.

Input parameters:

- `aggregation` (string)
- `chain_id` (string)
- `compare` (string)
- `dimension_filter` (string|null)
- `end_date` (string|null)
- `grain` (string)
- `group_by` (array)
- `limit` (integer)
- `metric` (string, required)
- `order` (string)
- `period` (string, required)
- `rollup` (boolean)
- `schema` (string)
- `start_date` (string|null)

### `fet112.transaction_comparison` (~110 tokens)

Native Fetch Same-Interval Comparison

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.

Input parameters:

- `schema` (string)

### `fet112.verify_quantitative_context` (~64 tokens)

Verify Native Quantitative Context

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.

Input parameters:

- `context` (object, required)
- `trusted_key_fingerprint` (string|null)

### `fet112.transaction_activity` (~121 tokens)

Native Fetch Transactions and Success

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.

Input parameters:

- `period` (string)
- `schema` (string)

### `fet112.staking_context` (~116 tokens)

Native Fetch Staking Flow

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.

Input parameters:

- `baseline_days` (integer)
- `period` (string)
- `schema` (string)

### `fet112.network_status` (~56 tokens)

FET112 Network Status

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.

### `fet112.recent_incidents` (~56 tokens)

FET112 Recent Incidents

Return bounded recent incidents associated with the current signed report context.

Input parameters:

- `cursor` (string|null)
- `limit` (integer)
- `severity` (string|null)
- `since_height` (integer|null)

### `fet112.security_report` (~43 tokens)

FET112 Signed Security Report

Return the current signed SecurityReportV1 for configured Fetch/ASI contracts on Ethereum (chain_id=1). It does not evaluate native fetchhub-4 traffic.

### `fet112.pre_action_check` (~82 tokens)

FET112 Pre-Action Check

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.

Input parameters:

- `action` (string, required)
- `amount` (string, required)
- `asset` (string, required)
- `destination` (string, required)
- `metadata` (object)

### `fet112.verify_attestation` (~60 tokens)

Verify FET112 Attestation

Verify an arbitrary SecurityReportV1/attestation pair offline, optionally against a trusted FET112 key fingerprint.

Input parameters:

- `attestation` (object, required)
- `report` (object, required)
- `trusted_key_fingerprint` (string|null)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-fet112-fet112/www#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 18
- 2026-10-31: 18
- 2026-10-30: 18
- 2026-10-29: 65
- 2026-10-28: 64
- 2026-10-27: 64
- 2026-10-26: 63
- 2026-10-25: 63

## Common questions

### 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.fet112.com/mcp
- Website: https://www.fet112.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-fet112-fet112/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fet112-fet112/www.json
- HTML version of this page: https://verifymcp.io/servers/com-fet112-fet112/www