mcp.gradientdecisions.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-008 | OK | — | 76 | 1 | 28a65a9bf82a4544… | |
| REL-SNAP-009 | OK | — | 63 | 1 | d5c9fc4ef9c6c2d6… | |
| REL-SNAP-010 | OK | — | 168 | 1 | d5c9fc4ef9c6c2d6… | |
| REL-SNAP-011 | OK | — | 71 | 1 | d5c9fc4ef9c6c2d6… | |
| REL-SNAP-012 | OK | — | 83 | 1 | d5c9fc4ef9c6c2d6… | |
| REL-SNAP-013 | OK | — | 59 | 1 | d5c9fc4ef9c6c2d6… | |
| REL-SNAP-014 | OK | — | 159 | 1 | d5c9fc4ef9c6c2d6… | |
| REL-SNAP-015 | OK | — | 358 | 1 | 1afa1901bfd43067… | |
| REL-SNAP-016 | OK | — | 350 | 1 | 1afa1901bfd43067… | |
| REL-SNAP-017 | OK | — | 207 | 1 | 1afa1901bfd43067… | |
| REL-SNAP-018 | OK | — | 228 | 1 | 1afa1901bfd43067… | |
| REL-SNAP-019 | OK | — | 205 | 1 | 1afa1901bfd43067… | |
| REL-SNAP-020 | OK | — | 349 | 1 | 1afa1901bfd43067… | |
| REL-SNAP-021 | OK | — | 400 | 1 | 1afa1901bfd43067… | |
| REL-SNAP-022 | OK | — | 308 | 1 | 1afa1901bfd43067… | |
| REL-SNAP-023 | OK | — | 392 | 1 | 1afa1901bfd43067… | |
| REL-SNAP-024 | OK | — | 354 | 1 | 1afa1901bfd43067… | |
| REL-SNAP-025 | OK | — | 272 | 1 | 1afa1901bfd43067… | |
| REL-SNAP-026 | OK | — | 183 | 1 | 1afa1901bfd43067… |
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
mcp.gradientdecisions.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.gradientdecisions/merchant-check 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
- merchant-check-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.