abfall-mcp.alpaycelik.dev/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-023 | OK | — | 43 | 5 | 34ecbd6611dc9e76… | |
| REL-SNAP-024 | OK | — | 178 | 5 | 34ecbd6611dc9e76… | |
| REL-SNAP-025 | OK | — | 23 | 5 | 34ecbd6611dc9e76… | |
| REL-SNAP-026 | OK | — | 46 | 5 | 34ecbd6611dc9e76… |
Identity
- Record key
abfall-mcp.alpaycelik.dev/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.AlpayC/mcp-abfall, io.github.AlpayC/abfall-mcp-server 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. — more than one registry name refers to this single endpoint. We record both rather than choosing between them; the observation covers the endpoint and cannot be attributed to one of them.
- Name reported by the server
- abfall-de 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.