SignCheck
REMOTE · API.YOURAITOOLS.CO · 2 COMPONENTS
Pre-sign safety check for agent wallets: tx, EIP-712, EIP-7702, x402. By Crypto Money Maker
Available components
Last scanned (15 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Crypto and Web3
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 395 tokens (~395/item across 1 items; 1 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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.
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.
- 22 Oct 26 68
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 22 Oct 2026 · Probed https://api.youraitools.co/signcheck/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.youraitools.co | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 16ce85edf8b8fd540ee8bd4da64828ec |
| SANs: api.youraitools.co | ||||||
| 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 api.youraitools.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| youraitools.co. | 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://api.youraitools.co/signcheck/mcp | Verified | 200 | |
| http (plaintext) | http://api.youraitools.co/signcheck/mcp | HTTPS enforced | 301 | https://api.youraitools.co/signcheck/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 →
check_signature Is it safe to sign this? ~334
Call BEFORE your agent signs or sends anything from a wallet. Decodes a transaction, an EIP-712 typed-data request (Permit, Permit2, EIP-3009 USDC authorizations, Seaport orders), an EIP-7702 delegation or an x402 payment (402 terms + payload) into plain English and returns SAFE / CAUTION / DANGER with risk flags (unlimited approvals, setApprovalForAll, fake USDC domains, x402 overpay or wrong payTo, OFAC SDN counterparties). Free preview tier (offline). The paid x402 endpoint /v1/check adds reasons, on-chain facts (spender is a wallet or contract, token metadata) and an eth_call simulation.
| Name | Type | Req | Description |
|---|---|---|---|
| authorization | object | – | EIP-7702 authorization {address (delegate contract), chainId, nonce} |
| chain | string | – | base (default), ethereum, base-sepolia or a chain id |
| payment_payload | object|string | – | x402 payment you are about to send: PAYMENT-SIGNATURE / X-PAYMENT (base64) or JSON |
| payment_required | object|string | – | x402 402 terms: the PAYMENT-REQUIRED header (base64) or JSON {accepts:[…]} |
| tx | object | – | Transaction to send: {"to":"0x…","data":"0x…","value":"0","from":"0x…"} (from enables simulation) |
| typed_data | object | – | EIP-712 request {domain, types, primaryType, message} as passed to eth_signTypedData_v4 |
No output schema declared.
No examples provided.
How do I install the SignCheck MCP server?
SignCheck is a hosted endpoint at https://api.youraitools.co/signcheck/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 · api.youraitools.co
claude mcp add --transport http co-youraitools-signcheck 'https://api.youraitools.co/signcheck/mcp'
What is the SignCheck MCP server?
SignCheck is an MCP server listed in the public MCP registry as co.youraitools/signcheck. Pre-sign safety check for agent wallets: tx, EIP-712, EIP-7702, x402. By Crypto Money Maker. This page covers its hosted endpoint (https://api.youraitools.co/signcheck/mcp).
Is the SignCheck MCP server safe to use?
SignCheck scores 68 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 SignCheck MCP server expose?
SignCheck exposes 1 tool: check_signature. Their descriptions and schemas cost roughly 334 tokens of context every time the server is loaded.
Does the SignCheck MCP server require authentication?
No. We connected to SignCheck without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SignCheck MCP server still maintained?
SignCheck is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.