mcpbeat Sign in

verifiable-claim-seed MCP Server

local only

verifiable-claim-seed runs on your own machine — the client starts it, so there is no endpoint to ping. 50 installs a week from pypi. Last commit 24 Aug 2026.

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

Installs per day peak 548 · avg 56 · -93% w/w
a month agotoday
50
Installs / week
pypi · verifiable-claim-seed
0
Stars
0 open issues
24 Aug 2026
Last commit
0 releases in 90 days
MIT
License
HTML

What the code does

We read the source, 23 h ago · rules 3dff92dd89df

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.

    proc = subprocess.Popen(cmd, stdin=subprocess.PIPE, stdout=subprocess.PIPE,
<script type="module" crossorigin="" src="https://cdn.ncbi.nlm.nih.gov/pmc/pd-medc-pmc-cloudpmc-viewer/production/bb3d0162/var/data/static/assets/base_style-D-jH62-1.js"></script>

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

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

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 verifiable-claim-seed -- uvx verifiable-claim-seed
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "verifiable-claim-seed": {
      "args": [
        "verifiable-claim-seed"
      ],
      "command": "uvx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.verifiable-claim-seed]
command = "uvx"
args = ["verifiable-claim-seed"]
.cursor/mcp.json
{
  "mcpServers": {
    "verifiable-claim-seed": {
      "args": [
        "verifiable-claim-seed"
      ],
      "command": "uvx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "verifiable-claim-seed": {
      "args": [
        "verifiable-claim-seed"
      ],
      "command": "uvx"
    }
  }
}

Alternatives to verifiable-claim-seed

same job, measured the same way
Ideabob Validation
by foodyogi

Score, validate, and pressure-test startup ideas with AI from Claude or any MCP agent.

5 tools answering
Mockserver
by mock-server

Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.

local only
E2e Runner
by fastslack

JSON-driven E2E test runner with parallel Chrome pool execution and 16 MCP tools.

53 installs/wk local only
Cucumberstudio
by herosizy

MCP server for Cucumber Studio - test scenarios, action words, and execution data

59 installs/wk local only
AI Validation
by zuhcya

Independent AI code validation: test bias, edge cases, coverage gaps.

30 installs/wk local only
Qatouch
by qatouch

MCP Server for software testing, test case management, test execution, and defect tracking.

113 installs/wk local only
Zephyr Scale MCP
by vilaabo

Zephyr Scale on self-hosted Jira Server/DC: test cases, cycles, executions, plans and attachments

55 installs/wk local only
Provar MCP Server
by provartesting

Provar MCP: AI-powered Salesforce test automation. Generate, validate, migrate, and run tests.

427 installs/wk local only

verifiable-claim-seed — questions

Answers built from our own checks of this server.

Why is there no uptime for verifiable-claim-seed?
verifiable-claim-seed 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 pypi package verifiable-claim-seed was installed 50 times last week.
How do I connect verifiable-claim-seed?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls verifiable-claim-seed straight from pypi; nothing to host, nothing to sign up for.
How many people use verifiable-claim-seed?
The pypi package verifiable-claim-seed was installed 50 times in the last week. Week over week that is -93%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is verifiable-claim-seed open source?
Yes — it is published under the MIT licence, written in HTML and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.