api.hiddenjobs.dev/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-038 | OK | — | 386 | 3 | f86d91271f8af169… | |
| REL-SNAP-039 | OK | — | 360 | 3 | f86d91271f8af169… | |
| REL-SNAP-040 | OK | — | 345 | 3 | f86d91271f8af169… | |
| REL-SNAP-041 | OK | — | 301 | 3 | f86d91271f8af169… | |
| REL-SNAP-042 | OK | — | 322 | 3 | f86d91271f8af169… | |
| REL-SNAP-043 | OK | — | 353 | 3 | f86d91271f8af169… | |
| REL-SNAP-044 | OK | — | 471 | 3 | f86d91271f8af169… | |
| REL-SNAP-045 | OK | — | 387 | 3 | f86d91271f8af169… | |
| REL-SNAP-046 | OK | — | 334 | 3 | f86d91271f8af169… | |
| REL-SNAP-047 | OK | — | 300 | 3 | f86d91271f8af169… | |
| REL-SNAP-048 | OK | — | 291 | 3 | f86d91271f8af169… | |
| REL-SNAP-049 | OK | — | 316 | 3 | f86d91271f8af169… | |
| REL-SNAP-050 | OK | — | 308 | 3 | f86d91271f8af169… | |
| REL-SNAP-051 | OK | — | 381 | 3 | f86d91271f8af169… | |
| REL-SNAP-052 | OK | — | 302 | 3 | f86d91271f8af169… | |
| REL-SNAP-053 | OK | — | 332 | 3 | f86d91271f8af169… | |
| REL-SNAP-054 | OK | — | 321 | 3 | f86d91271f8af169… | |
| REL-SNAP-055 | OK | — | 412 | 3 | f86d91271f8af169… | |
| REL-SNAP-056 | OK | — | 379 | 3 | f86d91271f8af169… | |
| REL-SNAP-057 | OK | — | 343 | 3 | f86d91271f8af169… | |
| REL-SNAP-058 | OK | — | 352 | 3 | f86d91271f8af169… | |
| REL-SNAP-059 | OK | — | 248 | 3 | f86d91271f8af169… |
Identity
- Record key
api.hiddenjobs.dev/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.hiddenjobs/job-search-mcp 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
- hidden-jobs-mcp 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.