Connect Zero Core Verify and your agent gets 5 tools, among them get_service_quality, health, list_tools. It answers at https://verify.rugslayer.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.
Post-tx outcome verification via LLM-as-judge. Zero Core Verify.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_service_quality | 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. Inputs: service_id |
health | Check Harvey Verify server status, uptime, and payment network configuration. |
list_tools | List all available Harvey Verify tools with pricing and input requirements. Use this for discovery. |
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. Inputs: service_id, was_successful, response_time_ms, notes |
verify_outcome | 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. Inputs: request_description, response_data, expected_schema, sla_requirements, service_id |
Every block below points at https://verify.rugslayer.com/mcp. Pick your client and copy.
claude mcp add --transport http zero-core-verify https://verify.rugslayer.com/mcp
{
"mcpServers": {
"zero-core-verify": {
"command": "npx",
"args": ["-y", "mcp-remote", "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"
}
}
}{
"context_servers": {
"zero-core-verify": {
"url": "https://verify.rugslayer.com/mcp"
}
}
}{
"mcpServers": {
"zero-core-verify": {
"serverUrl": "https://verify.rugslayer.com/mcp"
}
}
}{
"mcpServers": {
"zero-core-verify": {
"url": "https://verify.rugslayer.com/mcp"
}
}
}name: Zero Core Verify
version: 0.0.1
schema: v1
mcpServers:
- name: Zero Core Verify
type: streamable-http
url: https://verify.rugslayer.com/mcp{
"mcpServers": {
"zero-core-verify": {
"httpUrl": "https://verify.rugslayer.com/mcp"
}
}
}{
"mcpServers": {
"zero-core-verify": {
"type": "http",
"url": "https://verify.rugslayer.com/mcp"
}
}
}{
"mcpServers": {
"zero-core-verify": {
"url": "https://verify.rugslayer.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fverify.rugslayer.com%2Fmcp&type=streamable_http&id=zero-core-verify&name=Zero%20Core%20Verify
It answered our last check on 22 October 2026 in 330 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
5, as returned by the server's own tools/list on 17 September 2026: get_service_quality, health, list_tools, report_outcome, verify_outcome.
It answered our last check on 22 October 2026 in 330 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://verify.rugslayer.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.meltingpixelsai. Endpoint host: verify.rugslayer.com. ARD identifier: urn:air:io.github.meltingpixelsai:mcp:zero-core-verify.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.