Security & Testing

n8n.cloud

Provides tools for issuing, signing, looking up, and cryptographically verifying timestamped co-signed agreements between AI agents using Ed25519 signatures and deal hashes.

1 endpoint6 known toolsFirst detected May 29, 2026Last detected October 21, 2026

ENDPOINT 1

https://pvl.app.n8n.cloud/mcp/blankas-mcp

No auth detected

MCP server metadata

Name: Blankas_MCP
Version: 0.1.0

Capabilities

tools

Server instructions

Blankas issues numbered, issuer-signed blank forms for deals between two AI agents. Flow: 1) blankas_issue with both parties public keys; 2) both parties fill the same content (form agent-deal-v1, see blankas_spec) and each signs the deal hash with its own Ed25519 key on its own side; 3) blankas_verify the completed document. Optional: blankas_mark registers a timestamped mark that contains only the hash. To sign without writing code, run the local Blankas signer MCP server, which keeps keys on the agent's own machine: uvx --from git+https://github.com/sirsinatoriai-png/Blankas blankas-mcp. Blankas never holds money and never needs private keys.

Known tools 6

blankas_marks

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

Inferred read-only

blankas_mark

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

Inferred read-only

blankas_verify

Verify a co-signed agreement between AI agents: checks the issuer signature, the terms and both party signatures.

Inferred read-only

blankas_issue

Start a verifiable agreement between two AI agents: issues a numbered, issuer-signed blank form for a deal, contract, order or service terms.

Inferred read-only

blankas_spec

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.

Inferred read-only

blankas_info

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.blankas_mcp]
url = "https://pvl.app.n8n.cloud/mcp/blankas-mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "blankas_mcp": {
      "type": "http",
      "url": "https://pvl.app.n8n.cloud/mcp/blankas-mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: blankas_mcp
Remote MCP URL: https://pvl.app.n8n.cloud/mcp/blankas-mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "blankas_mcp": {
      "url": "https://pvl.app.n8n.cloud/mcp/blankas-mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "blankas_mcp": {
      "type": "http",
      "url": "https://pvl.app.n8n.cloud/mcp/blankas-mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "blankas_mcp",
  "transport": "streamable-http",
  "url": "https://pvl.app.n8n.cloud/mcp/blankas-mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.