Network Evidence MCP Server
by zznibleio.github.ZzNible/network-evidencev0.0.2
Read-only offline network profiles, caller-supplied Discovery and historical/synthetic cases.
context tax
~1,835 tok/turn3 tools
security
pending
cold start
hosted
freshness
pending
Our reading of Network Evidence, from the data
Network Evidence is an MCP server from zznible, listed in the official MCP Registry.
Its 3 tools add about 1,837 tokens to every model turn (measured 2026-10-19).
It runs as a hosted endpoint, so there is nothing to install.
Install Network Evidence MCP server
Install in Claude Code
claude mcp add --transport http network-evidence https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcpInstall in Cursor
{
"mcpServers": {
"network-evidence": {
"url": "https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcp"
}
}
}Install in Claude Desktop
{
"mcpServers": {
"network-evidence": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcp"
]
}
}
}Or add it as a custom connector under Settings → Connectors. The config above bridges via mcp-remote.
Install in VS Code
{
"servers": {
"network-evidence": {
"type": "http",
"url": "https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcp"
}
}
}Install in Windsurf
{
"mcpServers": {
"network-evidence": {
"serverUrl": "https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcp"
}
}
}Remote endpoints
- streamable-http
https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcp
Context tax
Connecting this server adds ~1,837 tokens of tool definitions to every model turn (moderate, 3 tools). Measured 2026-10-19 via its hosted endpoint; o200k tokenizer, worst case for clients that load all tools up front. How we measure
| Model | Per 1,000 turns | With prompt caching |
|---|---|---|
| Claude Opus 5.5 | $7.35 | $0.367 |
| Claude Sonnet 5.5 | $3.67 | $0.367 |
| Claude Haiku 5.5 | $0.184 | — |
Input prices as of 2026-10-06. Excludes your own prompt and output.
Tools (3)
discover_network_candidates1,346 tokRuns 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 t
get_reviewed_evidence_case201 tokReturns 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_profiles135 tokReturns 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.
Freshness
Not enough public signals yet to judge maintenance.
Last commit (default branch)
2026-10-10 · 8d ago · GitHub
Latest release
2026-10-08 · 10d ago · GitHub · v1.1.0
Package published
no data · npm/PyPI
Registry entry updated
2026-10-09 · 9d ago · official registry · v0.0.2
FAQ
›How do I install the Network Evidence MCP server in Claude Code?
Run: claude mcp add --transport http network-evidence https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.
›Does Network Evidence require an API key?
No required environment variables are declared in its published metadata.
›Can I use Network Evidence as a remote (hosted) MCP server?
Yes. It is a hosted MCP server; connect to its URL with any client that supports remote MCP.
›Is Network Evidence in the official MCP registry?
Yes, as io.github.ZzNible/network-evidence.
›How many tokens does Network Evidence add to my context?
Its tool definitions total about 1,835 tokens, resent on every turn.
Sources and method
- Official MCP Registry entry
- updated 2026-10-09
- GitHub repository
- fetched 2026-10-19
- Tool list (tools/list), measured by us
- 2026-10-19
- Last checked against all sources
- 2026-10-19
The description, packages and links come from the maintainer's own published metadata. Token cost, security signals, freshness and the reading above are MCPSkillHub's own measurements; see the methodology. Spot an error? Request a correction or claim the listing.