mcp.myplate.food/sse
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 1027 | — | — | |
| REL-SNAP-003 | OK | — | 988 | — | — | |
| REL-SNAP-004 | OK | — | 965 | — | — | |
| REL-SNAP-005 | OK | — | 956 | — | — | |
| REL-SNAP-006 | OK | — | 1401 | — | — | |
| REL-SNAP-007 | OK | — | 1149 | — | — | |
| REL-SNAP-008 | OK | — | 1191 | — | — | |
| REL-SNAP-009 | OK | — | 1040 | — | — | |
| REL-SNAP-010 | OK | — | 1078 | — | — | |
| REL-SNAP-011 | OK | — | 967 | — | — | |
| REL-SNAP-012 | OK | — | 1020 | — | — | |
| REL-SNAP-013 | OK | — | 1232 | — | — | |
| REL-SNAP-014 | OK | — | 1222 | — | — | |
| REL-SNAP-015 | OK | — | 869 | — | — | |
| REL-SNAP-016 | OK | — | 862 | — | — | |
| REL-SNAP-017 | OK | — | 786 | — | — | |
| REL-SNAP-018 | OK | — | 755 | — | — | |
| REL-SNAP-019 | OK | — | 863 | — | — | |
| REL-SNAP-020 | OK | — | 691 | — | — | |
| REL-SNAP-021 | OK | — | 1233 | — | — | |
| REL-SNAP-022 | OK | — | 745 | — | — | |
| REL-SNAP-023 | OK | — | 918 | — | — | |
| REL-SNAP-024 | OK | — | 1003 | — | — | |
| REL-SNAP-025 | OK | — | 1064 | — | — | |
| REL-SNAP-026 | OK | — | 873 | — | — |
Identity
- Record key
mcp.myplate.food/sse— the normalised endpoint observed. See the methodology for the rule.- Transport
- sse
- Registry names (not anchored)
- food.myplate/nutrition 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
- myplate-food-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.