Security & Testing

verifyum.com

Provides tools to manage and verify Verifyum proofs, including checking proof states, verifying public proofs, and anchoring commitments.

1 endpoint3 known toolsFirst detected September 1, 2026Last detected September 6, 2026

ENDPOINT 1

https://api.verifyum.com/mcp

No auth detected

MCP server metadata

Name: verifyum-mcp-endpoint
Version: 0.1.0

Capabilities

tools

Server instructions

Hosted Verifyum MCP endpoint with three remote-safe tools. File hashing, nonce generation and private-manifest construction must happen on the caller machine. Send only a completed commitment, an idempotency key, or a public proof ID. A finalized Verifyum anchor demonstrates that a commitment to exact file bytes existed no later than the estimated Solana block time. It does not prove authorship, ownership, legal signature validity, when the file was first created, or whether statements inside the file are true.

Known tools 3

verifyum_get_proof

Read the lifecycle state of one Verifyum proof (queued, submitted, finalized or failed).

Inferred read-only

verifyum_verify_public_proof

Check a finalized proof: metadata consistency, the exact 128-byte memo, and the Ed25519 service signature against the published key registry.

Inferred read-only

verifyum_anchor_commitment

Submit one locally calculated Verifyum version 2 commitment.

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.verifyum-mcp-endpoint]
url = "https://api.verifyum.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "verifyum-mcp-endpoint": {
      "type": "http",
      "url": "https://api.verifyum.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: verifyum-mcp-endpoint
Remote MCP URL: https://api.verifyum.com/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": {
    "verifyum-mcp-endpoint": {
      "url": "https://api.verifyum.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "verifyum-mcp-endpoint": {
      "type": "http",
      "url": "https://api.verifyum.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "verifyum-mcp-endpoint",
  "transport": "streamable-http",
  "url": "https://api.verifyum.com/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.