argushq.ai/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 578 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-003 | OK | — | 722 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-004 | OK | — | 616 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-005 | OK | — | 672 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-006 | OK | — | 652 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-007 | OK | — | 788 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-008 | OK | — | 706 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-009 | OK | — | 619 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-010 | OK | — | 735 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-011 | OK | — | 730 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-012 | OK | — | 741 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-013 | OK | — | 617 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-014 | OK | — | 718 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-015 | OK | — | 558 | 5 | 2cb5c86ddfe5427e… | |
| REL-SNAP-016 | OK | — | 394 | 5 | 2cb5c86ddfe5427e… |
Identity
- Record key
argushq.ai/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- ai.argushq/enforcement-database 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
- mcp-typescript server on vercel 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.