agents.getardaro.com/mcp/utilities
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-042 | OK | — | 214 | 0 | 4f53cda18c2baa0c… | |
| REL-SNAP-043 | HTTP_4XX | http_406 | — | — | — | |
| REL-SNAP-044 | OK | — | 209 | 0 | 4f53cda18c2baa0c… | |
| REL-SNAP-045 | OK | — | 276 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-046 | OK | — | 217 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-047 | OK | — | 237 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-048 | OK | — | 211 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-049 | OK | — | 329 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-050 | OK | — | 219 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-051 | OK | — | 207 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-052 | OK | — | 256 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-053 | OK | — | 218 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-054 | OK | — | 219 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-055 | OK | — | 335 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-056 | OK | — | 212 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-057 | OK | — | 207 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-058 | OK | — | 211 | 6 | 8ae8c73487883b6c… | |
| REL-SNAP-059 | OK | — | 215 | 6 | 8ae8c73487883b6c… |
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
agents.getardaro.com/mcp/utilities— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.ashevilleislove/ardaro-agent-utilities 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
- ardaro-agent-utilities 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.