LLM Observability Orchestration MCP server
LLM Observability & Orchestration Agent
C62/100grade C
Adoption
New
Little public usage data yet
Reviews
Write oneNobody has reviewed LLM Observability Orchestration yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
LLM Observability Orchestration tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
1 low
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 278ms; handshake note: Server's protocol version is not supported: 2026-07-2820/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityopen endpoint, read-only tools10/15
- Maintenanceno repository listed3/15
- Maintainer identityverified namespace with website, no repo4/10
Findings (1)
- lowNo source repository listed
maint.no-repo
Overall 62/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add --transport http llm-observability-orchestration https://llm-observability-orchestration.getvda.ai/mcp
LLM Observability Orchestration: common questions
- Is LLM Observability Orchestration MCP server safe?
- With care: it is graded C, so read the findings first (62/100). Read the LLM Observability Orchestration safety report
- How do I install LLM Observability Orchestration?
- It runs remotely at llm-observability-orchestration.getvda.ai. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does LLM Observability Orchestration need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is LLM Observability Orchestration maintained?
- The latest release is v1.0.0.
- Is LLM Observability Orchestration up?
- 100% of our last 6 checks got an answer. We check remote servers about four times a day.