DeployDoctor

https://server.smithery.ai/fkornelind/deploydoctor/mcp

● healthy

Triage Next.js/Vercel build errors and scan public GitHub repos for deploy-breaking mistakes. **What it does** - Paste a sanitized build log: get the matched lines, likely cause, official docs and steps to verify the fix (Module not found, npm ERESOLVE, React hydration mismatch). - Give it a public GitHub repo: finds case-sensitive imports that only work on macOS, undeclared packages, missing env vars, server/client boundary mistakes and Prisma without `prisma generate`. **Good to know** - Remote server, no API key, no account. - Read-only static analysis. Nothing is cloned, installed or executed. - Also available as a free GitHub Action for public repos: https://github.com/marketplace/actions/deploydoctor

Transport

streamable-http

Auth

smithery_api_key

Cost

—

Protocol revision

2025-11-25

negotiated, not declared

MCP readiness

B · 84/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 C+, 70.0/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	22/25	Endpoint answers the MCP initialize handshake (8143 ms); near timeout response -3.
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)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 5 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: Near timeout (8143 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,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 75% of peers; This listing 84 · peer median 81
Latency: Faster than 5% of peers; This listing 1,714 ms · peer median 326 ms

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

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.
Live MCP endpoint −3 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers the MCP initialize handshake (8143 ms); near timeout response -3.
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-10-09 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/fkornelind/deploydoctor/mcp

JSON-RPC initialize probe

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

Homepage

https://deploydoctor.nyttolabs.com/ai-plugin

Listed at (smithery)

https://deploydoctor.nyttolabs.com/ai-plugin