api.budgetary.tools/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 47 | 1 | 7c411948f6f463da… | |
| REL-SNAP-003 | OK | — | 38 | 1 | 7c411948f6f463da… | |
| REL-SNAP-004 | OK | — | 79 | 1 | 7c411948f6f463da… | |
| REL-SNAP-005 | OK | — | 82 | 1 | 7c411948f6f463da… | |
| REL-SNAP-006 | OK | — | 96 | 1 | 7c411948f6f463da… |
Identity
- Record key
api.budgetary.tools/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- Not held in the archive for this endpoint. Registry names are held only from REL-SNAP-013 onward, and this endpoint appears in no snapshot from then on — so this is a gap in our data, not a property of the endpoint. The name was read during the sweep but never written into a published snapshot, and what a registry said on a past date cannot be recovered afterwards. It is fixed forward rather than backfilled — seemethodology, which states why an empty value does not mean the same thing either side of that boundary.
- Name reported by the server
- budgetary 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.