Agent47 vs Llmprobe
A side-by-side look at the Agent47 and Llmprobe MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent47 for monitoring work as a local process; choose Llmprobe 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 Agent47 when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 51/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
Agent47 tools
No tool names declared yet. Check the project README from the listing page.
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.
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.
Agent47
{
"mcpServers": {
"bmdhodl-agent47": {
"command": "uvx",
"args": [
"agentguard47"
]
}
}
}
Llmprobe
{
"mcpServers": {
"jwrede-llmprobe": {
"url": "https://api.groq.com/openai"
}
}
}
Frequently asked questions
Agent47 is categorized under Monitoring and uses a local stdio subprocess. Llmprobe belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Agent47 for monitoring work and Llmprobe 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.
Agent47 is listed as free. Auth: no auth required. Llmprobe is listed as free. Auth: api key required. 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 bmdhodl-agent47 and jwrede-llmprobe as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent47 has a quality signal of 51/100 (Good) with 3 views, 0 installs and 4 GitHub stars. Llmprobe has 53/100 (Good) with 2 views, 0 installs and 6 GitHub stars.
