MCP 服务器

EVIDIQ Lineage

Deterministic supply-chain provenance, SBOM/AI-BOM generation, and dependency risk analysis for npm and PyPI packages, with 14 security rules and verifiable reports.

README

<h1 align="center">EVIDIQ Lineage</h1>

Deterministic supply-chain provenance, SBOM/AI-BOM generation, and dependency risk analysis.

Inspect · Prove · Audit — analyze npm and PyPI package manifests, detect typosquatting and malicious IOCs, and generate signed SBOMs for AI-generated code.

<a href="https://evidiq.dev">evidiq.dev</a> · <a href="https://evidiq.dev/docs/lineage">Lineage Docs</a> · <a href="https://mcp.evidiq.dev/lineage/skill.md">Agent Skill</a> · <a href="https://github.com/evidiq/evidiq">EVIDIQ Main</a> · <a href="https://github.com/evidiq/evidiq-lineage-mcp">Lineage MCP</a>

AI agents frequently generate, install, and execute code containing external package dependencies. Verifying which packages exist, whether they are typosquatted or malicious, and which licenses apply before execution is essential to supply-chain integrity.

EVIDIQ Lineage is the deterministic supply-chain provenance layer for the agent economy. It evaluates npm and PyPI package manifests against a 14-rule security risk engine, queries live OSV.dev advisories, audits licenses, and generates standard CycloneDX 1.6 / SPDX 3.0 SBOMs and CycloneDX-AI-1.6 AI-BOMs. Every report ships a SHA-256 integrity digest and an EIP-191 signature.

Launch status: live endpoint. The MCP server is deployed at https://mcp.evidiq.dev/lineage/mcp, paid calls settle through the official OKX Payment SDK, and the OKX.AI listing (Agent #9575) is under review.

What it does

14 Deterministic Risk Rules — Typosquatting detection, malicious package IOC matching, live OSV advisories, lifecycle install-script flags, Copyleft license conflicts, and unpinned wildcard dependencies.
npm & PyPI Ecosystem Support — Parses package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, requirements.txt, pyproject.toml, and poetry.lock.
SBOM Generation — CycloneDX 1.6 and SPDX 3.0 Software Bill of Materials.
AI-BOM Generation — CycloneDX-AI-1.6 for tracking AI models, training datasets, and TEE runtimes.
License Auditing — Detects Copyleft (GPL/AGPL), incompatible, missing, or unknown licenses.
Package Claim Verification — Queries npm/PyPI registries directly to confirm package existence and maintainer metadata.
Verifiable Reports — EIP-191 signed SHA-256 report digests and content-addressed artifacts.
Pay Per Analysis — Five paid tools cost 0.005–0.03 USDT0; five discovery and preflight tools are free.

Route to Lineage when

Use Lineage when an agent needs to verify dependency risk before installation, audit package licenses, generate standard SBOM or AI-BOM specifications, check package registry claims, or verify cryptographic lineage reports.

Do not route runtime network monitoring or live endpoint security to Lineage (use EVIDIQ Sentinel for endpoint/skill security scanning). Lineage focuses strictly on software components and supply-chain provenance.

Use it from any agent

# Read the public Skill document
curl -s https://mcp.evidiq.dev/lineage/skill.md

# Inspect current x402 pricing discovery
curl -s https://mcp.evidiq.dev/lineage/x402

# Connect the remote MCP server (Claude Code)
claude mcp add --transport http evidiq-lineage https://mcp.evidiq.dev/lineage/mcp

Public endpoints:

Endpoint	Purpose
`https://mcp.evidiq.dev/lineage/mcp`	Remote MCP transport
`https://mcp.evidiq.dev/lineage/skill.md`	Agent-readable usage and safety guide
`https://mcp.evidiq.dev/lineage/x402`	x402 v2 pricing and payment discovery
`https://mcp.evidiq.dev/lineage/health`	Service health
`https://evidiq.dev/docs/lineage`	Technical documentation

MCP tools

Paid analysis & BOM generation

Tool	Cost	Atomic	Description
`verify_package_claim`	`0.005 USDT0`	`5000`	Query npm/PyPI registry to verify package existence, version, and publisher metadata
`audit_licenses`	`0.01 USDT0`	`10000`	Audit manifest dependencies for Copyleft (GPL/AGPL) or incompatible licenses
`generate_sbom`	`0.015 USDT0`	`15000`	Generate standard CycloneDX 1.6 or SPDX 3.0 Software Bill of Materials
`scan_dependencies`	`0.02 USDT0`	`20000`	Execute full 14-rule supply-chain risk engine + live OSV vulnerability checks
`generate_aibom`	`0.03 USDT0`	`30000`	Generate CycloneDX-AI-1.6 AI-BOM for models, datasets, and TEE runtimes

