Paceproof

Name: Paceproof
Author: RudrenduPaul

by RudrenduPaulversion 0.1.1i★ –iRuns on your computer

Registry nameio.github.RudrenduPaul/paceproof

Install

Overview

Description from the maker (original English)

Verifies Ed25519-signed attestation records and builds audit reports via MCP tools.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "paceproof": {
      "command": "npx",
      "args": [
        "-y",
        "paceproof-cli",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add paceproof -- npx -y paceproof-cli mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "paceproof": {
      "command": "npx",
      "args": [
        "-y",
        "paceproof-cli",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "paceproof": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "paceproof-cli",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account RudrenduPaul, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18333 servers in this category
Published to the registry more recently than 20% of the other 18333 servers in this category
Basic checks equal to or better than 100% of the other 18333 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Paceproof safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Signoff

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Signoff

by ayuanxx-max

Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

PaceProof

PaceProof verifies Ed25519-signed compute-attestation records from any provider and tells you exactly which ones are real.

A record with a missing, malformed, or tampered signature never gets folded into a "verified" total; it's counted and reported separately, every time, in both human-readable and --json output.

PaceProof does not sign or generate attestations. It is a neutral, read-only ingest/verify/report/dashboard layer over records that are already signed somewhere else. Point it at a directory, file, or URL of signed records and it tells you, verifiably, what compute was actually run, by whom, and whether every record's signature checks out.

Install

paceproof-cli is published to both npm and PyPI:

npm install -g paceproof-cli

or

pip install paceproof-cli

Both commands install a paceproof binary. paceproof-cli is also available as an alias on both registries if you need to disambiguate from another tool on your PATH.

To build from source instead (useful if you're contributing, or want the exact repo state rather than a published release):

TypeScript (npm package, includes the MCP server):

git clone https://github.com/RudrenduPaul/PaceProof.git

cd PaceProof/packages/cli-ts npm install npm run build node dist/bin.js --help

Python (PyPI package, independent reimplementation):

git clone https://github.com/RudrenduPaul/PaceProof.git

cd PaceProof/packages/cli-py pip install -e . paceproof --help

Both the published npm install -g paceproof-cli and pip install paceproof-cli commands above were run fresh in a clean environment as part of writing this README, and the quickstart output below is real output from those installs, not fabricated.

Features
Quickstart
CLI command reference
Library API reference
How verification works
Comparison
What PaceProof is, and why it exists
FAQ
Contributing
License

Quickstart

paceproof init

paceproof report ./paceproof-example

paceproof init generates a fresh Ed25519 example keypair and 7 example attestation records: 3 validly signed, and 4 intentionally broken (a tampered payload, a wrong-key signature, a malformed signature, and a missing signature) so verify/report have real failure modes to demonstrate, not just a happy path.

Real output from an actual run against the published npm package:

$ paceproof report ./paceproof-example

PaceProof report -- source: ./paceproof-example generated at: 2026-08-04T02:54:30.898Z

== VERIFIED == records: 3 compute total: 144.50 gpu_hours

== UNVERIFIED (never counted in verified totals above) == records: 4 compute total: 1009 gpu_hours reasons:

rec-004: signature does not match record contents
rec-005: signature does not match record contents
rec-006: signature must decode to 64 bytes, got 4
rec-007: schema validation failed: (root) must have required property 'signature'

== BY PROVIDER == acme-cloud: verified=132 gpu_hours (2 records); unverified_count=0 beta-compute: verified=12.50 gpu_hours (1 records); unverified_count=0 gamma-hpc: verified=(none); unverified_count=2 delta-cloud: verified=(none); unverified_count=2

== BY WORKLOAD TYPE == training: verified=128 gpu_hours (1 records); unverified_count=1 inference: verified=12.50 gpu_hours (1 records); unverified_count=1 idle: verified=4 gpu_hours (1 records); unverified_count=1 unknown: verified=(none); unverified_count=1

verify exits non-zero when any record fails (real exit code from an actual run: 1, with 4 unverified records present):

$ paceproof verify ./paceproof-example

Verified: 3 Unverified: 4 FAIL rec-004: signature does not match record contents FAIL rec-005: signature does not match record contents FAIL rec-006: signature must decode to 64 bytes, got 4 FAIL rec-007: schema validation failed: (root) must have required property 'signature' $ echo $? 1

Render a dashboard from the same data:

paceproof dashboard ./paceproof-example --out dashboard.html

Both the TypeScript and Python builds were run against paceproof-example for this README, and both produced the same verified/unverified counts and totals shown above.

Features

Pluggable data-source adapters. ingest normalizes arbitrary input into the canonical schema through a documented Adapter interface (TypeScript interface, Python ABC). The shipped jsonl adapter reads newline-delimited JSON already in canonical form; a provider-specific adapter (e.g. for ComputeLedger's native export) implements the same interface without touching the aggregator, report renderer, or CLI wiring.
Ed25519 verification with strict verified/unverified separation. Every record is checked for schema validity and signature validity. A record that fails either check is never silently merged into a verified total: verified and unverified counts and compute totals are computed from disjoint sets and shown side by side in every report.
Two independent, parity-tested implementations. The TypeScript package (npm) and the Python package (PyPI) are separate, real implementations, not a wrapper around one or the other. Both produce byte-identical report --json output for the same input; a CI job runs the TypeScript CLI's output against the Python CLI's output on a shared fixture in both directions and fails the build on any divergence.
Self-contained static HTML dashboard. paceproof dashboard renders a single HTML file with inline CSS and no JavaScript: no CDN fonts, no external scripts, no remote requests of any kind. Currently ships one clean light theme; there's no dark-mode toggle yet.
MCP server for agent invocation. paceproof mcp starts a Model Context Protocol server exposing verify, ingest, and report as callable tools, so an orchestrating agent can call PaceProof programmatically instead of shelling out to a human-facing CLI. The tool handlers are thin wrappers around the same aggregator/report functions the CLI itself calls, with no separate reimplementation for the MCP path.
Security-hardened by design, not by afterthought. Aggregation buckets are built with Object.create(null) so an attacker-controlled provider or compute_unit field like "__proto__" can't pollute Object.prototype. The one network call PaceProof ever makes (ingest ) is bounded by a 30-second timeout and a 50 MiB response cap, enforced against the actual streamed byte count rather than trusting a Content-Length header. Every schema field carries an explicit maximum length so oversized input can't be used to exhaust memory before validation runs.

CLI command reference

Every table below is copied from the actual --help output of the published paceproof-cli npm package (v0.1.0).

`paceproof init [path]`

Scaffold an example directory with a sample keypair and validly/invalidly signed example records.

Argument	Description
`path`	Directory to create (default: `./paceproof-example`)

`paceproof verify`

Verify Ed25519 signatures on every record found at .

Option	Description
`--json`	Output structured JSON instead of a human-readable table
`--adapter`	Adapter to use for reading input (default: `jsonl`)

`paceproof ingest`

Run a named adapter over the input and emit normalized canonical-schema records as JSONL.

Option	Description
`--adapter`	Adapter to use (default: `jsonl`)
`--out`	Write JSONL output to a file instead of stdout

`paceproof report`

Ingest and verify records at , then aggregate into a summary report.

Option	Description
`--json`	Output structured JSON instead of a human-readable table
`--adapter`	Adapter to use for reading input (default: `jsonl`)

`paceproof dashboard`

Render a single self-contained static HTML dashboard from a report.

Option	Description
`--out`	Output HTML file path (default: `paceproof-dashboard.html`)
`--adapter`	Adapter to use for reading input (default: `jsonl`)

`paceproof mcp`

Start an MCP server exposing verify, ingest, and report as callable tools. TypeScript package only for now: running paceproof mcp from the Python package prints a message pointing to the npm package and exits non-zero.

Every command supports real non-zero exit codes on failure or verification failure, and --help on every subcommand.

Library API reference

The npm package also exports its internals directly (main/types in package.json point at real library code, not just the CLI entry point), for anyone building a custom adapter or embedding verification logic in another tool instead of shelling out to the CLI. This surface is TypeScript-only; the Python package exposes paceproof as a CLI only, with no documented import API.

import { getAdapter, verifyRecords, summarize } from 'paceproof-cli';

import type { Adapter } from 'paceproof-cli';

const records = await getAdapter('jsonl').read('./paceproof-example/records.jsonl'); const outcomes = verifyRecords(records); const report = summarize(outcomes);

Export	Signature	What it does
`Adapter`	`interface Adapter { readonly name: string; read(input: string): Promise }`	The extensibility point described above. Implement this to normalize a new provider's export format into canonical records.
`getAdapter(name)`	`(name: string) => Adapter`	Looks up a registered adapter by name (`jsonl` ships built in); throws if the name isn't registered.
`verifyRecord(raw)`	`(raw: RawRecord) => VerificationOutcome`	Schema-validates and signature-verifies a single record.
`verifyRecords(raws)`	`(raws: RawRecord[]) => VerificationOutcome[]`	Runs `verifyRecord` over a batch.
`summarize(outcomes)`	`(outcomes: VerificationOutcome[]) => ReportSummary`	Aggregates verification outcomes into the same verified/unverified-by-provider/by-workload-type structure `paceproof report --json` prints.
`verifyRecordSignature(record)`	`(record: AttestationRecord) => SignatureCheckResult`	Checks only the Ed25519 signature (schema validation is separate), against the canonical JSON encoding described below.
`canonicalizeRecord(record)`	`(record: Record ) => Uint8Array`	Produces the canonical byte encoding a signature is computed and checked over: lexicographically sorted keys, UTF-8, no insignificant whitespace.

| buildCli() | () => Command | Returns the Commander.js Command instance the published CLI itself runs, if you want to embed or extend it rather than rei

Only the beginning is shown; read the rest in the repo

Paceproof

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Signoff

README from the maker

PaceProof

Install

or

Table of Contents

Quickstart

Features

CLI command reference

paceproof init [path]

paceproof verify

paceproof ingest

paceproof report

paceproof dashboard

paceproof mcp

Library API reference

`paceproof init [path]`

`paceproof verify`

`paceproof ingest`

`paceproof report`

`paceproof dashboard`

`paceproof mcp`