Skip to main content
Glama
Sign In

Blankas

by io.github.sirsinatoriai-png
OverviewDiscussionsAdmin

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation4/5

Most tools target clearly distinct stages: status/info, issue, mark, lookup, spec, and verify. The main risk is blankas_mark vs blankas_marks, whose singular/plural names could be confused, though the descriptions clarify create/register versus lookup.

Naming Consistency4/5

All tools use the same blankas_ snake_case prefix and are readable. The pattern mixes nouns (info, spec, marks) and verbs (issue, verify, mark), and the singular/plural mark/marks pair is a minor inconsistency.

Tool Count5/5

Six tools are well scoped to the agreement lifecycle and each has a clear role: status, issuance, specification, verification, timestamp registration, and lookup. There is no obvious filler.

Completeness4/5

The core lifecycle is covered: status/info, issue a blank, read the spec, verify an agreement, register a timestamp proof, and look up marks. Minor gaps include no dedicated get_blank/retrieve-blank operation and signing is handled locally rather than by a tool, but the main workflow is not dead-ended.

Available Tools

6 tools
blankas_infoAInspect

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.

Inputs: no named parameters.

blankas_issueBInspect

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.

Inputs: party_a (required), party_b (required).

blankas_markAInspect

Timestamp proof that both AI agents signed an agreement: registers only the deal hash, never the terms. Kept 72 hours.

Inputs: blank (required), deal_hash (required), signatures (required).

blankas_marksBInspect

Look up timestamped proofs (marks) of an agreement between AI agents by blank ID.

Inputs: blank_id (required).

blankas_specBInspect

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.

Inputs: no named parameters.

blankas_verifyAInspect

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.

Inputs: document (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources