Network Evidence MCP

io.github.ZzNiblev0.0.1更新于 Oct 9, 2026

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

已验证Streamable HTTP可网页运行Developer ToolsSecurity & Monitoring

概览

AI 生成的概览

只读的网络证据服务器，用于报告某个确切网络或部署是否支持某项能力或操作，并给出明确结论。

功能
Network Evidence 为两类问题提供确定性的离线证据基础设施：Discovery（某个确切网络或部署能支持什么、当前可观测到什么）与 Resolution（底层网络本身对某个确切操作独立支持什么）。它会观测、规范化、重放并评估证据，给出明确结论：supported、contradicted、insufficient 或 ambiguous，且每个结论都记录其证据依据。它明确不是钱包、签名器、交易提交工具，也不是某项操作的授权方。
适用场景
当你需要独立、可复现地核查某个网络、部署或操作是否有证据支持，而不是依赖当前可用性的声明时使用。它适合证据预检、对固定夹具的历史重放，以及比较 Base 与 Solana 主网或测试网等候选配置。
运行要求
清单声明为远程 streamable HTTP 端点，未声明认证、环境变量或请求头。README 中的本地演示需要 Node.js 20.12 或更高版本、npm 安装以及克隆该仓库；Discovery 演示为离线且确定性。
安装前请注意
README 说明它不是钱包、签名器、交易提交工具或操作授权方，且支持并不代表当前可用；归档重放得到的可用性为 unknown。supported 等结论只覆盖所问的具体问题，执行、观测效果、结算与最终性是彼此独立的问题。清单未要求任何凭据。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Network Evidence MCP，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

README

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.

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.

sh
git clone https://github.com/ZzNible/network-evidence.gitcd network-evidencenpm cinpm 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.

sh
npm run maps:serve

Then 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.0 is the latest public source release, published on 2026-10-08 from de3ee11d08d22d2791d8b5acfe17c2e61df23e81; 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.

来源：README.md，提交 46e6600

工具

0
工具元数据尚未被收录。

版本历史

1
  1. v0.0.1最新Oct 9, 2026