# Modkeel (remote · api.modkeel.com)

Modded Minecraft: which mod crashed, where to get a mod for your version, which mods work together.

- Trust score: 76/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.modkeel.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-modkeel-modkeel/api.md), [page](https://verifymcp.io/servers/com-modkeel-modkeel/api)

## Channel facts

- Endpoint: `https://api.modkeel.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.11.4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2463 tokens (~351/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Modkeel MCP server?

Modkeel is a hosted endpoint at https://api.modkeel.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-modkeel-modkeel 'https://api.modkeel.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-modkeel-modkeel": {
      "url": "https://api.modkeel.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-modkeel-modkeel": {
      "type": "http",
      "url": "https://api.modkeel.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-modkeel-modkeel]
url = "https://api.modkeel.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-modkeel-modkeel": {
      "type": "remote",
      "url": "https://api.modkeel.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-modkeel-modkeel --url 'https://api.modkeel.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-modkeel-modkeel:
    url: "https://api.modkeel.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-modkeel-modkeel": {
      "Transport": "http",
      "Url": "https://api.modkeel.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-modkeel-modkeel -t streamable-http -u 'https://api.modkeel.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-modkeel-modkeel": {
      "type": "http",
      "url": "https://api.modkeel.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30.

### 2026-10-30 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23.

### 2026-10-28 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17.

### 2026-10-26 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10.

### 2026-10-24 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.

### 2026-10-16 (score 71, 0)

- [functional] Server version: 1.11.3 → 1.11.4

### 2026-10-15 (score 71, +4)

- [security improvement] HTTPS: unverified → pass

### 2026-10-14 (score 67, 0)

- [functional] Server version: 1.11.2 → 1.11.3

## MCP tools (7)

### `diagnose_crash` (~402 tokens)

Which mod crashed Minecraft

Find the mod most likely behind a modded Minecraft crash (Fabric, NeoForge, Forge). Use it whenever the user shares a crash report or latest.log or says the game will not start. It is the only tool that reads logs, and it adds what the file does not hold: it checks every installed mod against the Modkeel lab (pairs in the pack that clashed, jars that crashed on that Minecraft version), says how many other players hit the same crash and which fix worked for them (when 10+ did), counts lab runs of each suspect, and ranks suspects by evidence (mixin, trace, missing class) with a confidence level (NONE when nothing points at a mod). It also returns a fix guide and, when the log names the Minecraft version and loader, the build to install for the suspect and for every installed mod the lab saw crash on that version, so no follow-up call is needed. Pass the whole file as text, unedited: trimming it loses the mod list; or, when the user gave a link to a paste (mclo.gs, pastebin.com, paste.ee, gist.github.com, modkeel.com), pass url instead and Modkeel fetches it. Text with no crash in it comes back as an error to fix and retry. Up to 4 MB; read and dropped, never stored.

Input parameters:

- `text` (string): The full crash report (crash-reports/crash-*.txt, from '---- Minecraft Crash Report ----') or logs/latest.log, unedited. Up to 4 MB. Give text or url.
- `url` (string): A link to the crash report or log on a paste site (mclo.gs, pastebin.com, paste.ee, gist.github.com, modkeel.com), e.g. https://mclo.gs/abc123. Modkeel downloads the raw text itself. Give text or url.

Output parameters:

- `confidence` (string): How sure the first suspect is the cause.
- `description` (string)
- `error` (string): The root exception and its message.
- `guide` (string): How to fix this kind of crash.
- `in_game` (string): The same diagnosis inside the game, for players who crash often.
- `kind` (string)
- `loader` (string|null)
- `mc` (string|null)
- `next_step` (string|null): What to replace and with what, one sentence per mod; tell the user all of it. Null when the version or loader is unknown.
- `pack` (object): The installed mods checked against the lab, beyond this crash.
- `players` (object|null): What other players' reports of this same crash say (Modkeel Companion reports, monthly snapshot); null below 10 players.
- `replace` (array|null): The build to install for the first suspect, then for every installed mod whose jar crashed in the lab on this version (the next crash), as find_mod_download gives it; null when the version or loader…
- `signature` (string): Stable id of this crash shape.
- `source` (string)
- `suspects` (array): Most likely first; empty when no mod is implicated.

### `search_mods` (~333 tokens)

Find a mod's id in the Modkeel lab

Turn a mod's display name or part of its id into the exact mod id the other lab tools take, and see which mods the Modkeel lab has data on. Use it first when you only have a name ("Entity Culling", "Sodium") or are unsure of the id; skip it when you already have the id. To download a mod, call find_mod_download with its name instead: it finds the mod itself. Matching ignores case, spaces and punctuation; best match first, then the mods with more lab data. An empty query lists every mod the lab tested. Returns each mod's id, the Minecraft versions it was tested on and how many runs and pairs it has, plus the total number of matches. No match means the lab has no data on that mod, not that it is broken (get_mod_info still finds it on Modrinth by slug). mc keeps only mods with a run on that exact version; limit caps the list, and total says how many matched.

Input parameters:

- `limit` (integer): How many mods to return, 1 to 100. Default 25.
- `mc` (string): Minecraft version to narrow the answer to, e.g. 1.21.1, 1.20.1 or 26.2. Omit it to get every version the lab ran; with it, only runs on exactly that version count.
- `query` (string): Mod name or part of its id, e.g. "Entity Culling", "sod" or "create". Empty or omitted: list every mod the lab tested.

Output parameters:

- `data` (object): Snapshot date and license of the lab data; attribute when quoting.
- `mc` (string|null)
- `mods` (array): Best match first.
- `query` (string)
- `total` (integer): Matches before the limit.

### `get_mod_info` (~279 tokens)

What a mod is, from its catalog page

What one Minecraft mod is and where to get it: its Modrinth page (title, summary, categories, loaders, the Minecraft releases its author lists, client/server side, licence, downloads, source and issue links) next to a short Modkeel lab record (tested versions, run and pair counts). Use it for "what does this mod do?", "is it client-only?", "where do I download it?" or to link a suspect from diagnose_crash. The versions here are what the author declares; for what the lab saw run or crash, use get_mod_runs, and for two mods together, check_mod_pair. Takes a lab mod id or a Modrinth slug; from a name, call search_mods first. The project is matched by the SHA-1 of a jar the lab ran (source: jar_hash, exact), else by slug (source: slug); a mod on neither returns found: false, not an error. Asks Modrinth live on each call (nothing cached here), so it can fail when Modrinth is down: retry later.

Input parameters:

- `mod_id` (string, required): Lab mod id (e.g. fabric_api, ferritecore) or Modrinth slug (e.g. fabric-api, sodium-extra), lowercase. Unsure? Call search_mods first.

Output parameters:

- `data` (object): Snapshot date and license of the lab data; attribute when quoting.
- `found` (boolean): False: on neither Modrinth nor in lab jars.
- `lab` (object)
- `mod` (string)
- `modrinth` (object|null)
- `other_projects` (array): Other Modrinth project ids for this mod id: a fork the lab also ran, or the project whose slug is this id when the lab ran a port (fabric_api on NeoForge).
- `source` (string|null): How the Modrinth project was matched.

### `find_mod_download` (~406 tokens)

Where to download a mod for a Minecraft version

The exact file to install for one mod on one Minecraft version and loader, with its download link. Use it for "where do I get X for 26.2 Fabric?", after diagnose_crash names a mod that needs another build, or when updating a pack to a new version. Checks, best first: the author's own build on Modrinth (status official: file, required mods, and lab runs of that exact file), a community port the Modkeel lab verified in one of its modpacks (port), the author's file for an earlier version that the lab ran on this one and saw start (older_build), a port the lab built from its public source and saw start but does not host (build_from_source: the repo, branch and how to build it), the loaders the author does build for that version (other_loader), else none; when that older file crashed in the lab instead, older_build says so and next_step warns against it. next_step says what the user can do in each case. For what the mod is, use get_mod_info; for whether it ran in the lab, get_mod_runs. Takes the mod's name as the user wrote it ("YUNG's Better Mineshafts"), a lab mod id or a Modrinth slug: no search_mods call needed first. Asks Modrinth live (two to five calls, nothing cached), so it can fail when Modrinth is down: retry.

Input parameters:

- `loader` (string, required): Mod loader of the instance: fabric, neoforge, forge or quilt.
- `mc` (string, required): Minecraft version to install on, exactly, e.g. 1.21.1 or 26.2.
- `mod_id` (string, required): The mod's name as the user wrote it (e.g. Entity Culling), a lab mod id (e.g. sodium, fabric_api) or a Modrinth slug (e.g. fabric-api).

Output parameters:

- `data` (object): Snapshot date and license of the lab data; attribute when quoting.
- `declared_versions` (array): Newest Minecraft releases the author lists.
- `loader` (string)
- `mc` (string)
- `mod` (string)
- `next_step` (string): What the user can do now, one sentence.
- `official` (object|null): The author's build for this version and loader (a release when any).
- `older_build` (object|null): The author's file for an earlier version, as the Modkeel lab ran it on this one (only when there is no official build or port): ran (started on env) or crashed (detail says how).
- `other_loaders` (array): Loaders the author builds this version for.
- `ports` (array): Ports verified by the lab; only when there is no official build.
- `project` (object|null): The mod's Modrinth project; null when none matches.
- `source_build` (object|null): A port the Modkeel lab built from this GitHub repo and branch and saw start on env; Modkeel does not host its jar, so the player builds it (next_step says how). Only when nothing published fits.
- `status` (string)

### `get_mod_runs` (~276 tokens)

What the Modkeel lab saw a mod do

Everything the Modkeel lab saw one Minecraft mod do: each Minecraft version where it ran on a server or a client, or crashed, and every mod it ran with or clashed with. Use it for "does this mod work on 1.21.1?", "which versions was it tested on?" or to check a suspect from diagnose_crash. For one specific pair of mods, check_mod_pair gives a direct verdict; for what the mod is and where to get it, get_mod_info. Takes a mod id; from a name, call search_mods first. A mod the lab never ran returns tested: false with empty lists, not an error. Returns every matching row, unpaginated: a few dozen at most per mod.

Input parameters:

- `mc` (string): Minecraft version to narrow the answer to, e.g. 1.21.1, 1.20.1 or 26.2. Omit it to get every version the lab ran; with it, only runs on exactly that version count.
- `mod_id` (string, required): Lowercase mod id as the loader knows it (the Modrinth/Fabric/NeoForge id, e.g. sodium, create, entityculling), not the display name. Unsure of the id? Call search_mods first.

Output parameters:

- `data` (object): Snapshot date and license of the lab data; attribute when quoting.
- `mc` (string|null)
- `mod` (string)
- `pairs` (array): Mods it shared a run with; env: server, client or clash.
- `runs` (array): One per jar the lab ran; env: server, client or crashes.
- `tested` (boolean): False: the lab never ran this mod.

### `check_mod_pair` (~266 tokens)

Do two mods work together

Whether two Minecraft mods ran together in the Modkeel lab, clashed, or were never tested together. Use it for "can I use X with Y?" or to check two suspects from diagnose_crash; for one mod's whole record, use get_mod_runs. Takes two mod ids in any order (from names, call search_mods first). Unknown ids are not an error: the verdict is untested, meaning no lab run, never a known conflict. With mc, only runs on that version count. clash wins if any run clashed. Returns the verdict and the runs behind it.

Input parameters:

- `mc` (string): Minecraft version to narrow the answer to, e.g. 1.21.1, 1.20.1 or 26.2. Omit it to get every version the lab ran; with it, only runs on exactly that version count.
- `mod_a` (string, required): First mod. Lowercase mod id as the loader knows it (the Modrinth/Fabric/NeoForge id, e.g. sodium, create, entityculling), not the display name. Unsure of the id? Call search_mods first.
- `mod_b` (string, required): Second mod, same format, e.g. iris.

Output parameters:

- `data` (object): Snapshot date and license of the lab data; attribute when quoting.
- `mc` (string|null)
- `mods` (array)
- `runs` (array): The runs behind the verdict; env: server, client or clash.
- `verdict` (string): untested: no lab run, not a known conflict.

### `check_mod_list` (~280 tokens)

Do these mods work together

A whole mod list or modpack checked against the Modkeel lab at once: every pair in it that clashed, the mods whose jar crashed, the pairs that ran together, and the mods the lab has no data on. Use it for "will these mods work together?" or before updating a pack; for two mods, check_mod_pair is enough. Takes up to 300 mod ids (from names, search_mods first; unknown ids just land in untested_mods). With mc, only runs on that version count, and each crashed mod also gets the author's current build for it, since the crash is about the exact file the lab ran. verdict is problems_found when anything clashed or crashed, else no_known_problem, which is not a guarantee: pairs.tested out of pairs.total says how much of the list the lab covered.

Input parameters:

- `mc` (string): Minecraft version to narrow the answer to, e.g. 1.21.1, 1.20.1 or 26.2. Omit it to get every version the lab ran; with it, only runs on exactly that version count.
- `mod_ids` (array, required): Lowercase mod ids as the loader knows them, e.g. ["sodium", "iris", "create"]. The ids of a mods folder's jars work.

Output parameters:

- `clashes` (array): Pairs in the list that clashed in a lab run.
- `crashed` (array): Mods whose jar crashed in a lab run: that exact file (runs[].file).
- `data` (object): Snapshot date and license of the lab data; attribute when quoting.
- `mc` (string|null)
- `mods` (integer): Distinct ids checked.
- `next_step` (string|null): With mc and crashed mods: what to install or leave out, for the player.
- `pairs` (object)
- `ran_together` (array): Pairs in the list seen working together.
- `untested_mods` (array): No lab data: unknown, not broken.
- `verdict` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-modkeel-modkeel/api#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 74
- 2026-10-28: 74
- 2026-10-27: 73
- 2026-10-26: 73
- 2026-10-25: 72
- 2026-10-24: 72
- 2026-10-23: 71
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 71
- 2026-10-19: 71
- 2026-10-18: 71
- 2026-10-17: 71
- 2026-10-16: 71
- 2026-10-15: 71
- 2026-10-14: 67
- 2026-10-13: 67
- 2026-10-12: 67
- 2026-10-11: 67
- 2026-10-07: 70
- 2026-10-06: 69
- 2026-10-04: 68
- 2026-10-03: 68

## Common questions

### What is the Modkeel MCP server?

Modkeel is an MCP server listed in the public MCP registry as com.modkeel/modkeel. Modded Minecraft: which mod crashed, where to get a mod for your version, which mods work together. This page covers its hosted endpoint (https://api.modkeel.com/mcp).

### Is the Modkeel MCP server safe to use?

Modkeel scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Modkeel MCP server expose?

Modkeel exposes 7 tools: diagnose_crash, search_mods, get_mod_info, find_mod_download, get_mod_runs, and 2 more. Their descriptions and schemas cost roughly 2,242 tokens of context every time the server is loaded.

### Does the Modkeel MCP server require authentication?

No. We connected to Modkeel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Modkeel MCP server still maintained?

Modkeel is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Modkeel MCP server?

VerifyMCP ran 13 checks on Modkeel, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.modkeel.com/mcp
- Website: https://modkeel.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-modkeel-modkeel/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-modkeel-modkeel/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-modkeel-modkeel/api.json
- HTML version of this page: https://verifymcp.io/servers/com-modkeel-modkeel/api