Probity Wallet Reputation is listed as active in the registry but did not answer our last check. It exposes 7 tools.
Pre-transaction risk screening for Ethereum addresses: signed score, sanctions, audit trail.
Uptime history
49 days of history · worst day 15%
49 days agonow
14.3%
Uptime 24h
13 of 91 checks
7
Tools
read from the server
386 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 3
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 August 2026. No other catalogue keeps this.
24 Aug
a tool appeared
get_monitoring_events
24 Aug
a tool description was rewritten
get_screening_history
24 Aug
a tool changed version
Probity Wallet Reputation does not always answer
Over the last week it answered 55.7% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.
run in your terminal
claude mcp add wallet-reputation --transport http https://mcp.probitylabs.ai/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"wallet-reputation": {
"url": "https://mcp.probitylabs.ai/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.wallet-reputation]
url = "https://mcp.probitylabs.ai/mcp".cursor/mcp.json
{
"mcpServers": {
"wallet-reputation": {
"url": "https://mcp.probitylabs.ai/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"wallet-reputation": {
"url": "https://mcp.probitylabs.ai/mcp"
}
}
}Available tools 7
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
screening
get_screening_history
Returns the authenticated user's most recent screening runs across all addresses, newest first, each with the same detail as screen_address: score, band, confidence, sanctioned flag, and the top evidence signals. Returns up to `limit` runs (default 20), so raise `limit` to reach older runs. Costs zero credits. For the history of one specific address, use get_address_screening_history instead.
get_screening_narrative
Retrieve the enhanced Probity review for a completed screen by its screeningId. Costs zero credits. Returns the narrative and the key concerns it raises. It is generated in the background after screen_address returns, so it may briefly be pending. Retry shortly if so.
address
get_address_screening_history
Retrieve the authenticated user's prior screening runs for a specific Ethereum address, each with the same detail as screen_address: reputation score, band, confidence, sanctioned flag, and the top evidence signals. Use it to recall context for an already-screened address. Costs zero credits, unlike screen_address which always runs a fresh screen. For runs across all your addresses, use get_screening_history.
compare
compare_screening_runs
Compare two completed screens by their screeningId and see what changed. Costs zero credits. Two runs of the same address show why the reputation score moved. Two different addresses show a side by side. Returns each run score, band, and confidence, a reason level diff, and the score change broken into its drivers. Small differences between runs of one address can be normal variation rather than a data change.
credit
get_credit_balance
Returns the authenticated user's current credit balance as a whole number of credits. One credit screens one address: screen_address costs 1 credit, while this call and the history, narrative, and compare tools cost zero. Check it before screen_address to confirm a screen can be afforded.
monitoring
get_monitoring_events
Returns the authenticated user's monitoring events: material reputation changes detected on their monitored addresses, oldest first, each with the change type, a summary, and the band transition. Also returns a deterministic digest that rolls up the window into one sentence. Page forward by passing the returned nextCursor as cursor. Bound the window with since and until, or restrict to one address with address. Costs zero credits.
screen
screen_address
Screen an Ethereum address or `.eth` ENS name for on-chain reputation risk. Costs 1 credit. Returns a signed reputation score (-100 to +100), a risk band, a confidence level, a sanctioned flag, the top evidence factors, a screeningId, and a link to the full report. The enhanced review is generated in the background. Fetch it with get_screening_narrative(screeningId). Use the score, band, and sanctioned flag to gate pre-trade or payout flows.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.probitylabs.ai/mcp | streamable-http | answering | 321 ms | 15 min ago |
Alternatives to Probity Wallet Reputation
same job, measured the same waytraql
by traql
AML risk scoring for crypto addresses and transactions on Ethereum, BSC, TRON, TON, Bitcoin
Pathguard
by cieltech-pathguard
Crypto transaction safety tool — screens addresses and transactions for scam risk.
Publicaml
by publicaml
AML screening for crypto addresses: risk, sanctions, fund tracing and counterparties.
Arbitrum Transaction Preflight
by naur9n
Paid Arbitrum transaction simulation and risk scoring for wallets and AI agents.
Basis Protocol
by shlok-lgtm
Stablecoin risk scores, wallet risk profiles, and transaction risk assessment.
Publicaml
by saloprj
Free crypto AML/KYT screening for BTC/ETH/BSC/TRON — risk score, sanctions, source of funds.
Ibanforge
by cammac-creator
Pre-payout IBAN screening for AI agents: validation, sanctions, Swiss clearing, risk scoring
Cyberwarex Wallet Safety
by cyberpunk11147
Pre-sign wallet safety: tx simulation, signature decoding, address risk, ABI, URL phishing.
Probity Wallet Reputation — questions
Answers built from our own checks of this server.
What can Probity Wallet Reputation do?
It exposes 7 tools, read directly from the server on our last check. Among them: compare_screening_runs, get_address_screening_history, get_credit_balance, get_monitoring_events, get_screening_history, get_screening_narrative and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Probity Wallet Reputation working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 13 of 91 checks got a reply (14.3%), average response time 386 ms. The bar chart above shows every period we have measured.
The registry lists Probity Wallet Reputation as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Probity Wallet Reputation?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Probity Wallet Reputation need an API key?
No. Probity Wallet Reputation completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Probity Wallet Reputation?
It answers our handshake in 386 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.