MCP server list / zero-core-verify
Post-tx outcome verification via LLM-as-judge. Zero Core Verify.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 213 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 202 ms.
- Address
- https://verify.rugslayer.com/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.meltingpixelsai/
zero-core-verify - Transport
- streamable HTTP
streamable-http - Host
verify.rugslayer.com
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- harvey-verify
- Version:
- 1.0.0
- MCP features it lists:
- tools
- Tool names:
list_toolshealthverify_outcomeget_service_qualityreport_outcome
Reported Aug 17, 2026, 05:08 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 35 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 268 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 224 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 202 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.