Probity Wallet Reputation
REMOTE · MCP.PROBITYLABS.AI · SCANNED SEP 27
Pre-transaction risk screening for Ethereum addresses: signed score, sanctions, audit trail.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 961 tokens (~137/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (86% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Probity Wallet Reputation MCP server?
Probity Wallet Reputation is a hosted endpoint at https://mcp.probitylabs.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.probitylabs.ai
claude mcp add --transport http ai-probitylabs-wallet-reputation 'https://mcp.probitylabs.ai/mcp'
{
"mcpServers": {
"ai-probitylabs-wallet-reputation": {
"url": "https://mcp.probitylabs.ai/mcp"
}
}
} {
"servers": {
"ai-probitylabs-wallet-reputation": {
"type": "http",
"url": "https://mcp.probitylabs.ai/mcp"
}
}
} [mcp_servers.ai-probitylabs-wallet-reputation] url = "https://mcp.probitylabs.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-probitylabs-wallet-reputation": {
"type": "remote",
"url": "https://mcp.probitylabs.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-probitylabs-wallet-reputation --url 'https://mcp.probitylabs.ai/mcp' --transport streamable-http
mcp_servers:
ai-probitylabs-wallet-reputation:
url: "https://mcp.probitylabs.ai/mcp" {
"McpServers": {
"ai-probitylabs-wallet-reputation": {
"Transport": "http",
"Url": "https://mcp.probitylabs.ai/mcp"
}
}
} assistant mcp add ai-probitylabs-wallet-reputation -t streamable-http -u 'https://mcp.probitylabs.ai/mcp'
{
"mcpServers": {
"ai-probitylabs-wallet-reputation": {
"type": "http",
"url": "https://mcp.probitylabs.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Sept 26 0
- Stability: 0.97 → pass security
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 0
- Tool “get_screening_history” rewrote its description, which is the text the model reads security
- Schema quality: 773 → 961 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “get_monitoring_events” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Aug 26 0
- Tool “get_address_screening_history” rewrote its description, which is the text the model reads security
- Tool “get_credit_balance” rewrote its description, which is the text the model reads security
- Tool “get_screening_history” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 50% → 83% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Tool “get_address_screening_history” now declares an output schema ▲ functional
- Tool “get_screening_history” now declares an output schema ▲ functional
- “compare_screening_runs” reworded the description of “runIdA” cosmetic
- “compare_screening_runs” reworded the description of “runIdB” cosmetic
- “get_screening_narrative” reworded the description of “screeningId” cosmetic
- “screen_address” reworded the description of “address” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://mcp.probitylabs.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.probitylabs.ai | CN=YR2,O=Let's Encrypt,C=US | 14 Aug 2026 | 12 Nov 2026 | RSA 2048 | SHA256-RSA | 61c328c4dbaba52d0ea7b103b738e7bcf56 |
| SANs: mcp.probitylabs.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.probitylabs.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| probitylabs.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="probity", resource_metadata="https://mcp.probitylabs.ai/.well-known/oauth-protected-resource"
Bearer realm="probity", resource_metadata="https://mcp.probitylabs.ai/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Document | https://mcp.probitylabs.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.probitylabs.ai/mcp |
| Authorisation server | https://mcp.probitylabs.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.probitylabs.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.probitylabs.ai/mcp | HTTPS enforced | 308 | https://mcp.probitylabs.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_screening_runs Compare screening runs ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| runIdA | string | yes | First screeningId (rsr_...). Must be a completed screen you own. |
| runIdB | string | yes | Second screeningId (rsr_...). Must be a completed screen you own. |
| Name | Type | Req | Description |
|---|---|---|---|
| compositionDiff | array | yes | Which score drivers differ between the runs |
| mode | string | yes | temporal_delta when both runs are the same address, else side_by_side |
| reasonDiff | object | yes | What changed between the two runs at the reason level |
| runA | object | yes | – |
| runB | – | yes | – |
| scoreDelta | number | yes | runA score minus runB score |
No examples provided.
get_address_screening_history Get address screening history ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address (0x...) or .eth ENS name to look up historic screenings for |
| limit | integer | – | Number of past runs to return (1-50, default 5, newest first) |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Recent screening runs, newest first, each with the same detail as screen_address |
No examples provided.
get_credit_balance Get credit balance ~64
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_monitoring_events Get monitoring events ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Restrict to one monitored address (0x...). Omit for the whole portfolio. |
| cursor | string | – | Pass the nextCursor from a prior call to page forward. |
| limit | integer | – | Number of events (1-100, default 20) |
| since | string | – | ISO-8601 lower bound. Only events at or after this time are returned. |
| until | string | – | ISO-8601 upper bound. Only events at or before this time are returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| digest | string | yes | Deterministic rollup of the events in this window |
| events | array | yes | Monitoring events in the window, oldest first |
| hasMore | boolean | yes | True when more events remain past this page |
| nextCursor | string|null | yes | Cursor for the next page, or null when none remain |
No examples provided.
get_screening_history Get screening history ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of results (1-100, default 20) |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Recent screening runs, newest first, each with the same detail as screen_address |
No examples provided.
get_screening_narrative Get screening narrative ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| screeningId | string | yes | The rsr_... id returned by screen_address. Must reference a completed screen; the narrative can be pending for a few seconds right after the screen returns. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The screened address |
| concerns | array | yes | Key concerns raised by the review |
| narrative | string | yes | The enhanced review text |
| reportUrl | string | yes | Link to the full report on the Probity dashboard |
| screeningId | string | yes | The screen this review belongs to |
No examples provided.
screen_address Screen address ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address (0x...) or `.eth` ENS name (e.g. vitalik.eth) to screen. ENS names resolve to their current mainnet address and must resolve or the call errors. Addresses are case-insensitive and ne… |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The screened address |
| band | string | yes | Reputation band, e.g. Low Risk, Reputable |
| bandCode | string | yes | Band identifier, e.g. LOW_RISK, REPUTABLE |
| confidence | string | yes | Engine confidence in the result |
| evidence | array | yes | Up to 10 signals behind the verdict, most severe first |
| reportUrl | string | yes | Link to the full report on the Probity dashboard |
| sanctioned | boolean | yes | True if the address is a direct OFAC match |
| score | number | yes | Signed reputation score from -100 to +100. Lower is worse. |
| screenedAt | string | yes | When the screen ran (ISO-8601) |
| screeningId | string | yes | Immutable identifier for this screen (rsr_...) |
| summary | string | yes | One line verdict headline |
| transactionCount | integer | yes | Number of transactions analysed |
No examples provided.
What is the Probity Wallet Reputation MCP server?
Probity Wallet Reputation is an MCP server listed in the public MCP registry as ai.probitylabs/wallet-reputation. Pre-transaction risk screening for Ethereum addresses: signed score, sanctions, audit trail. This page covers its hosted endpoint (https://mcp.probitylabs.ai/mcp).
Is the Probity Wallet Reputation MCP server safe to use?
Probity Wallet Reputation scores 94 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Probity Wallet Reputation MCP server expose?
Probity Wallet Reputation exposes 7 tools: screen_address, get_screening_narrative, get_address_screening_history, compare_screening_runs, get_screening_history, and 2 more. Their descriptions and schemas cost roughly 910 tokens of context every time the server is loaded.
Does the Probity Wallet Reputation MCP server require authentication?
Yes. Probity Wallet Reputation asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Probity Wallet Reputation MCP server still maintained?
Probity Wallet Reputation is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.