Live market intelligence
This board turns pricing, proof, freshness, trust rollouts, and cross-registry corroboration into one daily-use market surface. Each signal can open into an operator brief via Explain this change.
The most important live changes in the current lens, sorted across severity, recency, and market impact.
Source quality pressure
PulseMCP
PulseMCP is leaning heavily toward protected-but-live inventory: 11 protected rows out of 11 visible. That is useful corroboration, but it also means less immediately executable supply.
Source quality pressure
Remote MCP
Remote MCP is leaning heavily toward protected-but-live inventory: 8 protected rows out of 8 visible. That is useful corroboration, but it also means less immediately executable supply.
Source quality pressure
Smithery
Smithery is leaning heavily toward protected-but-live inventory: 14 protected rows out of 14 visible. That is useful corroboration, but it also means less immediately executable supply.
Source quality pressure
ToolHive Registry
ToolHive Registry is leaning heavily toward protected-but-live inventory: 2 protected rows out of 2 visible. That is useful corroboration, but it also means less immediately executable supply.
Verification failure
Semgrep (Remote) · POST /mcp
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Verification failure
GitLab (Remote) · POST /api/v4/mcp
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Verification failure
Brave Search · POST /
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Verification failure
Zapier · POST /api/mcp/mcp
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Expansion quality is tracked source by source here: accepted versus gated supply, plus the current visible, verified, protected, and broken public footprint.
Official MCP Registry
15 visible · 0 verified · 3 protected · 0 broken.
ToolHive Registry
2 visible · 0 verified · 2 protected · 0 broken.
Smithery
14 visible · 0 verified · 14 protected · 0 broken.
PulseMCP
11 visible · 0 verified · 11 protected · 0 broken.
Remote MCP
8 visible · 0 verified · 8 protected · 0 broken.
Remote MCP Servers
0 visible · 0 verified · 0 protected · 0 broken.
These are the source families that are currently getting gated down hard or leaning too far toward protected or broken public inventory.
Source quality pressure
PulseMCP
PulseMCP is leaning heavily toward protected-but-live inventory: 11 protected rows out of 11 visible. That is useful corroboration, but it also means less immediately executable supply.
Source quality pressure
Remote MCP
Remote MCP is leaning heavily toward protected-but-live inventory: 8 protected rows out of 8 visible. That is useful corroboration, but it also means less immediately executable supply.
Source quality pressure
Smithery
Smithery is leaning heavily toward protected-but-live inventory: 14 protected rows out of 14 visible. That is useful corroboration, but it also means less immediately executable supply.
Source quality pressure
ToolHive Registry
ToolHive Registry is leaning heavily toward protected-but-live inventory: 2 protected rows out of 2 visible. That is useful corroboration, but it also means less immediately executable supply.
Normalized price cuts observed in live challenge history, not just docs edits.
Runtime, delivery, and proof regressions that now show up as open verification incidents.
Verification failure
Semgrep (Remote) · POST /mcp
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Verification failure
GitLab (Remote) · POST /api/v4/mcp
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Verification failure
Brave Search · POST /
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Verification failure
Zapier · POST /api/mcp/mcp
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Verification failure
Telnyx · POST /v2/mcp
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Verification failure
Short.io · POST /mcp
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Verification failure
SearchAPI · POST /mcp
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Verification failure
Polar Signals · POST /api/mcp
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Surfaces where unpaid proof, paid proof, or workflow evidence has gone stale enough to matter.
Services whose advisory, shadow, or enforce trust gates are suddenly touching more traffic.
Newly added endpoints that have already picked up fresh public proof in the last 7 days.
Listings that just gained another registry view and therefore moved up in confidence.
Health-score changes over the last 7 days, broken down by protocol, category, and source quality.