astranl.com/mcp/streamable
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-008 | OK | — | 393 | 43 | db25a69df89fcb92… | |
| REL-SNAP-009 | OK | — | 728 | 45 | f8d0a5349d78068b… | |
| REL-SNAP-010 | OK | — | 395 | 45 | f8d0a5349d78068b… | |
| REL-SNAP-011 | OK | — | 375 | 59 | 37ce606e812cd264… | |
| REL-SNAP-012 | OK | — | 587 | 60 | d6e10be69b68e35e… | |
| REL-SNAP-013 | OK | — | 374 | 60 | d6e10be69b68e35e… | |
| REL-SNAP-014 | OK | — | 376 | 60 | d6e10be69b68e35e… | |
| REL-SNAP-015 | OK | — | 84 | 62 | 086e1a1d44274c47… | |
| REL-SNAP-016 | OK | — | 42 | 62 | 086e1a1d44274c47… | |
| REL-SNAP-017 | OK | — | 56 | 71 | 3afafa9f5fd1d22c… | |
| REL-SNAP-018 | OK | — | 152 | 71 | 3afafa9f5fd1d22c… | |
| REL-SNAP-019 | OK | — | 73 | 5 | 801e47488711342d… | |
| REL-SNAP-020 | OK | — | 34 | 8 | bb0ff70a3f00a00d… | |
| REL-SNAP-021 | OK | — | 177 | 8 | bb0ff70a3f00a00d… | |
| REL-SNAP-022 | OK | — | 40 | 8 | bb0ff70a3f00a00d… | |
| REL-SNAP-023 | OK | — | 59 | 8 | bb0ff70a3f00a00d… | |
| REL-SNAP-024 | OK | — | 369 | 8 | bb0ff70a3f00a00d… | |
| REL-SNAP-025 | OK | — | 38 | 8 | bb0ff70a3f00a00d… | |
| REL-SNAP-026 | OK | — | 65 | 6 | 40d5e778bf0ad211… |
Tool schema changed 8 times 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
astranl.com/mcp/streamable— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.astranl/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
- astranl-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.