npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

mantleproof-mcp

v0.1.1

Published

MCP server: query the MantleProof on-chain audit oracle (Mantle) from any MCP-aware agent (Claude Desktop, Cursor, etc.)

Readme

mantleproof-mcp

An MCP server that lets any MCP-aware agent (Claude Desktop, Cursor, etc.) query the MantleProof on-chain audit oracle on Mantle before touching a contract.

Every audit returned by these tools is:

  • anchored on Mantle (MantleProofRegistry.submitAudit, signed by the oracle key),
  • pinned to IPFS (full report JSON, keccak'd into the on-chain rootHash),
  • and the rootHash you get back has been independently recomputed from the IPFS payload by the server before it answers, so the answer carries proof, not just trust.

Status: getAudit is live against Mantle mainnet today. auditContract is cache-first (returns the latest anchored audit if one exists). requestAudit drives the live x402 paywall — verified end-to-end with a real-USDC paid audit on Base + Mantle mainnet (2026-05-22). It surfaces the 402 payment requirements; an x402-aware wallet completes the EIP-3009 dance.

Tools

| Tool | Status | Purpose | |---|---|---| | getAudit(address) | ✅ live | Read-only lookup against MantleProofRegistry.getAudit(address) joined with the IPFS report + keccak integrity check. Free, no signer needed. | | auditContract(address, tier) | ✅ cache hit · ⏳ paid | Return the latest cached audit; if none exists, point the agent at requestAudit. | | requestAudit(address, tier) | ✅ live x402 | Pay 0.50 USDC on Base (eip155:8453); audit anchors on Mantle (eip155:5000); both txHashes returned. Surfaces the 402 payment requirements — never fabricates a receipt; an x402-aware wallet signs the EIP-3009 authorization. |

Output shape

All three tools return the canonical JSON shape locked by the engine REST API (T7):

{
  "audited": true,
  "target": "0x1892f77e335C133Ce4a7B28555f13bA74cBB76fA",
  "chain_id": 5000,
  "anchor": {
    "root_hash": "0x6a69e7d4…ca46",
    "severity": "high",
    "severity_uint8": 3,
    "ipfs_cid": "ipfs://bafkrei…ewce",
    "ipfs_uri": "ipfs://bafkrei…ewce",
    "timestamp": 1779263294,
    "submitter": "0x9f17…638a",
    "audit_count": 1
  },
  "integrity": {
    "expected_root_hash": "0x6a69…ca46",
    "recomputed_root_hash": "0x6a69…ca46",
    "match": true
  },
  "report": { "schema": "mantleproof/audit/v1", "findings": [ … ], "hallucination_guard": { "masked_count": 0, "public_note": "Hallucination guard fired: 0 masked" }, "…" : "…" },
  "ipfs_error": null,
  "explorer": { "target": "https://mantlescan.xyz/address/0x1892…76fA" }
}

integrity.match is the credibility-loop check: the server fetched the IPFS payload, stripped the post-hash fields, recomputed keccak256(canonical(json)), and compared it to the on-chain rootHash. If they don't match, match is false and recomputed_root_hash is surfaced — never silently hidden.

Install

Claude Code (one line, zero config)

claude mcp add mantleproof -- npx -y mantleproof-mcp

That's it — the server defaults to the hosted MantleProof engine, so no API URL or key is needed. Add -s project to share it with everyone who clones a repo, or -s user to enable it across all your projects. Then /mcp in a session lists the three tools.

Claude Desktop

{
  "mcpServers": {
    "mantleproof": {
      "command": "npx",
      "args": ["-y", "mantleproof-mcp"]
    }
  }
}

Environment:

| Var | Default | Purpose | |---|---|---| | MANTLEPROOF_API_BASE | hosted engine (…up.railway.app) | Base URL of the MantleProof engine REST API (/api/audit/{address}, /api/health). Override to point at a local engine, e.g. http://localhost:8000. |

Local development

pnpm install
pnpm typecheck
pnpm build               # tsc → build/, chmod +x build/index.js
node build/index.js      # speaks MCP over stdio

# end-to-end smoke against a local engine (talks to live mainnet + IPFS):
node scripts/smoke_stdio.mjs

The smoke script spawns the built server, sends tools/list + tools/call MCP frames over stdin, and asserts:

  1. exactly 3 tools advertised (auditContract, getAudit, requestAudit);
  2. getAudit against a known audited target returns integrity.match: true;
  3. requestAudit against an unaudited target returns isError: true with an honest "T11 not deployed" message (no fabricated tx).

Publishing

This package is published manually by the maintainer:

pnpm build
npm login
npm publish --access public

CI does not publish on push — npm credentials never leave a developer machine. Bump version in package.json before publishing a new release.

Architecture

agent  ──MCP stdio──▶  mantleproof-mcp  ──HTTP──▶  engine REST API
                       (this package)              /api/audit/{address}
                                                   /api/health
                                                            │
                              ┌─────────────────────────────┼─────────────────────────────┐
                              ▼                             ▼                             ▼
                       Mantle RPC                     IPFS gateway                  (writes only via
                       getAudit(target)               GET {cid}                      oracle signer)
                              │                             │
                              └──── recompute keccak(canonical(report)) ───▶ integrity.match

The MCP server is a thin client — all chain reads, signing, and integrity verification happen in the engine. The three query surfaces — on-chain getAudit, REST /api/audit/{addr}, and this MCP server — all return the same canonical JSON. Three doorways, one source of truth.

License

MIT.