Free preflight and verification

Tool	Cost	Description
`lineage_capabilities`	Free	Formats, dataset versions, 14 rules catalog, and full tool pricing
`validate_manifest`	Free	Validate manifest or lockfile syntax without network calls or payment
`estimate_cost`	Free	Return exact atomic and human-readable price for any paid tool
`verify_lineage_report`	Free	Cryptographically verify EIP-191 signature and SHA-256 report digest
`get_artifact`	Free	Retrieve a stored Lineage report or BOM artifact by ID

14 Deterministic Security Rules

TYPOSQUATTING — Detects typosquatted names against top 1000 popular package catalogs.
MALICIOUS_IOC — Matches dependencies against bundled malicious package IOC database.
OSV_VULNERABILITY — Queries OSV.dev for active CVEs and security advisories.
INSTALL_SCRIPTS — Flags lifecycle install scripts (preinstall, postinstall).
LICENSE_CONFLICT — Flags Copyleft licenses (GPL/AGPL) violating commercial policy.
LICENSE_UNKNOWN — Identifies missing or unrecognized package licenses.
UNPINNED_DEPENDENCY — Flags wildcards (*, latest, >=) that risk supply-chain takeover.
HALLUCINATED_PACKAGE — Detects non-existent package names in AI-generated manifests.
SUSPICIOUS_MAINTAINER — Identifies disposable or newly created maintainer accounts.
PROVENANCE_MISSING — Flags components lacking source repository URLs.
PROVENANCE_UNVERIFIED — Detects tag/commit hash mismatches.
COMPONENTS_EXCEEDED — Flags unexpected component inflation (>500 packages).
UNSUPPORTED_MANIFEST — Flags malformed or unrecognized manifest structures.
ADVISORY_DEGRADED — Signals remote advisory API unavailability.

How a Lineage scan works

Lineage parses the manifest or lockfile into a normalized LineageComponent[] graph.
A paid tool clears the x402 v2 payment gate before execution begins.
The 14-rule engine evaluates deterministic static rules against the component graph.
Live OSV.dev advisories are queried in parallel for known CVEs.
Verdict (PASS or BLOCK) and score (0–100) are computed deterministically.
Report SHA-256 digest and EIP-191 signature are generated.
Output artifacts (Report / SBOM / AI-BOM) are saved to storage.
Response is returned with reportId, artifactId, scanResult, and report.

Report and artifact integrity

A paid scan response contains:

scanResult — structured verdict, score, total components count, and findings array.
report — complete result, component metadata, integrity digest, signature, and signer.
reportId — deterministic ID starting with lin-.
artifactId — content-addressed artifact ID starting with art-.

verify_lineage_report verifies the integrity digest and EIP-191 signature to guarantee the report has not been tampered with since issuance.

Pricing and x402

Operation	Cost	Token	Network	Atomic
`verify_package_claim`	`0.005`	USDT0	X Layer (`eip155:196`)	`5000`
`audit_licenses`	`0.01`	USDT0	X Layer (`eip155:196`)	`10000`
`generate_sbom`	`0.015`	USDT0	X Layer (`eip155:196`)	`15000`
`scan_dependencies`	`0.02`	USDT0	X Layer (`eip155:196`)	`20000`
`generate_aibom`	`0.03`	USDT0	X Layer (`eip155:196`)	`30000`
`lineage_capabilities`	Free	—	—	—
`validate_manifest`	Free	—	—	—
`estimate_cost`	Free	—	—	—
`verify_lineage_report`	Free	—	—	—
`get_artifact`	Free	—	—	—

Asset: USDT0 (6 decimals) on X Layer (eip155:196), contract 0x779ded0c9e1022225f8e0630b35a9b54be713736.

Official OKX Payment SDK

Payment verification and settlement run through the official OKX Onchain OS Payment SDK:

Package	Role
`@okxweb3/x402-core`	`OKXFacilitatorClient` (HMAC-SHA256 OKX REST auth) and `x402ResourceServer`
`@okxweb3/x402-evm`	`ExactEvmScheme` — the EVM `exact` scheme server implementation

The OKX facilitator verifies each authorization and settles it on X Layer; Lineage keeps ownership of parsing, the rule engine, report signing, and anchoring. Each immutable per-tool price reaches the SDK as an explicit USD₮0 atomic asset amount rather than a USD string, so neither the fee nor its token can be substituted by currency conversion.

When the facilitator's own confirmation wait elapses it answers timeout even though the transaction it broadcast can still confirm moments later, so Lineage resolves that state through the facilitator's settlement-status lookup rather than discarding a paid call. Success is only ever reported when the facilitator confirms it.

