Verify Mcp

com.scopeblindPublished by scopeblind.comv0.1.3Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Local MCP server that lets an assistant verify Ed25519 signatures on signed receipts, bundles and trust artifacts, fully offline.

What you can do
  • Verify Ed25519 signatures on signed receipts, bundles and trust artifacts.
  • Run verification locally without network access, so signed material can be checked inside an assistant session.
  • No tool list is published, so the exact operations and their inputs are not documented in the supplied material.
When to use it
Useful when an assistant needs to confirm that a signed receipt, bundle or trust artifact is authentic before relying on it, and the check should happen on the user's own machine without contacting an external service.
Requirements
Runs as a local stdio process installed from the npm package @scopeblind/verify-mcp, so a Node.js runtime and npm are needed. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
The server handles cryptographic verification material; treat keys and signed artifacts as sensitive and keep them local. No tool list or README is provided, so review what it reads and writes before installing. Verification only confirms signatures, not the trustworthiness of the signer.

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.3LatestSep 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.