verifiable-claim-seed

io.github.elwslsPublished by GitHub account elwslsv1.3.1Updated Oct 27, 2026

Zero-dependency verifiable-claims MCP: validate safely, verify with allow_execution, self-test.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A zero-dependency local MCP server for validating and verifying verifiable claims, with an opt-in execution mode and a self-test.

What you can do
  • Validate verifiable claims safely through the server's validation tooling.
  • Verify claims, with execution gated behind an allow_execution option.
  • Run a self-test to check the server is working.
  • No tool list is published, so the exact tool names and inputs are not documented in the available material.
When to use it
Worth considering when you want an assistant to check verifiable-claim data locally and prefer a small, dependency-free server that keeps execution off unless explicitly enabled.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package verifiable-claim-seed and started with uvx, so a Python/uv environment is needed. Desktop client only; no authentication, environment variables or headers are declared.
Before you install
The verification path can execute code when allow_execution is enabled, so keep it off unless you trust the claims being checked. No tool list, README or instructions are provided, so behavior beyond the one-line description cannot be confirmed before installing.

Installation

In SourceWeft

  1. Open verifiable-claim-seed 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. v1.3.1LatestSep 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.