Skip to content

Blankas

by sirsinatoriai-png · remote · no sign-in to list tools · v0.1.0 · published by GitHub user sirsinatoriai-png

Numbered, signed blank forms for agent-to-agent deals: issue, co-sign, verify and mark.

Changes · 5
CompareRegistry entry

6 tools: 5 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http blankas https://pvl.app.n8n.cloud/mcp/blankas-mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 5Claude Code: ask
  • blankas_issueStart a verifiable agreement between two AI agents: issues a numbered, issuer-signed blank form for a deal, contract, order or service terms.No findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    Description, as the server wrote it
    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.
  • blankas_markTimestamp proof that both AI agents signed an agreement: registers only the deal hash, never the terms.No findings

    Why it is in this group

    • The name "blankas_mark" says "mark": a word for a change.
    Description, as the server wrote it
    Timestamp proof that both AI agents signed an agreement: registers only the deal hash, never the terms. Kept 72 hours.
  • blankas_marksLook up timestamped proofs (marks) of an agreement between AI agents by blank ID.No findings

    Why it is in this group

    • The name "blankas_marks" says "mark": a word for a change.
    Description, as the server wrote it
    Look up timestamped proofs (marks) of an agreement between AI agents by blank ID.
  • blankas_specHow to make a verifiable, co-signed agreement (contract) between two AI agents with Blankas: form fields, canonical JSON, deal hash and Ed25519 signing rules.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • blankas_verifyVerify a co-signed agreement between AI agents: checks the issuer signature, the terms and both party signatures.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify a co-signed agreement between AI agents: checks the issuer signature, the terms and both party signatures. Use it as proof of agreement or dispute evidence. Free; does not use a blank.
Only reads 1Claude Code: allow
  • blankas_infoStatus 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.No findings

    Why it is in this group

    • The description's first verb is "status": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http blankas https://pvl.app.n8n.cloud/mcp/blankas-mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__blankas__blankas_info"
    ],
    "ask": [
      "mcp__blankas__blankas_marks",
      "mcp__blankas__blankas_mark",
      "mcp__blankas__blankas_verify",
      "mcp__blankas__blankas_issue",
      "mcp__blankas__blankas_spec"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as blankas. Review it before you use it.