www.hoodgrow.com/api/mcp
Last observed:— recorded as HTTP_5XX (http_503)
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 1069 | 10 | c191f6e15d2c5ab3… | |
| REL-SNAP-010 | OK | — | 710 | 10 | c191f6e15d2c5ab3… | |
| REL-SNAP-011 | OK | — | 610 | 10 | c191f6e15d2c5ab3… | |
| REL-SNAP-012 | OK | — | 735 | 10 | c191f6e15d2c5ab3… | |
| REL-SNAP-013 | OK | — | 676 | 10 | c191f6e15d2c5ab3… | |
| REL-SNAP-014 | OK | — | 641 | 10 | c191f6e15d2c5ab3… | |
| REL-SNAP-015 | OK | — | 283 | 10 | c191f6e15d2c5ab3… | |
| REL-SNAP-016 | OK | — | 351 | 10 | c191f6e15d2c5ab3… | |
| REL-SNAP-017 | OK | — | 263 | 10 | c191f6e15d2c5ab3… | |
| REL-SNAP-018 | OK | — | 442 | 10 | c191f6e15d2c5ab3… | |
| REL-SNAP-019 | OK | — | 257 | 11 | 9a126b56a30009fe… | |
| REL-SNAP-020 | OK | — | 412 | 11 | 9a126b56a30009fe… | |
| REL-SNAP-021 | OK | — | 397 | 11 | 9a126b56a30009fe… | |
| REL-SNAP-022 | OK | — | 294 | 11 | 9a126b56a30009fe… | |
| REL-SNAP-023 | OK | — | 309 | 11 | 9a126b56a30009fe… | |
| REL-SNAP-024 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-025 | HTTP_5XX | http_503 | — | — | — | |
| REL-SNAP-026 | HTTP_5XX | http_503 | — | — | — |
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
www.hoodgrow.com/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.MeMikko/hoodgrow-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
- Not reported. 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.