nempulse.com.au/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 350 | 8 | 7f6cf3d93630607e… | |
| REL-SNAP-010 | OK | — | 369 | 8 | eb6e76ba6a3a9d11… | |
| REL-SNAP-011 | OK | — | 352 | 8 | eb6e76ba6a3a9d11… | |
| REL-SNAP-012 | OK | — | 391 | 8 | eb6e76ba6a3a9d11… | |
| REL-SNAP-013 | OK | — | 567 | 8 | eb6e76ba6a3a9d11… | |
| REL-SNAP-014 | OK | — | 345 | 8 | eb6e76ba6a3a9d11… | |
| REL-SNAP-015 | OK | — | 636 | 8 | eb6e76ba6a3a9d11… | |
| REL-SNAP-016 | OK | — | 1500 | 8 | eb6e76ba6a3a9d11… | |
| REL-SNAP-017 | OK | — | 629 | 8 | eb6e76ba6a3a9d11… | |
| REL-SNAP-018 | OK | — | 647 | 8 | eb6e76ba6a3a9d11… | |
| REL-SNAP-019 | OK | — | 1489 | 8 | eb6e76ba6a3a9d11… | |
| REL-SNAP-020 | OK | — | 640 | 8 | a9f8c221cae574d8… | |
| REL-SNAP-021 | OK | — | 662 | 8 | a9f8c221cae574d8… | |
| REL-SNAP-022 | OK | — | 641 | 8 | a9f8c221cae574d8… | |
| REL-SNAP-023 | OK | — | 1511 | 8 | a9f8c221cae574d8… | |
| REL-SNAP-024 | OK | — | 651 | 8 | a9f8c221cae574d8… | |
| REL-SNAP-025 | OK | — | 683 | 8 | a9f8c221cae574d8… | |
| REL-SNAP-026 | OK | — | 666 | 8 | a9f8c221cae574d8… |
Tool schema changed 2 times across this history — the fingerprint differs between consecutive observations. A change can occur while the tool count stays identical, which is why the fingerprint is recorded alongside the count.
Identity
- Record key
nempulse.com.au/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- au.com.nempulse/nempulse 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
- NEMPulse 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.