Probity Wallet Reputation

Get address screening history

get_address_screening_history

Read-only

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Number of past runs to return (1-50, default 5, newest first)
`address`	Yes	Ethereum address (0x...) or .eth ENS name to look up historic screenings for

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes	Recent screening runs, newest first, each with the same detail as screen_address

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "items": {
+      "description": "Recent screening runs, newest first, each with the same detail as screen_address",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "address": {
+            "description": "The screened address",
+            "type": "string"
+          },
+          "band": {
+            "description": "Reputation band, e.g. Low Risk",
+            "type": "string"
+          },
+          "bandCode": {
+            "description": "Band identifier, e.g. LOW_RISK",
+            "type": "string"
+          },
+          "confidence": {
+            "anyOf": [
+              {
+                "enum": [
+                  "High",
+                  "Medium",
+                  "Low"
+                ],
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Engine confidence for this run"
+          },
+          "ensName": {
+            "description": "ENS name for the address, when known",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "evidence": {
+            "description": "Up to 10 signals behind this run, most severe first",
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "code": {
+                  "type": "string"
+                },
+                "factor": {
+                  "type": "string"
+                },
+                "message": {
+                  "type": "string"
+                },
+                "severity": {
+                  "enum": [
+                    "High",
+                    "Medium",
+                    "Low"
+                  ],
+                  "type": "string"
+                }
+              },
+              "required": [
+                "code",
+                "factor",
+                "severity",
+                "message"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "reportUrl": {
+            "description": "Link to the full report on the Probity dashboard",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sanctioned": {
+            "description": "True if the address is a direct OFAC match",
+            "type": "boolean"
+          },
+          "score": {
+            "description": "Signed reputation score from -100 to +100. Lower is worse.",
+            "type": "number"
+          },
+          "screenedAt": {
+            "description": "When the screen ran (ISO-8601)",
+            "type": "string"
+          },
+          "screeningId": {
+            "description": "Immutable run id (rsr_...)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "transactionCount": {
+            "description": "Number of transactions analysed",
+            "type": "integer"
+          }
+        },
+        "required": [
+          "screeningId",
+          "address",
+          "ensName",
+          "score",
+          "bandCode",
+          "band",
+          "confidence",
+          "sanctioned",
+          "transactionCount",
+          "evidence",
+          "screenedAt",
+          "reportUrl"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

First observedAug 4, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With annotations already indicating readOnlyHint=true and openWorldHint=false, the description adds meaningful behavioral context: the cost implication ('Costs zero credits'), the relationship to screen_address (fresh vs. historical), and the specific output fields ('reputation score, band, confidence, sanctioned flag, and top evidence signals'). This goes beyond the annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, each packed with distinct value: purpose/scope, use case, and key differentiator with alternatives. It is front-loaded with the essential action and avoids redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a relatively simple read-only tool with full schema coverage and an output schema present, the description provides complete context: what it returns, how it compares to a sibling, and when to use it. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides full coverage for both parameters (address and limit) with detailed descriptions, including format and constraints. The description does not add parameter-specific semantics beyond what the schema offers, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb-resource pair: 'Retrieve the authenticated user's prior screening runs for a specific Ethereum address.' It explicitly distinguishes from siblings by naming get_screening_history for all addresses and screen_address for fresh runs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance: 'Use it to recall context for an already-screened address.' It also gives an exclusion criterion: 'Costs zero credits, unlike screen_address which always runs a fresh screen,' and points to the alternative get_screening_history for broader queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Probity Wallet Reputation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?