Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Network Evidence MCP
Overview
Description from the maker (original English)
Read-only offline network profiles, caller-supplied Discovery and historical/synthetic cases.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcpRun this in your terminal
claude mcp add --transport http network-evidence https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"network-evidence": {
"url": "https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"network-evidence": {
"type": "http",
"url": "https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account ZzNible, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 18372 servers in this category
- Published to the registry more recently than 61% of the other 18372 servers in this category
- Basic checks equal to or better than 100% of the other 18372 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Network Evidence MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.0.2) reached the registry 29 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, A1RO — Irish employment tools
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
A1RO — Irish employment tools
by A11RO
Irish temp worker cost, public holiday pay and holidays, and SafeHandle certificate checks.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Network Evidence
Independent network evidence for exact networks, capabilities and actions.
Network Evidence provides deterministic evidence infrastructure for two related questions:
- Discovery: what can an exact network or deployment support, and what is currently observable or usable with evidence?
- Resolution: what does the underlying network itself independently support about this exact action?
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.
Public MCP beta for agents — Base + Solana
Try the [six-tool Base + Solana read-only beta](docs/distribution/MCP_BASE_SOLANA_PUBLIC_BETA_QUICKSTART.md) in any compatible remote Streamable HTTP MCP client:
- MCP endpoint: https://network-evidence-mcp-beta-jrkc26rjga-ew.a.run.app/mcp
- Current supported live profiles: Base mainnet / Base Sepolia, Solana mainnet / Solana devnet.
- Read-only RPC observations: exact public transaction/signature, native Core fragment, provenance and explicit non-claims; source-reported block-finality signals are not cryptographic settlement proof.
- Small public beta (2026-10-11): shared 24 HTTP
/mcpadmissions per 60 seconds per process (not per user), plus a separate eight live-RPC acquisitions/minute/process cap. Cloud Run stays at one maximum instance and one concurrent request; HTTP 429 and unavailable source observations remain possible. No SLA, wallet, signing or submission. - Different product identities: source Suite release v1.1.0 is a source release; official MCP Registry v0.0.2 still lists the older offline three-tool endpoint. All three public endpoint health responses report runtime
0.0.1; use the exact URL and tool surface to identify the server. See the endpoint/version table and client-test boundaries. The beta is neither MCP COMPLETE v1 nor a public ChatGPT/Claude directory listing.
Connect and reproduce a Base/Solana agent call · Privacy and RPC provider disclosure · GitHub Issues.
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.
@nec/discovery is a thin public Discovery orchestrator above Core. A caller supplies requirements and explicit candidates (presentation id, explicit mainnet/testnet label, and an already-derived network, manifest and snapshot). It can filter by exact candidate id and by environment. Core composeDiscoveryMatch classifies each candidate, and Core builds and verifies the deterministic DiscoverNetworksResult. Environment selects scope only and never changes a classification. There is no network I/O, ranking, scoring or network choice. See packages/discovery/README.md. A deterministic, offline integration demo runs with npm run -s demo:discovery. It covers Base and Solana, mainnet and testnet, an external caller choice, and an evidence preflight for the chosen candidate. See examples/discovery/README.md.
This repository intentionally has fresh history. Its selected package content comes from frozen source snapshots, but private Git history is not imported. It is licensed under Apache-2.0.
Reproducible Core -> Hub -> Lens demo
A zero-secret public integration path is included for the reviewed Base Sepolia ERC-4337 v0.6 case.
Requires Node.js 20.12 or newer.
git clone https://github.com/ZzNible/network-evidence.gitcd network-evidence npm ci npm run -s demo:core-hub-lens
The command replays a checksum-pinned public fixture through @nec/resolver-evm, evaluates the exact UserOperation through @nec/adapter-erc4337, equality-checks that fresh runtime result against the reviewed exact-fixture F2 Hub projection, then emits the existing browser-safe Lens case.
The demo is exact-fixture and deterministic. It does not add wallet/signing/ submission, bundler attribution, settlement, finality, confidence scoring or policy authority. See examples/core-hub-lens/README.md and examples/core-hub-lens/PROVENANCE.md.
Minimal NE Maps atlas
examples/ne-maps/ presents a versioned ne-maps-case-collection/v0.1 — the three stable Suite v1 cases plus the clearly labelled synthetic/local integrability case — as a small generic/multichain evidence atlas. It validates the collection fail-closed and consumes pinned browser-safe Lens projections; it does not resolve network evidence or add a graph engine, policy layer or stronger claim. Each case exposes Lens, Trail and exact-action handoffs while preserving supported, contradicted, insufficient, ambiguous and unavailable states when present.
npm run maps:serveThen open http://127.0.0.1:4177/. TARGET_CORE_MUTATIONS = 0.
Release and reproducibility
- RELEASE.md — release status, package/version inventory and release artifacts.
v1.1.0is the latest public source release, published on 2026-10-08 fromde3ee11d08d22d2791d8b5acfe17c2e61df23e81; no package is published to npm and no hosted deployment is part of the release. - docs/release/REPRODUCTION.md — clean-machine reproduction with expected test counts and output digests.
- docs/INTEGRABILITY_V1_1.md — Hub/Lens/Maps contracts and the BEFORE + Discovery completion summary.
- docs/release/DEPENDENCY_ADVISORIES.md — release-gate dependency status and remediation record (
npm audit: 0 vulnerabilities observed on 2026-10-07 and 2026-10-08). - SECURITY_BOUNDARIES.md — evidence boundaries and the public/private boundary.