MCP.Market

Network Evidence MCP server

online · 93% uptime
by ZzNible·io.github.ZzNible/network-evidence·v0.0.2·1 stars

Read-only offline network profiles, caller-supplied Discovery and historical/synthetic cases.

B81/100grade B
What users say
No reviews yet
Be the first
Safety scan
B81/100

full report

Adoption
Growing

1 stars

Reviews

Write one

Nobody has reviewed Network Evidence MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Network Evidence MCP tools (3, 1 write)

write = sends, deletes, buys or posts
  • discover_network_candidateswrite actionFree

    Runs the real @nec/discovery discoverNetworks (classification by @nec/core only) over 1..16 EXPLICIT, complete, already-derived candidate contexts you supply (network + ResolverManifest + CapabilitySnapshot in nec-wire-json-v1 form) and Core DiscoveryRequirements. Returns the Core-built, Core-verified DiscoverNetworksResult with digests and per-candidate eligible/conditional/ineligible copied from Core. The outcome depends ONLY on the supplied snapshots; this server observes nothing and does NOT choose, rank or recommend a network. Any resolver-specific evidence preflight is external to this tool. Invalid or incoherent contexts fail closed with a coded error.

  • get_reviewed_evidence_caseFree

    Returns ONE case by exact id (f1, f2, f3, synthetic-local-core-golden) from the shipped, checksum-pinned examples/ne-maps/data/collection.json: the browser-safe Lens envelope verbatim (all limitations, unavailable/unknown states and nonClaims preserved), its source provenance and an explicit label. f1/f2/f3 are HISTORICAL reviewed exports of past public-network observations; synthetic-local-core-golden is a SYNTHETIC fixture, not a network observation. No case is live evidence.

  • list_network_profilesFree

    Returns the FIXED public profile inventory (Base mainnet eip155:8453, Base Sepolia eip155:84532, Solana mainnet, Solana devnet, zkSYS Tanenbaum testnet eip155:57057 replay-only) with each resolver manifest's DECLARED capabilities and the truth boundaries. Nothing is observed: every currentSupport/currentAvailability is 'not_assessed'. Profile membership is not live availability. Takes no arguments.

Public scan report

scanner v0.1.10 · 2026-10-09 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 763ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Network Evidence MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
81/100
higher than 62% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
33%
typical: 0%. Fewer write tools means less an agent can break
Uptime
93%
of our recent checks; the typical remote server answers 100%
Response time
225 ms
faster than 59% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers

What its tools let an agent do: 2 read · 1 change

Install Network Evidence MCP in Claude Code, Cursor or VS Code

claude mcp add --transport http network-evidence https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcp
Add to Cursor

What the publisher says

From the Network Evidence MCP repository's README, as published. We do not edit it. Read it on GitHub

Network Evidence

Independent network evidence for exact networks, capabilities and actions.

Network Evidence provides deterministic evidence infrastructure for two related questions:

currently observable or usable with evidence?

  • Discovery: what can an exact network or deployment support, and what is

about this exact action?

  • Resolution: what does the underlying network itself independently support

Discovery support is distinct from current availability. Manifest membership is not proof of current support or availability, and an unknown required capability is not eligible.

Network Evidence observes, normalizes, replays, and evaluates evidence. It is not a wallet, signer, transaction-submission tool, or authority for an action. It reports explicit verdicts: supported, contradicted, insufficient, or ambiguous. Every conclusion records its evidence basis. Execution, observed effect, settlement, and finality are separate questions; support for one is not support for another.

This source capsule contains @nec/core, @nec/resolver-evm, @nec/adapter-x402, @nec/resolver-opstack, @nec/adapter-erc4337, @nec/resolver-solana, @nec/adapter-x402-svm, @nec/resolver-zksys, @nec/hub, @nec/lens, and @nec/discovery. The Solana resolver is generic post-fact Solana network evidence; the x402 SVM adapter is x402 v2 exact-SVM interpretation above that generic Solana evidence. The ERC-4337 package is a narrow evidence-correlation adapter above generic EVM evidence.

The zkSYS resolver is a thin zkSYS Tanenbaum BEFORE profile for pure historical replay v0.1. Support does not imply current availability; archived replay gives current availability unknown. It adds only a narrow provider-reported block height-to-batch/range capability. It does not establish block-hash-to-batch membership, Gateway settlement, data or PoDA availability, proof verification, Syscoin inclusion, or finality. It is not wallet, signing, funding, paymaster, or submission infrastructure. Package manifests retain private: true to prevent accidental npm publication.

Base BEFORE parity uses the generic EVM BEFORE foundation plus a minimal OP Stack overlay in @nec/resolver-opstack. There are two explicit profiles: Base mainnet eip155:8453 (labelled mainnet) and Base Sepolia eip155:84532 (labelled testnet). The labels are presentation only and are never evidence. The overlay adds one capability, OP Stack L2 block finality, whose availability comes only from probe observations. It never claims settlement and never infers withdrawal or output-root finalization. Replaying the pinned archived fixtures gives current availability unknown. See packages/resolver-opstack/README.md.

Solana BEFORE support lives in @nec/resolver-solana. There are two explicit genesis-bound profiles: Solana mainnet solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp (labelled mainnet) and Solana devnet solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1 (labelled testnet). Each pins the full getGenesisHash result, and the labels are presentation only. The manifest claims execution, observedEffects, dataBinding and finality, never settlement. Availability comes only from probe observations of the post-action read path. A Solana finalized commitment is a source observation. It never establishes settlement or economic irreversibility. Replaying the pinned archived mainnet and devnet fixtures gives current availability unknown. See packages/resolver-solana/README.md.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Network Evidence MCP: common questions

Is Network Evidence MCP server safe?
Mostly: it is graded B (81/100). Read the Network Evidence MCP safety report
How do I install Network Evidence MCP?
It runs remotely at network-evidence-mcp-jrkc26rjga-ew.a.run.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Network Evidence MCP need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Network Evidence MCP maintained?
The last commit was 26 days ago (2026-10-09). The latest release is v0.0.2.
Is Network Evidence MCP up?
93% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Network Evidence MCP?
Servers from other publishers that do the same job: Firefox DevTools MCP server.
How does Network Evidence MCP compare with other MCP servers?
safety score 81/100 (higher than 62% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Network Evidence MCP

Same job from other publishers: the closest match first, then the best rated.

  • Firefox DevTools MCP
    Control and debug Firefox: navigate, fill forms, inspect network and console, profile.
    A