mcpbeat Sign in

Veritasacta Verify MCP Server

local only

Veritasacta Verify runs on your own machine — the client starts it, so there is no endpoint to ping. 988 installs a week from npm. Last commit 25 Oct 2026.

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

Installs per day peak 377 · avg 75 · +113% w/w
a month agotoday
988
Installs / week
npm · @veritasacta/verify
5
Stars
5 open issues
25 Oct 2026
Last commit
35 releases in 90 days
Apache-2.0
License
JavaScript

What the code does

We read the source, 7 d ago · rules 995398eba69f

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims local-only, but the code calls out src/engines/watch.js:16, [пакет] src/engines/watch.js:16
import { readFileSync, readdirSync, statSync } from 'node:fs';
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Package points at a different repository scopeblind/scopeblindd2
пакет @veritasacta/verify ссылается на veritasacta/verify
  const child = spawn(cmd, args, {
Reads files and sends them to the network src/engines/watch.js:16, [пакет] src/engines/watch.js:16
import { readFileSync, readdirSync, statSync } from 'node:fs';

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Veritasacta Verify and you get told the day something new turns up.

Three servers free · no card

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": {
      "command": "npx",
      "args": [
        "-y",
        "@veritasacta/verify"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.veritasacta-verify]
command = "npx"
args = ["-y", "@veritasacta/verify"]
.cursor/mcp.json
{
  "mcpServers": {
    "veritasacta-verify": {
      "command": "npx",
      "args": [
        "-y",
        "@veritasacta/verify"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "veritasacta-verify": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@veritasacta/verify"
      ]
    }
  }
}

Alternatives to Veritasacta Verify

same job, measured the same way
Verify MCP
by tomjwxf

Offline Ed25519 verification of signed receipts, bundles, and trust artifacts.

79 installs/wk local only
Verify MCP
by scopeblind

Offline Ed25519 verification of signed receipts, bundles, and trust artifacts.

local only
TrustBench
by lithvall

x402 provider rankings + Ed25519-signed payment receipts + signature verification (3 tools).

78 installs/wk 3 tools answering
Baton
by vinsenzo83

Hand off AI work with a signed Verification Receipt — an independent verifier proves it runs.

43 installs/wk 45 tools answering
Receipt — sign an agent's work, verify it offline
by ecstatica

Ed25519 receipts over work artifacts: issue and verify offline, no account, no chain, no network.

2 tools answering
Soma
by medianemi-beep

Execution-verified code generation and verification with signed, offline-checkable certificates.

42 installs/wk local only
VerifyAPI — fact-check with signed receipts
by kythekitty

Fact-check any claim with live web sources. Ed25519-signed receipts. Catches hallucinations.

78 installs/wk local only
Ari MCP Py
by antmanbuilds

Python MCP server: fair-price checks, leaderboards, Ed25519 receipt verification for x402/MPP.

128 installs/wk local only

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 988 times last week.
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 in the form 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 988 times in the last week. Week over week that is +113%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Veritasacta Verify open source?
Yes — it is published under the Apache-2.0 licence, written in JavaScript, 5 stars on GitHub and 5 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.