Provenance Mcp

io.github.apeirontradePublished by GitHub account apeirontradev0.1.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that checks wash-traffic risk of Algorand x402 payee addresses so an agent can judge an endpoint before trusting or paying it.

What you can do
Check an Algorand endpoint payTo address for a free quick risk verdict: risk level, 0–100 score and on-chain red flags such as distinct payers, self-dealing payout loops, wallet ages, timing regularity and funding concentration. Retrieve service and paid-tier information about the Provenance engine. Point the server at a different Provenance deployment through an environment variable.
When to use it
Use it when an agent is about to trust or send USDC to an Algorand x402 endpoint and you want a statistical read on whether its revenue looks organic or manufactured. Useful for machine-payment workflows where claimed volume is easy to inflate.
Requirements
Runs locally over stdio, typically via npx with the npm package or the desktop bundle. Network access to the hosted Provenance API by default; the PROVENANCE_API_URL environment variable can point to another deployment. No authentication is declared. Free tier is limited to 30 checks per hour per IP.
Before you install
Scores are one operator's point-in-time estimates, not accusations; a high score means the pattern is consistent with self-dealing, not proven guilt. The free check is limited per IP, and deeper forensics are paid per call in USDC over x402, which spends money. Addresses you check are sent to the hosted Provenance service.

Installation

In SourceWeft

  1. Open Provenance Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

provenance-mcp

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

📊 The x402 Trust Index — our free public data site: dated Bazaar Wash Report snapshots (Base) + reseller-signal audits for 38 API brands.

Leaderboards for machine-payable APIs rank by claimed volume, which is easy to inflate — self-dealing loops, fresh-wallet farms, metronomic bots. Provenance reads public on-chain payments and gives your agent a statistical estimate of whether an endpoint's revenue looks organic or manufactured, so it can decide before sending USDC. This server scores Algorand payees; the public data site's report covers Base. Scores are one operator's estimates — the methodology publishes the weights, the limits, and what has not been validated yet.

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

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

Claude Desktop / any MCP client (mcpServers config):

json
{  "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:

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

MIT · Provenance — the trust layer for machine-payable endpoints.

Source: README.md at commit 88dc1c7

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts