https://docs.getmontecarlo.com/mcp ↗
Data + AI observability — monitor and troubleshoot production-grade agents and the context they use.
Monte Carlo is a remote MCP server published at docs.getmontecarlo.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 995 ms, a delay an agent will notice. It offers a narrow, focused set of 6 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
search — Description lacks specificity about documentation scopefetch — No clarification on ID source or content typesearch-endpoints — Could be confused with 'search' tool due to similar purposeRisk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/monte-carlo-monte-carlo)<a href="https://mcpmetrics.io/servers/monte-carlo-monte-carlo"><img src="https://mcpmetrics.io/badge/monte-carlo/monte-carlo/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 13:13:33 | Dual-era | 200 | 1572 | 200 | 1231 | 2026-07-28 |
| 2026-09-11 11:20:19 | Dual-era | 200 | 1012 | 200 | 995 | 2026-07-28 |
| 2026-09-11 09:28:19 | Dual-era | 200 | 1268 | 200 | 911 | 2026-07-28 |
| 2026-09-11 07:35:54 | Dual-era | 200 | 820 | 200 | 865 | 2026-07-28 |
| 2026-09-11 05:44:28 | Dual-era | 200 | 1000 | 200 | 536 | 2026-07-28 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 360 | 401 | 356 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.