Llmprobe vs SigNoz MCP Server
A side-by-side look at the Llmprobe and SigNoz MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Llmprobe for monitoring work over a hosted endpoint; choose SigNoz MCP Server for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Llmprobe when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
probe_all, probe_model, list_providers.
Choose SigNoz MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
SIGNOZ_URL, SIGNOZ_API_KEY, LOG_LEVEL, TRANSPORT_MODE, MCP_SERVER_PORT, MCP_SERVER_HOST. - You want tools like
signoz_get_org_overview, signoz_list_metrics, signoz_query_metrics.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 53/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | SIGNOZ_URLSIGNOZ_API_KEY |
Tools & capabilities
Llmprobe tools 4
probe_allProbe all configured endpoints from `probes.yml`. Returns TTFT, latency, throughput, and health status for every model. Accepts an optional `config` parameter for a custom config path.probe_modelProbe a single model without a config file. Requires `provider`, `model`, and `api_key_env`. Supports optional `base_url` for OpenAI-compatible endpoints and optional `label` for display.list_providersList all providers and models in the config file with their thresholds. Use this to discover available models before probing.get_configReturn the full parsed configuration including defaults, providers, models, and thresholds.
SigNoz MCP Server tools 43
signoz_get_org_overviewGet the current status and overall posture of the SigNoz deployment, with typed projections plus `sourceStats` containing every reported stats fieldsignoz_list_metricsDiscover active metric names and catalog metadatasignoz_query_metricsQuery known metrics for values, trends, breakdowns, or formulassignoz_get_top_metricsReturn top 100 metrics ranked by ingested sample volume with pre-computed percentages for cost and volume analysissignoz_check_metric_usageGiven a list of metric names (up to 50 per call), return which dashboards and alerts reference each onesignoz_check_metric_cardinalityReturn label/attribute keys for a single metric with cardinality counts and sample values, sorted highest-cardinality firstsignoz_get_field_keysDiscover available field keys for metrics, traces, or logs
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Llmprobe
{
"mcpServers": {
"jwrede-llmprobe": {
"url": "https://api.groq.com/openai"
}
}
}
SigNoz MCP Server
{
"mcpServers": {
"signoz-mcp-server": {
"url": "https://your-public-mcp-url.com/mcp"
}
}
}
Frequently asked questions
Llmprobe is categorized under Monitoring and uses a remote HTTP/SSE transport. SigNoz MCP Server belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Llmprobe for monitoring work and SigNoz MCP Server for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Llmprobe is listed as free. Auth: api key required. SigNoz MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add jwrede-llmprobe and signoz-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Llmprobe has a quality signal of 53/100 (Good) with 2 views, 0 installs and 6 GitHub stars. SigNoz MCP Server has 57/100 (Good) with 1 views, 0 installs and 125 GitHub stars.
