api.algovault.com/mcp
Last observed:— recorded as OK
Affiliation disclosure. This endpoint is operated by an entity affiliated with MCP Verify since 2026-08-06. It is excluded from every ranking and from any aggregate presented as independent evidence.
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 430 | 7 | d8058494d2d32128… | |
| REL-SNAP-003 | OK | — | 445 | 7 | d8058494d2d32128… | |
| REL-SNAP-004 | OK | — | 480 | 7 | d8058494d2d32128… | |
| REL-SNAP-005 | OK | — | 455 | 7 | d8058494d2d32128… | |
| REL-SNAP-006 | OK | — | 531 | 7 | d8058494d2d32128… | |
| REL-SNAP-007 | OK | — | 486 | 7 | d8058494d2d32128… | |
| REL-SNAP-008 | OK | — | 482 | 7 | d8058494d2d32128… | |
| REL-SNAP-009 | OK | — | 458 | 7 | d8058494d2d32128… | |
| REL-SNAP-010 | OK | — | 494 | 7 | d8058494d2d32128… | |
| REL-SNAP-011 | OK | — | 458 | 7 | d8058494d2d32128… | |
| REL-SNAP-012 | OK | — | 498 | 7 | d8058494d2d32128… | |
| REL-SNAP-013 | OK | — | 460 | 7 | d8058494d2d32128… | |
| REL-SNAP-014 | OK | — | 538 | 7 | d8058494d2d32128… | |
| REL-SNAP-015 | OK | — | 316 | 7 | d8058494d2d32128… | |
| REL-SNAP-016 | OK | — | 757 | 7 | 98e89edac8682155… |
Tool schema changed 1 time across this history — the fingerprint differs between consecutive observations. A change can occur while the tool count stays identical, which is why the fingerprint is recorded alongside the count.
Identity
- Record key
api.algovault.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.AlgoVaultFi/crypto-quant-signal-mcp What the registry said when we swept it, as observed by us — not evidence that the registry was correct, that the name belongs to whoever registered it, or that it still resolves. Not covered by the chain: no inclusion proof reaches this field.
- Name reported by the server
- crypto-quant-signal-mcp Self-reported and unverified — never used as identity.
Verifying this record
Each observation above carries a merkle leaf in the published snapshot it belongs to. Verify the chain explains how to walk a leaf to a published root without taking our word for any of it.