Koalr — Deployment Intelligence MCP Server Query your engineering data directly from Claude. Koalr's MCP server gives AI assistants read-only access to your GitHub-connected engineering metrics: deploy risk scores, DORA metrics, open PRs, team health, coverage, and incident data. What you can do: Score any pull request for deployment risk (0–100) before merging Get DORA metrics: deployment frequency, lead time, change failure rate, MTTR Find at-risk PRs, slow reviewers, and coverage gaps Query team and contributor performance Summarise org health, AI adoption, and well-being signals 20 read-only tools. No write access. Works with any GitHub-connected Koalr org. Requires a Koalr API key — get one at app.koalr.com → Settings → API Keys.

MCP readiness

B · 75/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 90.6/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (663 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	3.75/15	7/28 probes succeeded over 30 days (25%).
Tool declaration	10/10	Lists 20 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (663 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 35% of peers; This listing 75 · peer median 81
Latency: Faster than 19% of peers; This listing 643 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Uptime (30 days) −11.2 — Stay reachable in our daily probes.
Now: 7/28 probes succeeded over 30 days (25%).
Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/koalr/koalr-mcp/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/koalr/koalr-mcp/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://docs.koalr.com/docs/features/mcp-server

Listed at (smithery)

https://docs.koalr.com/docs/features/mcp-server