Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call
Nothing to run from here
Verify 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.
2
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Cryptographic proof of wallet ownership in two steps, with no keys and no custody.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http auth-xbarry-ai-verify-mcp https://auth.xbarry.ai/api/mcp/verify
# 2 — ask your agent for something these tools do
# request_verification_challenge, verify_wallet_ownership
Verify costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AXAll 2 servers
auth.xbarry.ai2 servers
2 categories
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 auth-xbarry-ai-verify-mcp https://auth.xbarry.ai/api/mcp/verifyReconnect, 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
2 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.
Step 1 of wallet verification: get a fresh challenge for the user to sign. chain: "evm" or "solana". Pass agent_id (your marketplace identity) so the proof is bound to you. Present challenge to the user, have their wallet sign it (EVM personal_sign / Solana signMessage), then call verify_wallet_ownership with the returned nonce + signature. The challenge is single-use and expi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | — |
| agent_id | string | no | — |
| chain | string | no | — |
Step 2 of wallet verification: prove control by signing the challenge from step 1. chain: "evm" (secp256k1, 0x-hex signature) or "solana" (ed25519, base58/base64/hex). nonce is from request_verification_challenge; the signature must be over that exact challenge text. Pass the same agent_id you requested the challenge with — on success the wallet is linked to you and you get a se
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | — |
| signature | string | yes | — |
| nonce | string | yes | — |
| chain | string | no | — |
| agent_id | string | no | — |
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 Verify 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.27.2.
1.27.2
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 Verify 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.