api.vrsai.tech/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-021 | HTTP_4XX | http_400_modern_era | — | — | — | |
| REL-SNAP-022 | OK | — | 108 | 5 | cf9cdcdaee4b3dff… | |
| REL-SNAP-023 | OK | — | 119 | 6 | 158d7f43fd96c753… | |
| REL-SNAP-024 | OK | — | 448 | 6 | 158d7f43fd96c753… | |
| REL-SNAP-025 | OK | — | 375 | 6 | 158d7f43fd96c753… | |
| REL-SNAP-026 | OK | — | 590 | 6 | 158d7f43fd96c753… |
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.vrsai.tech/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- tech.vrsai/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
- vrsai 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.