Zero Core Verify

io.github.meltingpixelsaiPublished by GitHub account meltingpixelsaiv1.0.0Updated Oct 24, 2026

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

The publisher's own server: core.blue

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Zero Core Verify lets an assistant verify the outcome of service calls after a transaction, scoring responses with code checks and an LLM judge and tracking per

What you can do
List available verification tools with their pricing and input requirements, and check server status, uptime and payment network configuration. Verify a post-transaction outcome: code checks the response against an expected schema or required fields and a measured time limit, then an AI judge scores accuracy and completeness. Record a simple pass/fail outcome report without LLM analysis, as a cheaper alternative to full verification. Retrieve aggregated quality scores for a service, including pass rates, average completeness and accuracy, counting each paying wallet once.
When to use it
Use it when you need to confirm that a paid or external service call actually returned what was promised, or when you want to log simple success/failure results and look up a service's historical quality before relying on it.
Requirements
Runs as a remote endpoint or as a local npm package over streamable HTTP. No authentication, environment variables or headers are declared. Some tools involve pricing and payment network configuration, so a paying wallet appears to be needed for verification.
Before you install
Verification and quality lookups are tied to paying wallets and pricing, so calls may cost money. The verify tool sends responses to an AI judge for scoring, meaning response content leaves your machine. Outcome reports and quality scores are written to a shared quality database, so recorded results are visible to others.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.meltingpixelsai%2Fzero-core-verify/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

This repository has no README.

Tools

5

list_tools

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

Takes no parameters.

health

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

Takes no parameters.

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.

Parametersservice_idresponse_datarequiredexpected_schemasla_requirementsrequest_descriptionrequiredsla_max_response_time_msobserved_response_time_ms

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.

Parametersservice_idrequired

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.

Parametersnotesservice_idrequiredwas_successfulrequiredresponse_time_ms

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • 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.

Other Core integrations