Local MCP capabilities provider for Expo
Nothing to run from here
Presign Guard 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.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Pre-sign and token checks for agents: green/orange/red for EVM signatures and Solana/EVM tokens.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http presign-guard-mcp https://presign-guard.fizzl.eu/mcp
# 2 — ask your agent for something these tools do
# presign_quick_check, token_quick_verdict, presign_check and 5 more
Presign Guard costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FIAll 5 servers
Fizzl135 servers
3 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 presign-guard-mcp https://presign-guard.fizzl.eu/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
8 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.
Free: the green/orange/red verdict only, for a transaction, token approval, EIP-712 signature, XRP Ledger transaction (type xrpl) or Algorand transaction (type algorand) your agent is about to sign. Limited to 10 calls per hour. For the reason codes and details use presign_check ($0.01); for a plain-language explanation presign_check_explain ($0.03).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | What the agent is about to sign; message = a plain personal_sign / eth_sign message in message; solana = a Solana transaction in transaction; xrpl = an unsigned XRP Ledger transaction in tx; algorand |
| transaction | string | no | solana: the base64 wire transaction about to be signed; decoded and simulated (red SOLANA_TOKEN_ACCOUNT_TAKEOVER, SOLANA_ACCOUNT_ASSIGN; orange SOLANA_UNLIMITED_DELEGATE, SOLANA_DURABLE_NONCE, HIDDEN_ |
| transactions | array | no | algorand: an atomic group, each a base64 msgpack transaction; send the whole group so every transaction is checked |
| chainId | integer | no | EVM chain id, required for approval, transaction and signature: 1, 10, 56, 137, 8453, 42161 (8453 = Base); optional for message |
| method | string | no | message: how it is signed (default personal_sign); eth_sign is always red |
| message | string | no | message: the text or 0x-hex about to be signed; a Sign-In with Ethereum message for another site than origin is red, unreadable bytes are orange |
| network | string | no | xrpl: xrpl:0 (mainnet, default) or xrpl:1 (testnet) |
| tx | object | no | xrpl: the unsigned transaction JSON (TransactionType, Account, Destination, Amount, …) |
| token | string | no | approval: the token contract |
| spender | string | no | approval: who gets the allowance |
| amount | string | no | approval: amount in base units (0 = revoke) |
| to | string | no | transaction: the target contract |
| data | string | no | transaction: 0x-prefixed calldata |
| value | string | no | transaction: native value in wei |
| from | string | no | transaction or message, optional: your wallet address; the transaction is then simulated (what really leaves and arrives; orange HIDDEN_APPROVAL, SIMULATION_NFT_OUT, SIMULATION_FAILS) and its recipien |
| typedData | no | signature: the exact eth_signTypedData_v4 payload (Permit, Permit2, EIP-3009 x402 payment, Seaport) | |
| origin | string | no | optional: the site asking for the signature or transaction (URL or hostname); a domain under 30 days old is orange |
| intent | string | no | optional: what you are trying to do, in one sentence (e.g. "swap 10 USDC for ETH on Uniswap"); orange INTENT_MISMATCH when signing would do more or something else |
| x402 | object | no | optional, EIP-3009 payments only: the x402 payment requirements you are paying ({ accepted: { scheme, network, amount, asset, payTo, maxTimeoutSeconds, extra } }, one entry of the 402's accepts); red |
Free: the green/orange/red verdict and grade only, for a Solana or EVM token your agent is about to buy, hold or accept. Limited to 10 free calls per hour (shared with presign_quick_check). For the reasons, one-line summary and market data use token_verdict ($0.01).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | Chain the token lives on |
| address | string | yes | Solana mint address (base58), EVM token contract (0x...), XRPL token as CURRENCY.rIssuer, or Algorand asset id (e.g. 31566704) |
Paid ($0.01 USDC via x402 on Base or Solana): call this before you sign. Send the transaction, token approval or EIP-712 signature (Permit, Permit2, EIP-3009 x402 payment, Seaport) your agent is about to sign; get back green, orange or red with reason codes: who gets access, whether the spender or recipient is flagged, sanctioned (OFAC SDN) or unverified, unlimited allowances, and the token itself
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | What the agent is about to sign; message = a plain personal_sign / eth_sign message in message; solana = a Solana transaction in transaction; xrpl = an unsigned XRP Ledger transaction in tx; algorand |
| transaction | string | no | solana: the base64 wire transaction about to be signed; decoded and simulated (red SOLANA_TOKEN_ACCOUNT_TAKEOVER, SOLANA_ACCOUNT_ASSIGN; orange SOLANA_UNLIMITED_DELEGATE, SOLANA_DURABLE_NONCE, HIDDEN_ |
| transactions | array | no | algorand: an atomic group, each a base64 msgpack transaction; send the whole group so every transaction is checked |
| chainId | integer | no | EVM chain id, required for approval, transaction and signature: 1, 10, 56, 137, 8453, 42161 (8453 = Base); optional for message |
| method | string | no | message: how it is signed (default personal_sign); eth_sign is always red |
| message | string | no | message: the text or 0x-hex about to be signed; a Sign-In with Ethereum message for another site than origin is red, unreadable bytes are orange |
| network | string | no | xrpl: xrpl:0 (mainnet, default) or xrpl:1 (testnet) |
| tx | object | no | xrpl: the unsigned transaction JSON (TransactionType, Account, Destination, Amount, …) |
| token | string | no | approval: the token contract |
| spender | string | no | approval: who gets the allowance |
| amount | string | no | approval: amount in base units (0 = revoke) |
| to | string | no | transaction: the target contract |
| data | string | no | transaction: 0x-prefixed calldata |
| value | string | no | transaction: native value in wei |
| from | string | no | transaction or message, optional: your wallet address; the transaction is then simulated (what really leaves and arrives; orange HIDDEN_APPROVAL, SIMULATION_NFT_OUT, SIMULATION_FAILS) and its recipien |
| typedData | no | signature: the exact eth_signTypedData_v4 payload (Permit, Permit2, EIP-3009 x402 payment, Seaport) | |
| origin | string | no | optional: the site asking for the signature or transaction (URL or hostname); a domain under 30 days old is orange |
| intent | string | no | optional: what you are trying to do, in one sentence (e.g. "swap 10 USDC for ETH on Uniswap"); orange INTENT_MISMATCH when signing would do more or something else |
| x402 | object | no | optional, EIP-3009 payments only: the x402 payment requirements you are paying ({ accepted: { scheme, network, amount, asset, payTo, maxTimeoutSeconds, extra } }, one entry of the 402's accepts); red |
Paid ($0.03 USDC via x402 on Base or Solana): the same verdict and reason codes as presign_check, plus a 3 to 5 sentence plain-language explanation a person can read before approving (lang en or nl). Same as POST /v1/check/explain. The answer carries a signed receipt (EIP-191, bound to your arguments) that proves later which verdict you got.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | What the agent is about to sign; message = a plain personal_sign / eth_sign message in message; solana = a Solana transaction in transaction; xrpl = an unsigned XRP Ledger transaction in tx; algorand |
| transaction | string | no | solana: the base64 wire transaction about to be signed; decoded and simulated (red SOLANA_TOKEN_ACCOUNT_TAKEOVER, SOLANA_ACCOUNT_ASSIGN; orange SOLANA_UNLIMITED_DELEGATE, SOLANA_DURABLE_NONCE, HIDDEN_ |
| transactions | array | no | algorand: an atomic group, each a base64 msgpack transaction; send the whole group so every transaction is checked |
| chainId | integer | no | EVM chain id, required for approval, transaction and signature: 1, 10, 56, 137, 8453, 42161 (8453 = Base); optional for message |
| method | string | no | message: how it is signed (default personal_sign); eth_sign is always red |
| message | string | no | message: the text or 0x-hex about to be signed; a Sign-In with Ethereum message for another site than origin is red, unreadable bytes are orange |
| network | string | no | xrpl: xrpl:0 (mainnet, default) or xrpl:1 (testnet) |
| tx | object | no | xrpl: the unsigned transaction JSON (TransactionType, Account, Destination, Amount, …) |
| token | string | no | approval: the token contract |
| spender | string | no | approval: who gets the allowance |
| amount | string | no | approval: amount in base units (0 = revoke) |
| to | string | no | transaction: the target contract |
| data | string | no | transaction: 0x-prefixed calldata |
| value | string | no | transaction: native value in wei |
| from | string | no | transaction or message, optional: your wallet address; the transaction is then simulated (what really leaves and arrives; orange HIDDEN_APPROVAL, SIMULATION_NFT_OUT, SIMULATION_FAILS) and its recipien |
| typedData | no | signature: the exact eth_signTypedData_v4 payload (Permit, Permit2, EIP-3009 x402 payment, Seaport) | |
| origin | string | no | optional: the site asking for the signature or transaction (URL or hostname); a domain under 30 days old is orange |
| intent | string | no | optional: what you are trying to do, in one sentence (e.g. "swap 10 USDC for ETH on Uniswap"); orange INTENT_MISMATCH when signing would do more or something else |
| x402 | object | no | optional, EIP-3009 payments only: the x402 payment requirements you are paying ({ accepted: { scheme, network, amount, asset, payTo, maxTimeoutSeconds, extra } }, one entry of the 402's accepts); red |
| lang | string | no | Language of the explanation (default en) |
Paid ($0.01 USDC via x402 on Base or Solana): call this before your agent buys, holds or accepts a token. Send the chain (solana, base, ethereum, arbitrum, optimism, polygon, bsc, xrpl, algorand) and the token address, mint, CURRENCY.rIssuer or Algorand asset id; get back green/orange/red, a grade (SAFE, CAUTION, RISKY, AVOID), reason codes (mint or freeze authority still active, honeypot, tax or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | Chain the token lives on |
| address | string | yes | Solana mint address (base58), EVM token contract (0x...), XRPL token as CURRENCY.rIssuer, or Algorand asset id (e.g. 31566704) |
Paid ($0.02 USDC via x402 on Base or Solana): audit the open token approvals of an EVM wallet (base, ethereum, arbitrum, optimism, polygon, bsc), for example your agent's own wallet as a periodic check. Get back green/orange/red, a grade, a one-line summary and every ERC-20 allowance with its spender: flagged malicious (red), a plain wallet, on a doubt list, an unverified contract or an unlimited
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | EVM chain to audit |
| address | string | yes | Wallet address (0x...) |
Paid ($0.01 USDC via x402 on Base or Solana): call this before your agent pays an address, or before accepting money from one. Send any chain's wallet address (EVM 0x..., Solana, Tron, Bitcoin, XRP Ledger, Algorand, or another currency OFAC lists). Get back green/orange/red: red SANCTIONED_ADDRESS with the SDN entry (name, programs, currency) when the address is on the OFAC SDN list, red or orange
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | The wallet address to screen, any chain: EVM (0x...), Solana, Tron, Bitcoin, XRP Ledger, Algorand, or another currency OFAC lists |
Report a bug, a missing feature or anything else about this service, in a structured way. Free. A person reads every report; nothing is run or changed automatically.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | bug, feature (something missing) or other |
| message | string | yes | What happened or what you need |
| endpoint | string | no | Optional: the route or tool it is about, e.g. /v1/token |
| contact | string | no | Optional: how to reach you about it |
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 Presign Guard 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: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. 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.5.0.
1.5.0
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 Presign Guard 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.