Answers modded Minecraft questions from real lab data, for Fabric, NeoForge and Forge. - **diagnose_crash**: paste a crash report or `latest.log`; get the mod most likely behind it, the evidence, how sure, and how to fix it. It also checks the rest of the pack against the lab. The text is read and dropped, never stored. - **search_mods**: a mod's id from its name. - **get_mod_info**: what a mod is, from its Modrinth page, next to what the lab saw it do. - **find_mod_download**: the file to install for your Minecraft version and loader, with the mods it needs; lab-verified ports when the author has no build yet. - **get_mod_runs**: the Minecraft versions where a mod ran or crashed in the lab. - **check_mod_pair** / **check_mod_list**: whether two mods, or a whole pack, ran together, clashed, or were never tested ("untested" is not a conflict). No API key. Lab data is CC BY 4.0: credit "Modkeel lab data (modkeel.com)". Docs: https://modkeel.com/mcp

MCP readiness

B · 87/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	24/25	Endpoint answers the MCP initialize handshake (3302 ms); slow response -1.
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 7 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: Slow (3302 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 88% of peers; This listing 87 · peer median 81
Latency: Faster than 12% of peers; This listing 835 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.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-10-03 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/modkeel/modkeel/mcp

JSON-RPC initialize probe

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

Homepage

https://modkeel.com

Listed at (smithery)

https://modkeel.com