api.bowmark.ai/mcp/registry
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 463 | 2 | 339d62f1f63fecca… | |
| REL-SNAP-003 | OK | — | 541 | 2 | 339d62f1f63fecca… | |
| REL-SNAP-004 | OK | — | 441 | 2 | 339d62f1f63fecca… | |
| REL-SNAP-005 | OK | — | 488 | 2 | 339d62f1f63fecca… | |
| REL-SNAP-006 | OK | — | 564 | 2 | 339d62f1f63fecca… | |
| REL-SNAP-007 | OK | — | 476 | 3 | b2b753c2c7de8e53… | |
| REL-SNAP-008 | OK | — | 400 | 3 | b2b753c2c7de8e53… | |
| REL-SNAP-009 | OK | — | 414 | 3 | b2b753c2c7de8e53… | |
| REL-SNAP-010 | OK | — | 804 | 3 | b2b753c2c7de8e53… | |
| REL-SNAP-011 | OK | — | 394 | 3 | b2b753c2c7de8e53… | |
| REL-SNAP-012 | OK | — | 806 | 3 | b2b753c2c7de8e53… | |
| REL-SNAP-013 | OK | — | 787 | 3 | b2b753c2c7de8e53… | |
| REL-SNAP-014 | OK | — | 407 | 3 | b2b753c2c7de8e53… | |
| REL-SNAP-015 | OK | — | 350 | 3 | b2b753c2c7de8e53… | |
| REL-SNAP-016 | OK | — | 392 | 3 | b2b753c2c7de8e53… |
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.bowmark.ai/mcp/registry— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- ai.bowmark/bowmark 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
- bowmark 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.