mcpbeat

Veritasacta Verify MCP Server

io.github.tomjwxf/veritasacta-verify
local only

Veritasacta Verify runs on your own machine — the client starts it, so there is no endpoint to ping. 39 installs a week from npm.

Offline receipt verifier. Ed25519 signature verification without contacting any server.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 25 · avg 10 · -57% w/w
a month agotoday
39
Installs / week
npm · @veritasacta/verify
—
Stars
on GitHub
—
Last commit
0 releases in 90 days
—
License
language unknown

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add veritasacta-verify -- npx -y @veritasacta/verify
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "veritasacta-verify": {
      "args": [
        "-y",
        "@veritasacta/verify"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.veritasacta-verify]
command = "npx"
args = ["-y", "@veritasacta/verify"]
.cursor/mcp.json
{
  "mcpServers": {
    "veritasacta-verify": {
      "args": [
        "-y",
        "@veritasacta/verify"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "veritasacta-verify": {
      "args": [
        "-y",
        "@veritasacta/verify"
      ],
      "command": "npx"
    }
  }
}

Veritasacta Verify — questions

Answers built from our own checks of this server.

Why is there no uptime for Veritasacta Verify?
Veritasacta Verify runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @veritasacta/verify was installed 39 times last week.
Is Veritasacta Verify still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Veritasacta Verify?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @veritasacta/verify straight from npm; nothing to host, nothing to sign up for.
How many people use Veritasacta Verify?
The npm package @veritasacta/verify was installed 39 times in the last week. Week over week that is -57%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.