Blankas
REMOTE · PVL.APP.N8N.CLOUD
Numbered, signed blank forms for agent-to-agent deals: issue, co-sign, verify and mark.
Available components
Last scanned (3 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Security63
- 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 6 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 625 tokens (~104/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- Tool “blankas_verify” rewrote its description, which is the text the model reads security
- “blankas_verify” reworded the description of “document” cosmetic
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://pvl.app.n8n.cloud/mcp/blankas-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.app.n8n.cloud | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3b38c5d507701514138d3f87eab15211 |
| SANs: *.app.n8n.cloud | ||||||
| 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 pvl.app.n8n.cloud. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cloud. | present | 7041 | 13 | Verified |
| n8n.cloud. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | sandbox allow-downloads allow-forms allow-modals allow-orientation-lock allow-pointer-lock allow-popups allow-popups-to-escape-sandbox allow-presentation allow-scripts allow-top-navigation-by-user-activation allow-top-navigation-to-custom-protocols |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pvl.app.n8n.cloud/mcp/blankas-mcp | Verified | 200 | |
| http (plaintext) | http://pvl.app.n8n.cloud/mcp/blankas-mcp | HTTPS enforced | 301 | https://pvl.app.n8n.cloud/mcp/blankas-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 →
blankas_info ~47
Status of Blankas, a free service for verifiable agreements between AI agents: issuer public key, free blanks left, links to the spec and to the local signer. Call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
blankas_issue ~129
Start a verifiable agreement between two AI agents: issues a numbered, issuer-signed blank form for a deal, contract, order or service terms. Both parties then sign the same terms with their own keys, so each holds proof of agreement. Uses one free blank. Never send private keys.
| Name | Type | Req | Description |
|---|---|---|---|
| party_a | – | yes | Public keys of party A: object with sign (Ed25519) and box (X25519), each 32 raw bytes as base64url without padding |
| party_b | – | yes | Public keys of party B in the same format as party_a, different from party A |
No output schema declared.
No examples provided.
blankas_mark ~92
Timestamp proof that both AI agents signed an agreement: registers only the deal hash, never the terms. Kept 72 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| blank | – | yes | The issued blank object exactly as returned by blankas_issue |
| deal_hash | string | yes | Deal hash: 64-character lowercase hex SHA-256 |
| signatures | – | yes | Object with Ed25519 signatures a and b over the deal hash, base64url |
No output schema declared.
No examples provided.
blankas_marks ~49
Look up timestamped proofs (marks) of an agreement between AI agents by blank ID.
| Name | Type | Req | Description |
|---|---|---|---|
| blank_id | string | yes | Blank ID, for example BLK-000001-7afb11 |
No output schema declared.
No examples provided.
blankas_spec ~46
How to make a verifiable, co-signed agreement (contract) between two AI agents with Blankas: form fields, canonical JSON, deal hash and Ed25519 signing rules.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
blankas_verify ~102
Verify a co-signed agreement between AI agents. The document parameter must be the complete JSON object {blank, content, deal_hash, signatures}, not text. Checks the issuer signature, the terms and both party signatures; use it as proof of agreement or dispute evidence. Free. To look up timestamped marks by blank ID, use blankas_marks instead.
| Name | Type | Req | Description |
|---|---|---|---|
| document | – | yes | The complete JSON object {blank, content, deal_hash, signatures}, not text |
No output schema declared.
No examples provided.
How do I install the Blankas MCP server?
Blankas is a hosted endpoint at https://pvl.app.n8n.cloud/mcp/blankas-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 · pvl.app.n8n.cloud
claude mcp add --transport http sirsinatoriai-png-blankas 'https://pvl.app.n8n.cloud/mcp/blankas-mcp'
What is the Blankas MCP server?
Blankas is an MCP server listed in the public MCP registry as io.github.sirsinatoriai-png/blankas. Numbered, signed blank forms for agent-to-agent deals: issue, co-sign, verify and mark. This page covers its hosted endpoint (https://pvl.app.n8n.cloud/mcp/blankas-mcp).
Is the Blankas MCP server safe to use?
Blankas scores 74 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 Blankas MCP server expose?
Blankas exposes 6 tools: blankas_marks, blankas_mark, blankas_verify, blankas_issue, blankas_spec, blankas_info. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.
Does the Blankas MCP server require authentication?
No. We connected to Blankas without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Blankas MCP server still maintained?
Blankas is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.