Probity Wallet Reputation
v1.0.4Pre-transaction risk screening for Ethereum addresses: signed score, sanctions, audit trail.
Endpoint health
online- Last checked
- 11/20/2026, 10:17:46 AM
- Latency
- 261 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:ai.probitylabs%2Fwallet-reputation
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"ai.probitylabs/wallet-reputation": {
"url": "https://mcp.probitylabs.ai/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
7 shown · authentication unknown
Compare screening runs
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.
Schema valid · SHA-256 98ce350423ae…
View input schema
{ "type": "object", "properties": { "runIdA": { "type": "string", "description": "First screeningId (rsr_...). Must be a completed screen you own." }, "runIdB": { "type": "string", "description": "Second screeningId (rsr_...). Must be a completed screen you own." } }, "required": [ "runIdA", "runIdB" ], "$schema": "http://json-schema.org/draft-07/schema#" }Get address screening history
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.
Schema valid · SHA-256 9b6789014654…
View input schema
{ "type": "object", "properties": { "address": { "type": "string", "description": "Ethereum address (0x...) or .eth ENS name to look up historic screenings for" }, "limit": { "description": "Number of past runs to return (1-50, default 5, newest first)", "type": "integer", "minimum": 1, "maximum": 50 } }, "required": [ "address" ], "$schema": "http://json-schema.org/draft-07/schema#" }
Connections
streamable-http
https://mcp.probitylabs.ai/mcp