agent-observatory-sensor.nolimit-observatory.workers.dev/s/ns-utc/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-044 | OK | — | 80 | 30 | 9407e5f338db6181… | |
| REL-SNAP-045 | OK | — | 71 | 30 | 9407e5f338db6181… | |
| REL-SNAP-046 | OK | — | 43 | 30 | 9407e5f338db6181… | |
| REL-SNAP-047 | OK | — | 45 | 30 | 9407e5f338db6181… | |
| REL-SNAP-048 | OK | — | 48 | 30 | 9407e5f338db6181… | |
| REL-SNAP-049 | OK | — | 47 | 30 | 9407e5f338db6181… | |
| REL-SNAP-050 | OK | — | 59 | 31 | be54c474a333fa61… | |
| REL-SNAP-051 | OK | — | 58 | 31 | c1f8db804d238ef8… | |
| REL-SNAP-052 | OK | — | 47 | 31 | c1f8db804d238ef8… | |
| REL-SNAP-053 | OK | — | 52 | 31 | c1f8db804d238ef8… | |
| REL-SNAP-054 | OK | — | 50 | 31 | c1f8db804d238ef8… | |
| REL-SNAP-055 | OK | — | 45 | 31 | c1f8db804d238ef8… | |
| REL-SNAP-056 | OK | — | 53 | 31 | c1f8db804d238ef8… | |
| REL-SNAP-057 | OK | — | 44 | 31 | c1f8db804d238ef8… | |
| REL-SNAP-058 | OK | — | 66 | 31 | c1f8db804d238ef8… | |
| REL-SNAP-059 | OK | — | 46 | 31 | c1f8db804d238ef8… |
Tool schema changed 2 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
agent-observatory-sensor.nolimit-observatory.workers.dev/s/ns-utc/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.sadri-dridi/ns-utc 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
- UTC nanosecond 9-digit band 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.