api.dreamfare.app/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-030 | OK | — | 496 | 38 | 4f3afa5799c9daaf… | |
| REL-SNAP-031 | OK | — | 623 | — | — | |
| REL-SNAP-032 | OK | — | 694 | — | — | |
| REL-SNAP-033 | OK | — | 611 | — | — | |
| REL-SNAP-034 | OK | — | 378 | — | — | |
| REL-SNAP-035 | OK | — | 428 | — | — | |
| REL-SNAP-036 | OK | — | 447 | — | — | |
| REL-SNAP-037 | OK | — | 368 | — | — | |
| REL-SNAP-038 | OK | — | 575 | — | — | |
| REL-SNAP-039 | OK | — | 436 | — | — | |
| REL-SNAP-040 | OK | — | 469 | — | — | |
| REL-SNAP-041 | OK | — | 410 | — | — | |
| REL-SNAP-042 | OK | — | 436 | — | — | |
| REL-SNAP-043 | OK | — | 443 | — | — | |
| REL-SNAP-044 | OK | — | 405 | — | — | |
| REL-SNAP-045 | OK | — | 653 | — | — | |
| REL-SNAP-046 | OK | — | 648 | — | — | |
| REL-SNAP-047 | OK | — | 512 | — | — | |
| REL-SNAP-048 | OK | — | 494 | — | — | |
| REL-SNAP-049 | OK | — | 442 | — | — | |
| REL-SNAP-050 | OK | — | 405 | — | — | |
| REL-SNAP-051 | OK | — | 548 | — | — | |
| REL-SNAP-052 | OK | — | 363 | — | — | |
| REL-SNAP-053 | OK | — | 429 | — | — | |
| REL-SNAP-054 | OK | — | 435 | — | — | |
| REL-SNAP-055 | OK | — | 411 | — | — | |
| REL-SNAP-056 | OK | — | 448 | — | — | |
| REL-SNAP-057 | OK | — | 433 | — | — | |
| REL-SNAP-058 | OK | — | 643 | — | — | |
| REL-SNAP-059 | OK | — | 433 | — | — |
Identity
- Record key
api.dreamfare.app/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- app.dreamfare/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
- dreamfare 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.