pixdress.de/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-004 | OK | — | 367 | 3 | db52d85c3345627f… | |
| REL-SNAP-005 | OK | — | 405 | 3 | db52d85c3345627f… | |
| REL-SNAP-006 | OK | — | 397 | 3 | db52d85c3345627f… | |
| REL-SNAP-007 | OK | — | 372 | 3 | db52d85c3345627f… | |
| REL-SNAP-008 | OK | — | 400 | 3 | db52d85c3345627f… | |
| REL-SNAP-009 | OK | — | 385 | 3 | db52d85c3345627f… | |
| REL-SNAP-010 | OK | — | 446 | 3 | db52d85c3345627f… | |
| REL-SNAP-011 | OK | — | 379 | 3 | db52d85c3345627f… | |
| REL-SNAP-012 | OK | — | 478 | 3 | db52d85c3345627f… | |
| REL-SNAP-013 | OK | — | 383 | 3 | db52d85c3345627f… | |
| REL-SNAP-014 | OK | — | 418 | 3 | db52d85c3345627f… | |
| REL-SNAP-015 | OK | — | 139 | 3 | db52d85c3345627f… | |
| REL-SNAP-016 | OK | — | 108 | 3 | db52d85c3345627f… | |
| REL-SNAP-017 | OK | — | 99 | 3 | db52d85c3345627f… | |
| REL-SNAP-018 | OK | — | 134 | 3 | db52d85c3345627f… | |
| REL-SNAP-019 | OK | — | 83 | 3 | db52d85c3345627f… | |
| REL-SNAP-020 | OK | — | 87 | 3 | db52d85c3345627f… | |
| REL-SNAP-021 | OK | — | 153 | 3 | db52d85c3345627f… | |
| REL-SNAP-022 | OK | — | 97 | 3 | db52d85c3345627f… | |
| REL-SNAP-023 | OK | — | 103 | 3 | db52d85c3345627f… | |
| REL-SNAP-024 | OK | — | 86 | 3 | db52d85c3345627f… | |
| REL-SNAP-025 | OK | — | 88 | 3 | db52d85c3345627f… | |
| REL-SNAP-026 | OK | — | 85 | 3 | db52d85c3345627f… |
Identity
- Record key
pixdress.de/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- de.pixdress/design 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
- pixdress 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.