Network Evidence MCP Server

by zznible Your server? Claim it

answering

Network Evidence MCP is answering right now. Last checked 4 min ago. It exposes 3 tools. Last commit 11 Oct 2026.

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

Uptime history 9 days of history · worst day 99%

9 days agonow

99.4%

Uptime 24h

174 of 175 checks

Tools

read from the server

1916 ms

Response time

average over 24h

Stars

last commit 11 Oct 2026

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 October 2026. No other catalogue keeps this.

16 Oct a tool description was rewritten discover_network_candidates

15 Oct a tool description was rewritten discover_network_candidates

12 Oct a tool description was rewritten discover_network_candidates

Network Evidence MCP missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "network-evidence": {
      "url": "https://network-evidence-mcp-preview-jrkc26rjga-ew.a.run.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.network-evidence]
url = "https://network-evidence-mcp-preview-jrkc26rjga-ew.a.run.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "network-evidence": {
      "url": "https://network-evidence-mcp-preview-jrkc26rjga-ew.a.run.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "network-evidence": {
      "url": "https://network-evidence-mcp-preview-jrkc26rjga-ew.a.run.app/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

discover

discover_network_candidates

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.

network

list_network_profiles

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.

reviewed

get_reviewed_evidence_case

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.

Endpoints

URL	Transport	State	Latency	Checked
https://network-evidence-mcp-preview-jrkc26rjga-ew.a.run.app/mcp	streamable-http	answering	7846 ms	5 min ago
https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcp	streamable-http	answering	6593 ms	4 min ago

Alternatives to Network Evidence MCP

same job, measured the same way

my quant — finite market briefing

by beepboop2025

Read-only discovery for a finite, offline-capable market briefing with explicit evidence boundaries.

2 tools answering

Macaroon Network

by macaroonnetwork

Discover categories, governed sources, vertical MCPs, and x402 USDC products on Macaroon Network.

247 installs/wk local only

Seiche Agent Community

by beepboop2025

Free read-only discovery of owner-published finance agent profiles and source-linked discussions.

5 tools answering

Xahau MCP

by hugegreencandle

MCP server for the Xahau network — offline Hook WASM VM + static analyzer, read-only ledger tools.

58 installs/wk local only

MentionedOn Discovery Evidence Tools

by mentioned-on

Assess AI-discovery readiness, plan visibility fixes, and summarize scan evidence. Read-only.

3 tools answering

Raisely MCP by usefulapi

by usefulapi

Read campaigns, donations, profiles and supporters; record offline donations and upsert users.

23 tools answering

OSF CLI Go

by edithatogo

Read-only MCP tools for authenticated Open Science Framework projects and files.

local only

x402 Pay — USDC API Payment Helper

by scriptmasterlabs

Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.

5 tools answering

Network Evidence MCP — questions

Answers built from our own checks of this server.

What can Network Evidence MCP do?

It exposes 3 tools, read directly from the server on our last check. Among them: discover_network_candidates, get_reviewed_evidence_case, list_network_profiles. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Network Evidence MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 174 of 175 checks got a reply (99.4%), average response time 1916 ms. The bar chart above shows every period we have measured.

How do I connect Network Evidence MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Network Evidence MCP need an API key?

No. Network Evidence MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Network Evidence MCP?

It answers our handshake in 1916 ms on average, which is faster than 1% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Network Evidence MCP open source?

Yes — it is published under the Apache-2.0 licence, written in TypeScript, 1 stars on GitHub and 2 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.