Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
Probity Wallet Reputation is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Pre-transaction risk screening for Ethereum addresses: signed score, sanctions, audit trail.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http probity-wallet-reputation-mcp https://mcp.probitylabs.ai/mcp
# 2 — ask your agent for something these tools do
# screen_address, get_screening_narrative, get_address_screening_history and 4 more
Probity Wallet Reputation costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PRAll 1 server
probitylabs1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http probity-wallet-reputation-mcp https://mcp.probitylabs.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 sanct
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 nee |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
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_screen
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Ethereum address (0x...) or .eth ENS name to look up historic screenings for |
| limit | integer | no | Number of past runs to return (1-50, default 5, newest first) |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Number of results (1-100, default 20) |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | ISO-8601 lower bound. Only events at or after this time are returned. |
| until | string | no | ISO-8601 upper bound. Only events at or before this time are returned. |
| cursor | string | no | Pass the nextCursor from a prior call to page forward. |
| address | string | no | Restrict to one monitored address (0x...). Omit for the whole portfolio. |
| limit | integer | no | Number of events (1-100, default 20) |
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 parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Probity Wallet Reputation or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.3.
1.0.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Probity Wallet Reputation can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.