provenance-mcp
Checks wash-traffic risk of Algorand x402 endpoints using on-chain analysis, helping agents decide whether to pay USDC.
README
provenance-mcp
Check the wash-traffic risk of Algorand x402 endpoints before your agent pays them.
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_URLto 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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.