Local MCP capabilities provider for Expo
Nothing to run from here
FET112 is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
Security intelligence for AI agents monitoring Ethereum before actions.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http fet112-mcp https://www.fet112.com/mcp
# 2 — ask your agent for something these tools do
# fet112.network_state_attestation, fet112.verify_network_state_attestation, fet112.network_state_keys and 11 more
FET112 costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FEAll 1 server
fet1121 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http fet112-mcp https://www.fet112.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 pro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| content_hash | string | no | — |
Verify canonical signed payload, pinned identity, expiry and source age independently. No live chain canonicality check.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | object | yes | — |
| trusted_key_fingerprint | string/null | no | — |
Discover current Ed25519 public key and fingerprint. Discovery is not an independent trust anchor.
No parameter schema on file.
Discover supported native metrics, exact semantics, aggregations, coverage requirements and executable query examples. No model or chain RPC calls.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schema | string | no | — |
| chain_id | string | no | — |
| metric | string | yes | — |
| period | string | yes | — |
| start_date | string/null | no | — |
| end_date | string/null | no | — |
| grain | string | no | — |
| aggregation | string | no | — |
| group_by | array | no | — |
| dimension_filter | string/null | no | — |
| rollup | boolean | no | — |
| compare | string | no | — |
| order | string | no | — |
| limit | integer | no | — |
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-cha
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schema | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| context | object | yes | — |
| trusted_key_fingerprint | string/null | no | — |
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 attempt
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schema | string | no | — |
| period | string | no | — |
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. Defaul
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schema | string | no | — |
| period | string | no | — |
| baseline_days | integer | no | — |
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.
No parameter schema on file.
Return bounded recent incidents associated with the current signed report context.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| severity | string/null | no | — |
| since_height | integer/null | no | — |
| cursor | string/null | no | — |
Return the current signed SecurityReportV1 for configured Fetch/ASI contracts on Ethereum (chain_id=1). It does not evaluate native fetchhub-4 traffic.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | — |
| destination | string | yes | — |
| amount | string | yes | — |
| asset | string | yes | — |
| metadata | object | no | — |
Verify an arbitrary SecurityReportV1/attestation pair offline, optionally against a trusted FET112 key fingerprint.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report | object | yes | — |
| attestation | object | yes | — |
| trusted_key_fingerprint | string/null | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install FET112 or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest1ce6c800e0310a938c813405d944b93a7071a78625e464d8f032c4ac696a0544
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| fet112.network_state_attestation | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| fet112.verify_network_state_attestation | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| fet112.network_state_keys | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| fet112.analytics_catalog | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| fet112.analytics_query | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| fet112.transaction_comparison | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| fet112.verify_quantitative_context | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| fet112.transaction_activity | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| fet112.staking_context | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| fet112.network_status | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| fet112.recent_incidents | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| fet112.security_report | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| fet112.pre_action_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| fet112.verify_attestation | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest1ce6c800e0310a93
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish FET112 can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.