PlainText Wallet Approval Checker
REMOTE · PLAINTEXT.FIZZL.EU
Explains wallet approvals and signature requests in plain language: SAFE, CAUTION or RISK.
Available components
Last scanned (23 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 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 Security46
- 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 connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 & Reachability0
- Transport check failed: the endpoint responded but didn't complete an MCP handshake over streamable-http. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 15 Nov 26 −63
- Endpoint reachability: unreachable → not serving MCP ▼ security
- HSTS header: unverified → fail ▼ security
- HTTPS: unverified → fail ▼ security
- TLS certificate: unverified → pass ▲ security
- Transport: Transport check failed: the endpoint responded but didn't complete an MCP handshake over streamable-http. security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 14 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 +63
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 15 Oct 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.53 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 14 Oct 26 0
- HSTS header: fail → pass ▲ security
- 9 Oct 26 0
- Tool “check_wallet_approvals” now declares an output schema ▲ functional
- Tool “explain_approval” now declares an output schema ▲ functional
- Tool “feedback” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- 2 Oct 26 0
- Tool “check_wallet_approvals” rewrote its description, which is the text the model reads security
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 21 Nov 2026 · Probed https://plaintext.fizzl.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fizzl.eu | CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB | 10 Sept 2026 | 9 Mar 2027 | RSA 2048 | SHA256-RSA | 8a684bb5e8357e70b6de0eb25866c405 |
| SANs: *.fizzl.eu, fizzl.eu | ||||||
| CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 397a66cc2756362e0daa87ca6eabe3b1 |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
| CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US (CA) | CN=AAA Certificate Services,O=Comodo CA Limited,L=Salford,ST=Greater Manchester,C=GB | 12 Mar 2019 | 31 Dec 2028 | RSA 4096 | SHA384-RSA | 3972443af922b751d7d36c10dd313595 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of plaintext.fizzl.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | DS published | 35926 | 8 | Verified |
| fizzl.eu. | No DS | 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://plaintext.fizzl.eu/mcp | Not MCP | 200 | |
| http (plaintext) | http://plaintext.fizzl.eu/mcp | Served over HTTP | 200 |
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_wallet_approvals Check Wallet Approvals ~115
Check an EVM wallet's live token/NFT approvals and get a plain-language safety verdict (SAFE, CAUTION, or RISK) with an explanation. The verdict comes from presign-guard's approval audit (who each spender is, which to revoke).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM wallet address to check, e.g. 0x... |
| chain | string | – | Chain to check approvals on (default: ethereum) |
| kind | string | – | Approval type to check (default: token) |
| Name | Type | Req | Description |
|---|---|---|---|
| explanation | string | yes | Plain-language explanation of what the approval or payload allows |
| verdict | string | yes | SAFE, CAUTION or RISK |
No examples provided.
explain_approval Explain Approval Payload ~51
Explain an arbitrary approval/permission JSON payload in plain language, when you already have the data instead of needing an on-chain lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Arbitrary approval/permission JSON payload to explain |
| Name | Type | Req | Description |
|---|---|---|---|
| explanation | string | yes | Plain-language explanation of what the approval or payload allows |
| verdict | string | yes | SAFE, CAUTION or RISK |
No examples provided.
feedback Send feedback (free) ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | Optional: how to reach you about it |
| endpoint | string | – | Optional: the route or tool it is about, e.g. /v1/token |
| message | string | yes | What happened or what you need |
| type | string | – | bug, feature (something missing) or other |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Report id, to refer to it later |
| note | string | – | – |
| received | boolean | yes | true: a person will read it |
| service | string | – | – |
| type | string | – | – |
No examples provided.
How do I install the PlainText Wallet Approval Checker MCP server?
PlainText Wallet Approval Checker is a hosted endpoint at https://plaintext.fizzl.eu/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 · plaintext.fizzl.eu
claude mcp add --transport http fizzl13-plaintext-wallet-checker 'https://plaintext.fizzl.eu/mcp'
What is the PlainText Wallet Approval Checker MCP server?
PlainText Wallet Approval Checker is an MCP server listed in the public MCP registry as io.github.Fizzl13/plaintext-wallet-checker. Explains wallet approvals and signature requests in plain language: SAFE, CAUTION or RISK. This page covers its hosted endpoint (https://plaintext.fizzl.eu/mcp).
Is the PlainText Wallet Approval Checker MCP server safe to use?
PlainText Wallet Approval Checker scores 18 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 PlainText Wallet Approval Checker MCP server expose?
PlainText Wallet Approval Checker exposes 3 tools: check_wallet_approvals, explain_approval, feedback. Their descriptions and schemas cost roughly 275 tokens of context every time the server is loaded.
Does the PlainText Wallet Approval Checker MCP server require authentication?
No. We connected to PlainText Wallet Approval Checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PlainText Wallet Approval Checker MCP server still maintained?
PlainText Wallet Approval Checker is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the PlainText Wallet Approval Checker MCP server?
VerifyMCP ran 5 checks on PlainText Wallet Approval Checker, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about PlainText Wallet Approval Checker: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.