Skip to content

io.github.meltingpixelsai/zero-core-verify

by meltingpixelsai · remote · local (npm) · no sign-in to list tools · v1.0.0 · published by GitHub user meltingpixelsai

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

Changes · 3
CompareRegistry entry

5 tools: 3 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 3Claude Code: ask
  • healthCheck Harvey Verify server status, uptime, and payment network configuration.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check Harvey Verify server status, uptime, and payment network configuration.
  • report_outcomeRecord a simple pass/fail outcome report for a service call.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • paymentHint: true
    • paymentPriceUSD: $0.002
    • paymentNetworks: [object Object]
    • paymentVersion: 1
  • verify_outcomePost-transaction verification using LLM-as-judge.No findings

    Why it is in this group

    • The description's first verb is "post": a word for a change.
    Description, as the server wrote it
    Post-transaction verification using LLM-as-judge. Checks if a service delivered what was promised. Returns completeness score, accuracy score, format compliance, SLA adherence, issues list, and overall pass/fail.

    Annotations the server declares

    • paymentHint: true
    • paymentPriceUSD: $0.01
    • paymentNetworks: [object Object]
    • paymentVersion: 1
Only reads 2Claude Code: allow
  • get_service_qualityGet aggregated quality scores for a service based on all past verifications.No findings

    Why it is in this group

    • The name "get_service_quality" says "get": a word for reading.
    Description, as the server wrote it
    Get aggregated quality scores for a service based on all past verifications. Returns average completeness, accuracy, pass rate, format compliance rate, SLA compliance rate, and quality trend.

    Annotations the server declares

    • paymentHint: true
    • paymentPriceUSD: $0.005
    • paymentNetworks: [object Object]
    • paymentVersion: 1
  • list_toolsList all available Harvey Verify tools with pricing and input requirements.No findings

    Why it is in this group

    • The name "list_tools" says "list": a word for reading.
    Description, as the server wrote it
    List all available Harvey Verify tools with pricing and input requirements. Use this for discovery.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__zero-core-verify__list_tools",
      "mcp__zero-core-verify__get_service_quality"
    ],
    "ask": [
      "mcp__zero-core-verify__health",
      "mcp__zero-core-verify__verify_outcome",
      "mcp__zero-core-verify__report_outcome"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as zero-core-verify. Review it before you use it.