presign-guard
REMOTE · PRESIGN-GUARD.ONRENDER.COM · SCANNED SEP 25
Pre-sign and token checks for agents: green/orange/red for EVM signatures and Solana/EVM tokens.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1097 tokens (~219/item across 5 items; 5 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the presign-guard MCP server?
presign-guard is a hosted endpoint at https://presign-guard.onrender.com/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 · presign-guard.onrender.com
claude mcp add --transport http fizzl13-presign-guard 'https://presign-guard.onrender.com/mcp'
{
"mcpServers": {
"fizzl13-presign-guard": {
"url": "https://presign-guard.onrender.com/mcp"
}
}
} {
"servers": {
"fizzl13-presign-guard": {
"type": "http",
"url": "https://presign-guard.onrender.com/mcp"
}
}
} [mcp_servers.fizzl13-presign-guard] url = "https://presign-guard.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fizzl13-presign-guard": {
"type": "remote",
"url": "https://presign-guard.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add fizzl13-presign-guard --url 'https://presign-guard.onrender.com/mcp' --transport streamable-http
mcp_servers:
fizzl13-presign-guard:
url: "https://presign-guard.onrender.com/mcp" {
"McpServers": {
"fizzl13-presign-guard": {
"Transport": "http",
"Url": "https://presign-guard.onrender.com/mcp"
}
}
} assistant mcp add fizzl13-presign-guard -t streamable-http -u 'https://presign-guard.onrender.com/mcp'
{
"mcpServers": {
"fizzl13-presign-guard": {
"type": "http",
"url": "https://presign-guard.onrender.com/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 63
First indexed and scored.
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 25 Sept 2026 · Probed https://presign-guard.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of presign-guard.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://presign-guard.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://presign-guard.onrender.com/mcp | HTTPS enforced | 301 | https://presign-guard.onrender.com/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 →
presign_check Pre-sign risk check ($0.01 via x402) ~302
Paid ($0.01 USDC via x402 on Base): 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 or unverified, unlimited allowances, and the token itself (honeypot, fake look-alike, high tax). Only proceed on green; on orange ask your user; never sign on red. Same as POST /v1/check.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | approval: amount in base units (0 = revoke) |
| chainId | integer | yes | EVM chain id: 1, 10, 56, 137, 8453, 42161 (8453 = Base) |
| data | string | – | transaction: 0x-prefixed calldata |
| spender | string | – | approval: who gets the allowance |
| to | string | – | transaction: the target contract |
| token | string | – | approval: the token contract |
| type | string | yes | What the agent is about to sign |
| typedData | – | – | signature: the exact eth_signTypedData_v4 payload (Permit, Permit2, EIP-3009 x402 payment, Seaport) |
| value | string | – | transaction: native value in wei |
No output schema declared.
No examples provided.
presign_check_explain Pre-sign risk check with explanation ($0.03 via x402) ~249
Paid ($0.03 USDC via x402 on Base): 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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | approval: amount in base units (0 = revoke) |
| chainId | integer | yes | EVM chain id: 1, 10, 56, 137, 8453, 42161 (8453 = Base) |
| data | string | – | transaction: 0x-prefixed calldata |
| lang | string | – | Language of the explanation (default en) |
| spender | string | – | approval: who gets the allowance |
| to | string | – | transaction: the target contract |
| token | string | – | approval: the token contract |
| type | string | yes | What the agent is about to sign |
| typedData | – | – | signature: the exact eth_signTypedData_v4 payload (Permit, Permit2, EIP-3009 x402 payment, Seaport) |
| value | string | – | transaction: native value in wei |
No output schema declared.
No examples provided.
presign_quick_check Quick pre-sign verdict (free) ~245
Free: the green/orange/red verdict only, for a transaction, token approval or EIP-712 signature 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).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | approval: amount in base units (0 = revoke) |
| chainId | integer | yes | EVM chain id: 1, 10, 56, 137, 8453, 42161 (8453 = Base) |
| data | string | – | transaction: 0x-prefixed calldata |
| spender | string | – | approval: who gets the allowance |
| to | string | – | transaction: the target contract |
| token | string | – | approval: the token contract |
| type | string | yes | What the agent is about to sign |
| typedData | – | – | signature: the exact eth_signTypedData_v4 payload (Permit, Permit2, EIP-3009 x402 payment, Seaport) |
| value | string | – | transaction: native value in wei |
No output schema declared.
No examples provided.
token_quick_verdict Quick token verdict (free) ~113
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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana mint address (base58) or EVM token contract (0x...) |
| chain | string | yes | Chain the token lives on |
No output schema declared.
No examples provided.
token_verdict Token verdict ($0.01 via x402) ~188
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) and the token address or mint; get back green/orange/red, a grade (SAFE, CAUTION, RISKY, AVOID), reason codes (mint or freeze authority still active, honeypot, tax or transfer fee, LP not locked, low liquidity, new token, concentrated holders, rugged), a one-line summary, and market data (price, liquidity, market cap, 24h volume, age). Same as GET /v1/token.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana mint address (base58) or EVM token contract (0x...) |
| chain | string | yes | Chain the token lives on |
No output schema declared.
No examples provided.
What is the presign-guard MCP server?
presign-guard is an MCP server listed in the public MCP registry as io.github.Fizzl13/presign-guard. Pre-sign and token checks for agents: green/orange/red for EVM signatures and Solana/EVM tokens. This page covers its hosted endpoint (https://presign-guard.onrender.com/mcp).
Is the presign-guard MCP server safe to use?
presign-guard scores 63 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 presign-guard MCP server expose?
presign-guard exposes 5 tools: presign_quick_check, token_quick_verdict, presign_check, presign_check_explain, token_verdict. Their descriptions and schemas cost roughly 1,097 tokens of context every time the server is loaded.
Does the presign-guard MCP server require authentication?
No. We connected to presign-guard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the presign-guard MCP server still maintained?
presign-guard is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.