Brand and competitor trend volume over time, with growth signals. Free key at trendsmcp.ai
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 1 h ago | mcp initialize | ok | 200 | 156 ms | server trendsmcp 1.0.0 · protocol 2025-03-26 |
| 1 h ago | mcp initialize | ok | 200 | 155 ms | server trendsmcp 1.0.0 · protocol 2025-03-26 |
| 1 h ago | mcp initialize | ok | 200 | 162 ms | server trendsmcp 1.0.0 · protocol 2025-03-26 |
| 1 h ago | mcp initialize | ok | 200 | 160 ms | server trendsmcp 1.0.0 · protocol 2025-03-26 |
| 1 h ago | mcp initialize | failed | — | — | unsafe: DNS resolution failed |
| 1 h ago | mcp initialize | ok | 200 | 159 ms | server trendsmcp 1.0.0 · protocol 2025-03-26 |
| 1 h ago | mcp initialize | ok | 200 | 152 ms | server trendsmcp 1.0.0 · protocol 2025-03-26 |
| 1 h ago | mcp initialize | ok |
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.
| 200 |
| 156 ms |
| server trendsmcp 1.0.0 · protocol 2025-03-26 |
| 1 h ago | mcp initialize | ok | 200 | 164 ms | server trendsmcp 1.0.0 · protocol 2025-03-26 |
| 1 h ago | mcp initialize | ok | 200 | 160 ms | server trendsmcp 1.0.0 · protocol 2025-03-26 |