mcp.tsuyoshikashiwazaki.jp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-004 | OK | — | 255 | 6 | 4c39507160964934… | |
| REL-SNAP-005 | OK | — | 246 | 6 | 4c39507160964934… | |
| REL-SNAP-006 | OK | — | 293 | 6 | 4c39507160964934… | |
| REL-SNAP-007 | OK | — | 275 | 6 | 4c39507160964934… | |
| REL-SNAP-008 | OK | — | 311 | 6 | 4c39507160964934… | |
| REL-SNAP-009 | OK | — | 295 | 6 | 4c39507160964934… | |
| REL-SNAP-010 | OK | — | 278 | 6 | 4c39507160964934… | |
| REL-SNAP-011 | OK | — | 258 | 6 | 4c39507160964934… | |
| REL-SNAP-012 | OK | — | 311 | 6 | 4c39507160964934… | |
| REL-SNAP-013 | OK | — | 289 | 6 | 4c39507160964934… | |
| REL-SNAP-014 | OK | — | 594 | 6 | 4c39507160964934… | |
| REL-SNAP-015 | OK | — | 541 | 6 | 4c39507160964934… | |
| REL-SNAP-016 | OK | — | 543 | 6 | 4c39507160964934… | |
| REL-SNAP-017 | OK | — | 872 | 6 | 4c39507160964934… | |
| REL-SNAP-018 | OK | — | 1049 | 6 | 4c39507160964934… | |
| REL-SNAP-019 | OK | — | 551 | 6 | 4c39507160964934… | |
| REL-SNAP-020 | OK | — | 546 | 6 | 4c39507160964934… | |
| REL-SNAP-021 | OK | — | 569 | 6 | 4c39507160964934… | |
| REL-SNAP-022 | OK | — | 547 | 6 | 4c39507160964934… | |
| REL-SNAP-023 | OK | — | 547 | 6 | 4c39507160964934… | |
| REL-SNAP-024 | OK | — | 560 | 6 | 4c39507160964934… | |
| REL-SNAP-025 | OK | — | 554 | 6 | 4c39507160964934… | |
| REL-SNAP-026 | OK | — | 576 | 6 | 4c39507160964934… |
Identity
- Record key
mcp.tsuyoshikashiwazaki.jp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- jp.tsuyoshikashiwazaki/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
- tsuyoshikashiwazaki-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.