Verify Mcp

io.github.tomjwxfPublished by GitHub account tomjwxfv0.1.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an assistant verify Ed25519 signatures on signed receipts, bundles and trust artifacts, entirely offline.

What you can do
Verify Ed25519 signatures on signed receipts, bundles and trust artifacts, working offline without network calls. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to check that a signed receipt, bundle or trust artifact carries a valid Ed25519 signature, and the check should happen locally without sending data out.
Requirements
Runs as a local process over stdio, installed from the npm package @scopeblind/verify-mcp, so a Node.js runtime is needed. Desktop only; no authentication, environment variables or headers are declared.
Before you install
The manifest lists no tools, so what the server reads or writes cannot be confirmed from this listing. Review the package before installing, since verification results are only as trustworthy as the code performing them.

Installation

In SourceWeft

  1. Open Verify Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.