Back to Browse

Provenance MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

Wash-traffic risk checks for Algorand x402 endpoints before your agent trusts or pays them.

About

Wash-traffic risk checks for Algorand x402 endpoints before your agent trusts or pays them.

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (2 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.

3 files analyzed Β· 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Provenance API base URL (defaults to the hosted service)Optional

Environment variable: PROVENANCE_API_URL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-apeirontrade-provenance-mcp": {
      "env": {
        "PROVENANCE_API_URL": "your-provenance-api-url-here"
      },
      "args": [
        "-y",
        "provenance-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

provenance-mcp

Check the wash-traffic risk of Algorand x402 endpoints before your agent pays them.

πŸ“Š The x402 Trust Index β€” our free public leaderboard: weekly Bazaar Wash Report + resale-authorization audits for 38 API brands.

Roughly half of x402 "agentic payment" activity is artificial β€” self-dealing loops, fresh-wallet farms, metronomic bots. Provenance reads the chain and tells your agent whether an endpoint's revenue is organic or fabricated, so it can decide before sending USDC.

Tools

  • check_endpoint_risk(address) β€” free quick verdict for any Algorand endpoint payTo address: risk level (low/medium/high/critical), 0–100 score, and the on-chain red flags (distinct-payer count, self-dealing payout loops, wallet ages, timing regularity, funding concentration).
  • provenance_service_info() β€” service + paid-tier info.

Deep forensics are x402-paid on the same API: /score $0.05 Β· /report $0.50 (full 8-signal grade + facilitator drift) Β· /diligence $5.00.

Install

Claude Code

claude mcp add provenance -- npx -y provenance-mcp

Claude Desktop / any MCP client (mcpServers config):

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

Then ask your agent: β€œcheck the wash risk of Algorand endpoint <ADDRESS>”.

How it works

The hosted Provenance engine indexes USDC (ASA 31566704) payments on Algorand mainnet, enriches payer wallets (age, first funder, asset diversity, rekey auth-addr), clusters them (union-find over funding + shared-key links), and runs 8 wash-detection signals. Scores are point-in-time snapshots, anchored on-chain for tamper-evidence. Methodology: signals, not accusations β€” a high score means the revenue pattern is consistent with self-dealing, not that the operator is guilty of anything.

  • Env: PROVENANCE_API_URL to point at a different Provenance deployment.
  • Free tier: 30 checks/hour/IP.

Guard your x402 client directly

Building an agent that pays over x402? provenance-guard wraps any x402-paying fetch and runs this same check automatically before any money moves β€” one line, zero dependencies:

import { createGuard } from "provenance-guard";
const guarded = createGuard().guardedFetch(fetchWithPayment);

MIT Β· Provenance β€” the trust layer for machine-payable endpoints.

Reviews

No reviews yet

Be the first to review this server!