Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.meltingpixelsai/zero-core-verify

REMOTE · VERIFY.RUGSLAYER.COM · 2 COMPONENTS

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

0 this week 75 Trust /100

Last scanned (13 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 590 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management88
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 84 to 88.

  • 10 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 88 to 84.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 84 to 88.

  • 8 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 88 to 84.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 84 to 88.

  • 6 Nov 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 84 to 88.

  • 4 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 88 to 84.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://verify.rugslayer.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=verify.rugslayer.com CN=YE1,O=Let's Encrypt,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA384 5fed530ca12504f46ac15e83a4a735a5327
SANs: verify.rugslayer.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of verify.rugslayer.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
rugslayer.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://verify.rugslayer.com/mcp Verified 200
http (plaintext) http://verify.rugslayer.com/mcp HTTPS enforced 301 https://verify.rugslayer.com/mcp
MCP tools · 5 exposed · ~590 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_service_quality ~132

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.

NameTypeReqDescription
service_idstringyesService identifier to query (e.g. 'harvey-tools/scrape_url')

No output schema declared.

No examples provided.

health ~20

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_tools ~25

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

report_outcome ~114

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.

NameTypeReqDescription
notesstring–Optional notes about the outcome
response_time_msinteger–Response time in milliseconds
service_idstringyesService identifier (e.g. 'harvey-tools/scrape_url')
was_successfulbooleanyesWhether the service call succeeded

No output schema declared.

No examples provided.

verify_outcome ~299

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.

NameTypeReqDescription
expected_schemastring–A JSON Schema, or two or more required top-level field names (letters, digits, _ and -) separated by commas, e.g. 'name, price, url'. Anything else is passed to the AI judge only.
observed_response_time_msinteger–The response time you measured, in milliseconds
request_descriptionstringyesWhat was requested from the service
response_datastringyesThe actual response/output received from the service
service_idstring–Service identifier for quality tracking (e.g. 'harvey-tools/scrape_url')
sla_max_response_time_msinteger–The response time limit, in milliseconds
sla_requirementsstring–SLA wording for the AI judge (e.g. 'must include all fields'). For a time limit code can check, use the two fields below.

No output schema declared.

No examples provided.

Install

How do I install the io.github.meltingpixelsai/zero-core-verify MCP server?

io.github.meltingpixelsai/zero-core-verify is a hosted endpoint at https://verify.rugslayer.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · verify.rugslayer.com

# add to Claude Code
claude mcp add --transport http meltingpixelsai-zero-core-verify 'https://verify.rugslayer.com/mcp'
Common questions

What is the io.github.meltingpixelsai/zero-core-verify MCP server?

io.github.meltingpixelsai/zero-core-verify is an MCP server listed in the public MCP registry as io.github.meltingpixelsai/zero-core-verify. Post-tx outcome verification via LLM-as-judge. Zero Core Verify. This page covers its hosted endpoint (https://verify.rugslayer.com/mcp).

Is the io.github.meltingpixelsai/zero-core-verify MCP server safe to use?

io.github.meltingpixelsai/zero-core-verify scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.meltingpixelsai/zero-core-verify MCP server expose?

io.github.meltingpixelsai/zero-core-verify exposes 5 tools: list_tools, health, verify_outcome, get_service_quality, report_outcome. Their descriptions and schemas cost roughly 590 tokens of context every time the server is loaded.

Does the io.github.meltingpixelsai/zero-core-verify MCP server require authentication?

No. We connected to io.github.meltingpixelsai/zero-core-verify without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.meltingpixelsai/zero-core-verify MCP server still maintained?

io.github.meltingpixelsai/zero-core-verify is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.meltingpixelsai/zero-core-verify MCP server?

VerifyMCP ran 12 checks on io.github.meltingpixelsai/zero-core-verify, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.meltingpixelsai/zero-core-verify: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.