Skip to content

zero-core-verify MCP server

io.github.meltingpixelsai/zero-core-verifymeltingpixelsaistreamable-httpv1.0.0Scanned

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

5 tools: 3 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the zero-core-verify MCP server can do

The zero-core-verify MCP server is published by the GitHub account meltingpixelsai. It has 5 tools. It can create or change data (3 tools: health, verify_outcome and report_outcome), but cannot delete data. 2 tools only read.

1 tool can send data out of your system (verify_outcome).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

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.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "post": a word for a change.

    What it can reach

    • outboundThe description's first verb is "post": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • paymentHint: true
    • paymentPriceUSD: $0.01
    • paymentNetworks: [object Object]
    • paymentVersion: 1
Only reads 2Show 2 read-only tools
  • get_service_qualityGet aggregated quality scores for a service based on past verifications and reports, counting each paying wallet once (its latest).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 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.

    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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:23 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://verify.rugslayer.com/mcp: tools/list returned 5 tools to an anonymous client, including health (write), verify_outcome (write), report_outcome (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff

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
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as zero-core-verify. Review it before you use it.

Capability tags behind 1 rule
  • mcp__zero-core-verify__verify_outcome outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.meltingpixelsai/zero-core-verify/verify?hash=b1bed9e87d41ceaff7eda26af10bf49c6995519da6bf4ff8222810b950317268" | jq -e '.changed == false'

Pinned hash b1bed9e87d41, from Nov 21, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.meltingpixelsai/zero-core-verify/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.meltingpixelsai/zero-core-verify
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.meltingpixelsai/zero-core-verify.svg)](https://radar.anlyon.com/servers/io.github.meltingpixelsai/zero-core-verify)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:40 UTC.

zero-core-verify MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the zero-core-verify MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the zero-core-verify MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the zero-core-verify MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the zero-core-verify MCP server have?

5 tools: 3 write, 2 read. health, verify_outcome, report_outcome, list_tools and get_service_quality.

Does the zero-core-verify MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the zero-core-verify MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): verify_outcome.

Has the zero-core-verify MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 7, 2026. Every change is on this page and in its Atom feed.