Probity Wallet Reputation
by probitylabs.ai · remote · no sign-in to list tools · v1.0.3 · published by ai.probitylabs
Pre-transaction risk screening for Ethereum addresses: signed score, sanctions, audit trail.
7 tools: 1 change things and 6 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things1Claude Code: ask: see these tools
- Only reads6Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http wallet-reputation https://mcp.probitylabs.ai/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
7 tools
Changes things 1Claude Code: ask
screen_addressScreen an Ethereum address or `.eth` ENS name for on-chain reputation risk.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Only reads 6Claude Code: allow
compare_screening_runsCompare two completed screens by their screeningId and see what changed.No findings
Why it is in this group
- The name "compare_screening_runs" says "compare": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_address_screening_historyRetrieve 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 …No findings
Why it is in this group
- The name "get_address_screening_history" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_credit_balanceReturns the authenticated user's current credit balance as a whole number of credits.No findings
Why it is in this group
- The name "get_credit_balance" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_monitoring_eventsReturns 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 b…No findings
Why it is in this group
- The name "get_monitoring_events" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_screening_historyReturns 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 fla…No findings
Why it is in this group
- The name "get_screening_history" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_screening_narrativeRetrieve the enhanced Probity review for a completed screen by its screeningId.No findings
Why it is in this group
- The name "get_screening_narrative" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.0.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http wallet-reputation https://mcp.probitylabs.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__wallet-reputation__get_screening_narrative",
"mcp__wallet-reputation__get_address_screening_history",
"mcp__wallet-reputation__compare_screening_runs",
"mcp__wallet-reputation__get_screening_history",
"mcp__wallet-reputation__get_monitoring_events",
"mcp__wallet-reputation__get_credit_balance"
],
"ask": [
"mcp__wallet-reputation__screen_address"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as wallet-reputation. Review it before you use it.