hackerbob.ai/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-020 | OK | — | 52 | 3 | 63d433847ac24f30… | |
| REL-SNAP-021 | OK | — | 71 | 3 | 63d433847ac24f30… | |
| REL-SNAP-022 | OK | — | 69 | 3 | 63d433847ac24f30… | |
| REL-SNAP-023 | OK | — | 58 | 3 | 63d433847ac24f30… | |
| REL-SNAP-024 | OK | — | 62 | 3 | 63d433847ac24f30… | |
| REL-SNAP-025 | OK | — | 50 | 3 | 63d433847ac24f30… | |
| REL-SNAP-026 | OK | — | 54 | 3 | 63d433847ac24f30… |
Identity
- Record key
hackerbob.ai/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.bobnetsec/hacker-bob-public-records 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
- hacker-bob-public-records 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.