Integration guide: OKX Onchain OS — integrate via SDK.

Proven on-chain

Live paid calls against the deployed endpoint completed the full x402 v2 round trip through the official OKX facilitator:

Tool	Amount	Settlement tx	Result
`verify_package_claim`	`0.005 USDT0` (`5000` atomic)	`0xfd9a7480…c2ea2af` · success	live registry answer: exists, age, maintainers, deprecation, provenance
`scan_dependencies`	`0.02 USDT0` (`20000` atomic)	`0xcf5360d5…b23423` · success	score `60`, verdict `REVIEW`, `TYPOSQUAT_DISTANCE` caught `expresss`

Flow for both: unpaid call → HTTP 402 + PAYMENT-REQUIRED → EIP-3009 signature → PAYMENT-SIGNATURE retry → HTTP 200 + PAYMENT-RESPONSE (status: settled). Both receipts are status 0x1 on X Layer. Free tools stay ungated and answer 200 without any payment header.

Architecture

flowchart TB
    agent["<b>AI agent</b><br/>MCP client"]
    request{"Tool call<br/>free or paid?"}
    agent -->|POST /lineage/mcp| request

    free["Free preflight<br/>capabilities · validate<br/>estimate · verify · get_artifact"]
    gate["x402 v2 gate<br/>EIP-3009 exact · pay per analysis"]
    xlayer[("X Layer<br/>USD₮0 · eip155:196")]
    request -->|free helper| free
    request -->|paid analysis| gate
    gate -. verify and settle .-> xlayer

    subgraph lineage["EVIDIQ Lineage trust boundary"]
        direction TB
        parse["1. Manifest parser<br/>npm & PyPI lockfiles"]
        engine["2. 14-Rule engine<br/>typosquat · IOCs · OSV · licenses"]
        bom["3. BOM Generator<br/>CycloneDX 1.6 · SPDX 3.0 · AI-BOM"]
        report["4. Canonical report<br/>SHA-256 digest · EIP-191 signature"]
        artifacts["5. Content-addressed artifacts<br/>report · SBOM · AI-BOM"]
        parse --> engine --> bom --> report --> artifacts
    end

    free --> parse
    gate --> parse

    response["<b>MCP response</b><br/>result + report + artifacts"]
    artifacts --> response

    classDef client fill:#312e81,stroke:#a78bfa,color:#ffffff,stroke-width:2px;
    classDef payment fill:#052e16,stroke:#4ade80,color:#ffffff,stroke-width:2px;
    classDef core fill:#0f172a,stroke:#38bdf8,color:#ffffff,stroke-width:2px;
    classDef output fill:#4c1d95,stroke:#c4b5fd,color:#ffffff,stroke-width:2px;
    class agent,request client;
    class free,gate,xlayer payment;
    class parse,engine,bom,report,artifacts core;
    class response output;
    style lineage fill:#0f172a,stroke:#38bdf8,color:#e0f2fe,stroke-width:2px;

Security boundaries

Lineage parses supplied code manifests and lockfiles; it never executes arbitrary caller code.
Every scan runs deterministically against bundled IOC datasets and live OSV.dev advisories.
Reports are canonicalized before hashing so integrity checks are reproducible across platforms.
EIP-191 signatures prove authenticity and non-repudiation of the attester key.

Self-host

Requirements: Node.js 22+ and npm.

npm install
npm run build
npm start

Or run the container:

docker build -t evidiq-lineage .
docker run -d --name evidiq-lineage -p 3000:3000 --env-file .env evidiq-lineage

Local routes: POST /mcp · GET /skill.md · GET /x402 · GET /health

Configuration

Copy .env.example to .env and set parameters:

# Server
PORT=3000
HOSTNAME=0.0.0.0
PUBLIC_BASE_URL=https://mcp.evidiq.dev/lineage

# Official OKX Payment SDK
OKX_API_KEY=...
OKX_SECRET_KEY=...
OKX_PASSPHRASE=...
OKX_BASE_URL=https://web3.okx.com

# x402 v2 — X Layer mainnet / USDT0
X402_CHAIN=eip155:196
X402_ASSET=0x779ded0c9e1022225f8e0630b35a9b54be713736
X402_PAY_TO=0x2a8efe3093278bb4bd3b2d9c7b5ba992ca4fc9b0
X402_DOMAIN_NAME=USD₮0
X402_DOMAIN_VERSION=1
X402_RPC=https://rpc.xlayer.tech

Development

npm install      # install dependencies
npm run build    # compile TypeScript to dist/
npm test         # run the 24-test suite
npm run dev      # start local watch server