ai.probitylabs/wallet-reputation

MCPcommunitylive
v1.0.3ai.probitylabsUnknownUpdated 5d ago

Pre-transaction risk screening for Ethereum addresses: signed score, sanctions, audit trail.

Endpoint healthlive
checked 2 days ago · 1292ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5d agoLast update
Package
Authorai.probitylabs
LicenseUnknown
Version1.0.3
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: this listing has no repository on file, so `forge publish` cannot verify ownership automatically. Use "Claim this listing" above — Forge reviews these by hand.
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface7 tools · none privileged
Security scan✓ Cleanvlive · 13d agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

7 tools · none privileged
Observed live from the vendor's endpoint13d ago

Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.

  • https://mcp.probitylabs.ai/mcp7 tools · 1062ms
screen_addressScreen 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…

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…

ParameterTypeDescription
address*stringEthereum 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 error…
get_screening_narrativeRetrieve 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.

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.

ParameterTypeDescription
screeningId*stringThe 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.
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 flag, and the top evidence signals. Use it to recall context for an already-screened address. Costs zero credits, unlik…

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, unlik…

ParameterTypeDescription
address*stringEthereum address (0x...) or .eth ENS name to look up historic screenings for
limitintegerNumber of past runs to return (1-50, default 5, newest first)
compare_screening_runsCompare 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…

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…

ParameterTypeDescription
runIdA*stringFirst screeningId (rsr_...). Must be a completed screen you own.
runIdB*stringSecond screeningId (rsr_...). Must be a completed screen you own.
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 flag, and the top evidence signals. Returns up to `limit` runs (default 20), so raise `limit` to reach older runs. Costs z…

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 z…

ParameterTypeDescription
limitintegerNumber of results (1-100, default 20)
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 band transition. Also returns a deterministic digest that rolls up the window into one sentence. Page forward by passing…

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…

ParameterTypeDescription
sincestringISO-8601 lower bound. Only events at or after this time are returned.
untilstringISO-8601 upper bound. Only events at or before this time are returned.
cursorstringPass the nextCursor from a prior call to page forward.
addressstringRestrict to one monitored address (0x...). Omit for the whole portfolio.
limitintegerNumber of events (1-100, default 20)
get_credit_balanceReturns 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.

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.

No input schema was published for this tool.

7 of 7 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Pre-transaction risk screening for Ethereum addresses: signed score, sanctions, audit trail.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.

Topics

Related in crypto & web3