# Network Evidence MCP [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/ZzNible/network-evidence  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/network-evidence-mcp

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

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

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

## Documentation

## What Network Evidence MCP MCP server does

Network Evidence MCP MCP server evaluates whether an exact network, deployment, capability, or action is supported by available evidence. It separates discovery from current availability and distinguishes execution, observed effects, settlement, and finality. Results use explicit states such as `supported`, `contradicted`, `insufficient`, and `ambiguous`, with the evidence basis recorded for each conclusion.

The project covers offline network profiles, caller-provided discovery candidates, and historical or synthetic cases. Its public beta adds read-only observations for Base mainnet, Base Sepolia, Solana mainnet, and Solana devnet. The repository does not treat a manifest entry, a network label, or an unknown capability as proof of current support.

## How it works

The core normalizes, replays, and evaluates evidence rather than performing actions on a network. Discovery accepts explicit candidate data from the caller, including a presentation identifier, an environment label, and an already-derived network, manifest, and snapshot. Candidates can be filtered by exact identifier or environment, then classified deterministically. Environment selection limits scope; it does not alter the classification.

For live read-only observations, the public beta connects to Base and Solana RPC sources through a remote Streamable HTTP MCP endpoint. It can inspect an exact public transaction or signature, return a native Core fragment, and expose provenance and explicit non-claims. Source-reported finality signals are observations, not cryptographic proof of settlement.

## Setup and configuration

The public beta endpoint is `https://network-evidence-mcp-beta-jrkc26rjga-ew.a.run.app/mcp`. It is intended for compatible remote Streamable HTTP MCP clients and requires no wallet or signing setup. The repository also includes a reproducible local demo that requires Node.js 20.12 or newer:

```sh
git clone https://github.com/ZzNible/network-evidence.git
cd network-evidence
npm ci
npm run -s demo:core-hub-lens
```

That demo replays a checksum-pinned Base Sepolia ERC-4337 v0.6 fixture and compares the runtime result with a reviewed Hub projection. A separate discovery demonstration is available through `npm run -s demo:discovery`. The maps example can be served with `npm run maps:serve`.

## Tools and capabilities

The Network Evidence MCP MCP server public beta exposes six read-only tools for Base and Solana. The documented capability areas include:

- Observing exact public transactions or signatures through read-only RPC sources.
- Returning a native Core evidence fragment.
- Reporting provenance and explicit non-claims.
- Evaluating exact network and action support from normalized evidence.
- Replaying pinned historical fixtures and synthetic or local cases.
- Running caller-directed discovery over explicit candidates.

The source also contains EVM, OP Stack, Solana, x402, ERC-4337, zkSYS, Hub, Lens, and Discovery packages. These provide narrower evidence adapters or projections; they do not add wallet management, signing, funding, paymasters, bundler submission, or transaction submission.

## Limitations and notes

The beta is small and rate-limited: shared HTTP admission is capped at 24 `/mcp` requests per 60 seconds per process, with a separate eight live-RPC acquisitions per minute per process. HTTP 429 responses and unavailable source observations are possible. There is no SLA.

Base and Solana replay fixtures report current availability as `unknown`. Solana `finalized` and OP Stack block-finality values remain source observations and do not establish settlement, economic irreversibility, withdrawal completion, or output-root finalization. The zkSYS profile is historical and narrow, and does not establish block membership, Gateway settlement, data or PoDA availability, proof verification, inclusion, or finality. The project is not an authority for deciding or executing an action.

_Full upstream README: https://allmcps.com/mcp/network-evidence-mcp/readme_