Post-tx outcome verification via LLM-as-judge. Zero Core Verify.
Connect Remote server
claude mcp add --transport http zero-core-verify https://verify.rugslayer.com/mcp
{
"mcpServers": {
"zero-core-verify": {
"url": "https://verify.rugslayer.com/mcp"
}
}
}
{
"servers": {
"zero-core-verify": {
"type": "http",
"url": "https://verify.rugslayer.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://verify.rugslayer.com/mcp
Tools 5 found in our last check
list_toolsList all available Harvey Verify tools with pricing and input requirements. Use this for discovery.
healthCheck Harvey Verify server status, uptime, and payment network configuration.
verify_outcomePost-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 judg…
get_service_qualityGet 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 sco…
report_outcomeRecord 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.
Details
| Endpoint | https://verify.rugslayer.com/mcp (Streamable HTTP) |
| Package | @meltingpixels/[email protected] (NPM, streamable-http) |
| First published | 30 Apr 2026 |
| Last updated | 30 Apr 2026 |
| Registry name | io.github.meltingpixelsai/zero-core-verify |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
