Zero Core Verify MCP Server

by meltingpixelsai Your server? Claim it

answering

Zero Core Verify is answering right now. Last checked 3 min ago. 31 installs a week from npm. It exposes 5 tools. Last commit 29 Oct 2026.

Post-tx outcome verification via LLM-as-judge. Zero Core Verify.

Installs per day peak 8 · avg 2 · +158% w/w

a month agotoday

Uptime history 91 days of history

91 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

387 ms

Response time

average over 24h

Installs / week

npm and PyPI

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 23 October 2026. No other catalogue keeps this.

23 Oct 2 tool descriptions were rewritten3 times that day get_service_quality, verify_outcome

23 Oct 3 tools changed the parameters they ask for get_service_quality, report_outcome, verify_outcome

and 1 more, back to 23 October 2026

What the code does

We read the source, 5 d ago · tools taken from the live server · rules 995398eba69f

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.

Package points at a different repository meltingpixelsai/zero-core-verify

пакет @meltingpixels/zero-core-verify ссылается на meltingpixelsai/harvey-verify

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.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add zero-core-verify --transport http https://verify.rugslayer.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://verify.rugslayer.com/mcp

~/.codex/config.toml

[mcp_servers.zero-core-verify]
url = "https://verify.rugslayer.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "zero-core-verify": {
      "url": "https://verify.rugslayer.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "zero-core-verify": {
      "type": "http",
      "url": "https://verify.rugslayer.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

health

health

Check Harvey Verify server status, uptime, and payment network configuration.

report

report_outcome

Record a simple pass/fail outcome report for a service call. No LLM analysis - just logs the result to the quality database. Cheaper alternative to verify_outcome when you only need to record success/failure.

service

get_service_quality

Get aggregated quality scores for a service based on past verifications and reports, counting each paying wallet once (its latest). Returns the pass rate (overall, and over the rows where code checked the format or a measured time), average completeness and accuracy over the scored rows with their count, the count of inconclusive rows, format and SLA compliance rates, and a trend by pass rate. The scores are self-reported by paying wallets and not attested: nothing proves a reporter used the service.

tools

list_tools

List all available Harvey Verify tools with pricing and input requirements. Use this for discovery.

verify

verify_outcome

Post-transaction verification. Code checks what it can: the response against expected_schema (a JSON Schema or a list of required field names), and a measured response time against a stated limit. A response that fails code's checks fails without the AI judge; otherwise the judge scores accuracy and completeness as advice. Without a schema or a time limit only the judge decides, and decided_by says so. Returns a verdict (pass, fail or inconclusive), decided_by, scores, format compliance, SLA result, issues, and what code checked.

Endpoints

URL	Transport	State	Latency	Checked
https://verify.rugslayer.com/mcp	streamable-http	answering	329 ms	3 min ago

Alternatives to Zero Core Verify

same job, measured the same way

Cancellation-outcome verification

by textforagents

You cancelled the run — did the work actually stop?

3 tools answering

Agent Output Guard

by agenson-horrowitz

Validate and verify data from other agents before acting on it. Zero LLM costs.

55 installs/wk local only

Trust Gate

by botagram

Merchant trust verification for agentic commerce. Verify any merchant before autonomous payment.

37 installs/wk local only

AI Architect MCP Spec

by cdeust

PRD verification and host-driven generation with multi-judge consensus across 17 MCP tools.

local only

LLMVerify

by subodhkc

Local-first MCP server for LLM output verification — risk signals, injection and PII checks.

579 installs/wk local only

Otr Protocol

by yb48666-ctrl

Merchant trust verification for AI agents. One call = trust score, badge, and purchase safety.

46 installs/wk local only

EnvoAPI

by envoapi

People, company, job and LinkedIn post data, plus email finding and verification.

answering

Emailable

by pipeworx-io

Emailable MCP — wraps the Emailable email verification API (emailable.com)

498 installs/wk 45 tools answering

Zero Core Verify — questions

Answers built from our own checks of this server.

What can Zero Core Verify do?

It exposes 5 tools, read directly from the server on our last check. Among them: get_service_quality, health, list_tools, report_outcome, verify_outcome. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Zero Core Verify working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 387 ms. The bar chart above shows every period we have measured.

How do I connect Zero Core Verify?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Zero Core Verify need an API key?

No. Zero Core Verify completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Zero Core Verify?

It answers our handshake in 387 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Zero Core Verify?

The npm package @meltingpixels/zero-core-verify was installed 31 times in the last week. Week over week that is +158%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Zero Core Verify open source?

The code is open source: it is published under the MIT licence, written in TypeScript, 1 stars on GitHub and 2 open issues. The licence covers the code in the repository, not the hosted service at verify.rugslayer.com, which runs on its operator's own terms.