Search / io.github.meltingpixelsai/zero-core-verify
zero-core-verify
R0· no sign-inPost-tx outcome verification via LLM-as-judge. Zero Core Verify.
v1.0.0 · active · repository · website · descriptor JSON · versions
Search / io.github.meltingpixelsai/zero-core-verify
R0· no sign-inPost-tx outcome verification via LLM-as-judge. Zero Core Verify.
v1.0.0 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"zero-core-verify": {
"type": "http",
"url": "https://verify.rugslayer.com/mcp"
}
}
}claude mcp add --transport http zero-core-verify https://verify.rugslayer.com/mcp[mcp_servers.zero-core-verify]
url = "https://verify.rugslayer.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zero-core-verify": {
"type": "remote",
"url": "https://verify.rugslayer.com/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"zero-core-verify": {
"type": "http",
"url": "https://verify.rugslayer.com/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=zero-core-verify&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdmVyaWZ5LnJ1Z3NsYXllci5jb20vbWNwIn0%3D"
}{
"servers": {
"zero-core-verify": {
"type": "http",
"url": "https://verify.rugslayer.com/mcp"
}
}
}{
"mcpServers": {
"zero-core-verify": {
"httpUrl": "https://verify.rugslayer.com/mcp"
}
}
}extensions:
"zero-core-verify":
enabled: true
name: "zero-core-verify"
type: streamable_http
uri: "https://verify.rugslayer.com/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky onestools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: report_outcome (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_tools (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); health (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …tools.token_costabout 850 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns3 advisories to act on (malicious, or rated high or critical with a fix available): GHSA-w2fm-25vw-vh7f in [email protected] (indirect, fixed in 1.1.0), GHSA-96hv-2xvq-fx4p in [email protected] (indirect, fixed in 8.21.0), GHSA-96hv-2xvq-fx4p in [email protected] (indirect, fixed in 8.21.0); 5 more of lower severity or without a fixdeps.mcp_sdk_version@modelcontextprotocol/sdk 1.18.2 has 4 known advisories (GHSA-345p-7cg4-v4c7, GHSA-6qxp-vccf-f47h, GHSA-8r9q-7v3j-jr4g, ...); update @modelcontextprotocol/sdk to 1.31.0 or laterdeps.resolvable@meltingpixels/[email protected] resolved: 639 packagesNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo +website +reachable +uptime-100% ~updated-173d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
@meltingpixels/[email protected] npm638 dependencies, resolved · MCP SDK @modelcontextprotocol/sdk 1.30.1 · advisories checked 2026-10-19
| advisory | severity | package | fixed in |
|---|---|---|---|
| GHSA-345p-7cg4-v4c7@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse | high | @modelcontextprotocol/[email protected]MCP SDK, indirect | fixed in 1.26.0 |
| GHSA-6qxp-vccf-f47hMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server | high | @modelcontextprotocol/[email protected]MCP SDK, indirect | fixed in 1.31.0 |
| GHSA-6qxp-vccf-f47hMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server | high | @modelcontextprotocol/[email protected]MCP SDK, direct | fixed in 1.31.0 |
| GHSA-8r9q-7v3j-jr4gAnthropic's MCP TypeScript SDK has a ReDoS vulnerability | high | @modelcontextprotocol/[email protected]MCP SDK, indirect | fixed in 1.25.2 |
| GHSA-w48q-cv73-mx4wModel Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default | high | @modelcontextprotocol/[email protected]MCP SDK, indirect | fixed in 1.24.0 |
| GHSA-w2fm-25vw-vh7fmcp-handler has a tool response leak across concurrent client sessions ('Race Condition') | high | [email protected]indirect | fixed in 1.1.0 |
| GHSA-96hv-2xvq-fx4pws: Memory exhaustion DoS from tiny fragments and data chunks | high | [email protected]indirect | fixed in 8.21.0 |
| GHSA-96hv-2xvq-fx4pws: Memory exhaustion DoS from tiny fragments and data chunks | high | [email protected]indirect | fixed in 8.21.0 |
| GHSA-vcc3-ghjq-m6frdecode-uri-component: Denial of service via exponential decoding of malformed percent-encoded input | moderate | [email protected]indirect | fixed in 0.5.0 |
| GHSA-w5hq-g745-h8pquuid: Missing buffer bounds check in v3/v5/v6 when buf is provided | moderate | [email protected]indirect | fixed in 11.1.1 |
3 more advisories in the dependencies endpoint.
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://verify.rugslayer.com/mcp streamable-http | none | yes | 100% | 192 ms | 2025-06-18 | 2026-10-20 |
| package | registry | version | runtime | secrets |
|---|---|---|---|---|
@meltingpixels/zero-core-verify | npm | 1.0.0 | – |
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. |
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. |
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. |
Schemas: list_tools.
{
"name": "io.github.meltingpixelsai/zero-core-verify",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://verify.rugslayer.com/mcp",
"type": "streamable-http"
}
],
"version": "1.0.0",
"packages": [
{
"version": "1.0.0",
"transport": {
"url": "https://verify.rugslayer.com/mcp",
"type": "streamable-http"
},
"identifier": "@meltingpixels/zero-core-verify",
"registryType": "npm"
}
],
"repository": {
"url": "https://github.com/meltingpixelsai/harvey-verify",
"source": "github"
},
"websiteUrl": "https://relayzero.ai",
"description": "Post-tx outcome verification via LLM-as-judge. Zero Core Verify."
}