# COD Loadout for AI assistants and developers

URL: https://codloadout.gitlab.io/ai/
Updated: 2026-11-04

Everything on COD Loadout is also published as plain files and through a read-only MCP server. Each value says whether Activision published it or a community site reported it, and each file carries a date. Activision does not publish damage or time to kill, so no file and no tool here estimates them.

## Files for crawlers and scripts

These files are static, public and need no key. They are rebuilt with the site and change only when the data is refreshed, so fetch one once and keep it until its date changes. The Modern Warfare 4 files are listed here.

*Machine-readable files, what each holds, which layer it belongs to and the date of its data*

| File | What it holds | Layer | Data date |
| --- | --- | --- | --- |
| [`/llms.txt`](https://codloadout.gitlab.io/llms.txt) | Short index of the pages and sources, written for language models. | Both, each row labelled | 2026-11-04 |
| [`/llms-full.txt`](https://codloadout.gitlab.io/llms-full.txt) | Every weapon, Apex Attachment, attachment type, community attachment, tier placement, build, perk and piece of equipment as Markdown tables. | Both, each row labelled | 2026-11-04 |
| [`/data/mw4.json`](https://codloadout.gitlab.io/data/mw4.json) | 33 weapons with fire rate, magazine, reserve, weapon levels, unlock levels and attachment types, plus Apex Attachments, perks, equipment and killstreaks. | Activision-published | 2026-10-24 |
| [`/data/mw4-community-stats.json`](https://codloadout.gitlab.io/data/mw4-community-stats.json) | Base stats of 33 weapons and the multiplier each attachment applies to them. | Community-reported (CODMunity) | 2026-11-04 |
| [`/data/mw4-community-builds.json`](https://codloadout.gitlab.io/data/mw4-community-builds.json) | 130 builds with build codes, plus each weapon's Multiplayer pick rate. | Community-reported (CODMunity) | 2026-11-04 |
| [`/data/mw4-community-tiers.json`](https://codloadout.gitlab.io/data/mw4-community-tiers.json) | 67 tier placements from ggranked and DMZ Radar, each list with its own method. | Community-reported (ggranked and DMZ Radar) | 2026-11-04 |
| [`/data/mw4-community-attachments.json`](https://codloadout.gitlab.io/data/mw4-community-attachments.json) | 615 standard attachments with names, labels and the weapons they were reported on, and some weapon levels. | Community-reported (DMZ Codex, DMZ Radar, wzranked, ggranked, and CODMunity) | 2026-10-28 |
| [`/sitemap.xml`](https://codloadout.gitlab.io/sitemap.xml) | Every indexable page with the date of the data it shows. | Not data | 2026-11-04 |
| `/mw4/weapons/m4/index.md` | The same page as Markdown: add index.md to any page address, for example the file shown in the first column. | Both, each row labelled | 2026-11-04 |
| [`/mw4/feed.xml`](https://codloadout.gitlab.io/mw4/feed.xml) | Feed of recent changes to the data and the pages. | Both, each row labelled | 2026-11-04 |

## Which numbers come from where

Two layers are kept apart in every file, every page and every MCP result.

### Activision-published

Fire rate, magazine, reserve, weapon levels, unlock levels, attachment types, Apex Attachments and what they block, perks, equipment and killstreaks. They come from Activision's launch posts and carry the data date October 24, 2026. MCP results mark them with the status "official".

### Community-reported

Weapon base stats and what attachments change (CODMunity), builds and pick rates (CODMunity), tier placements (ggranked, DMZ Radar) and the standard attachment list. Community sites report them, nobody has verified them, and a patch can change them. Each file and result carries the date it was read. MCP results mark them with the status "community-reported".

### What is not here

A damage table and time to kill are not published by Activision, and the site does not compute or estimate them. The only time-to-kill figures are the milliseconds one community tier list reports, shown as that list's own measure. When a source does not report a value, the file says null or "not reported". It never writes 0.

## MCP server

COD Loadout runs a read-only [Model Context Protocol](https://modelcontextprotocol.io/) server. The endpoint is `https://codloadout-mcp.worker-rebi.workers.dev/mcp`. It speaks Streamable HTTP in stateless mode: one JSON-RPC 2.0 request in a POST, one JSON response. There is no account, no key and nothing to install.

The tools read the JSON files listed above at request time and cache them for five minutes, so an answer always matches the site. Every result names the layer each number comes from, says whether it is official or community-reported, gives the data date and gives the page to cite. Names are matched without regard to case or punctuation, and a miss returns a list of near matches.

*MCP tools, what each returns, its arguments and an example*

| Tool | Returns | Arguments | Example arguments |
| --- | --- | --- | --- |
| `list_weapons` | Every weapon with class, unlock level, fire rate, magazine and reserve, or one class. | `class` (optional) | `{"class": "SMG"}` |
| `get_weapon` | One weapon: Activision numbers, then community base stats, tier placements, pick rate and build count, kept apart. | `weapon` (required) | `{"weapon": "M4"}` |
| `get_best_build` | Community builds for a weapon, best listed tier first, with build codes, the main stat changes and a class builder link. | `weapon` (required); `mode` (optional) | `{"weapon": "Han 86", "mode": "multiplayer"}` |
| `compare_weapons` | One row per stat for two weapons with the better value of each stat. Unknown values are null. Not an overall rating. | `a` (required); `b` (required) | `{"a": "M4", "b": "VEL 46"}` |
| `search_attachments` | Community-reported attachments matching a name, a weapon or a type, with the stat changes reported for that weapon. | `query` (optional); `weapon` (optional); `type` (optional) | `{"query": "suppressor", "weapon": "M4"}` |
| `get_unlock_level` | The Player Level of a weapon, perk, equipment or killstreak, or the community-reported weapon level of an attachment. | `item` (required) | `{"item": "Ghost"}` |
| `get_patch_notes` | Recent patches, newest first, with the weapon changes listed. Says "not available yet" until the site publishes patch notes. | `limit` (optional) | `{"limit": 3}` |

### Example call

Ask for the M4 with curl. The response below is trimmed to a few fields; the full result also lists every community base stat, the tier placements, the source files and the notes.

```
curl -s -X POST https://codloadout-mcp.worker-rebi.workers.dev/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_weapon","arguments":{"weapon":"M4"}}}'

{
  "weapon": {
    "id": "m4",
    "name": "M4",
    "page": "https://codloadout.gitlab.io/mw4/weapons/m4/"
  },
  "official": {
    "status": "official",
    "unlockPlayerLevel": 14,
    "weaponLevels": 72,
    "fireRateRpm": 810,
    "magazine": 30,
    "reserve": 90,
    "apexAttachment": {
      "name": "M4 Hurricane",
      "blocks": [
        "Barrel",
        "Magazine"
      ]
    }
  },
  "community": {
    "status": "community-reported",
    "pickRate": {
      "percent": 5.6,
      "mode": "multiplayer",
      "source": "CODMunity",
      "retrieved": "2026-11-04"
    }
  },
  "dataDate": "2026-11-04",
  "cite": {
    "text": "COD Loadout: M4 in Modern Warfare 4",
    "url": "https://codloadout.gitlab.io/mw4/weapons/m4/"
  }
}
```

The result is JSON in the content field and again, parsed, in structuredContent.

## Connect a client

Any MCP client that accepts a remote server by URL needs only the endpoint address. No authentication is used. Clients name their settings differently, so look in your client's documentation for where a remote or Streamable HTTP server goes. This site does not test or vouch for particular products. The JSON below is a generic form in the layout many clients use; rename the fields to match yours.

```
{
  "mcpServers": {
    "codloadout": {
      "url": "https://codloadout-mcp.worker-rebi.workers.dev/mcp"
    }
  }
}
```

### Check the connection from a terminal

These two commands show that the endpoint answers. The first initialises a session, the second lists the tools.

```
curl -s -X POST https://codloadout-mcp.worker-rebi.workers.dev/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

curl -s -X POST https://codloadout-mcp.worker-rebi.workers.dev/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'
```

A browser can read the plain-text description of the server at the root of the same host. Browser clients are allowed by CORS.

## How to cite

Cite the page you read, with the data date shown on it. MCP results give both in the cite and dataDate fields.

- **Name**: COD Loadout, an unofficial Call of Duty: Modern Warfare 4 fan reference. Not affiliated with Activision or Infinity Ward.
- **URL**: [https://codloadout.gitlab.io/](https://codloadout.gitlab.io/)
- **Data date**: October 24, 2026 for Activision-published data, November 4, 2026 for the newest community data. Use the date printed on the page or in the result you used.

- Name the page address you read, not only the site.
- Give the data date of the page or result, not the date you read it.
- Community-reported data must be attributed to its source as well as to COD Loadout: weapon stats and builds to CODMunity, tier placements to ggranked or DMZ Radar, according to the layer shown on the page.
- Do not present community-reported numbers as Activision data, and do not call them current after a patch.
- Do not state damage or time to kill for a weapon on the strength of this site. It has no such data.

### Example citation

```
COD Loadout, "M4 in Modern Warfare 4", https://codloadout.gitlab.io/mw4/weapons/m4/, Activision-published data of 2026-10-24, community-reported stats from CODMunity read 2026-11-04.
```

## Frequently asked questions

**Q: Can I use COD Loadout data in my own project?**

A: The JSON files are public and need no key, and the MCP server is open to any client. Fetch a file once and keep it until its date changes. The site states no licence for the data beyond the citation rules on this page. The names, artwork and trademarks of the game belong to Activision.

**Q: Does the MCP server cost anything or need a key?**

A: No. It is free to call, needs no account and cannot change anything: every tool only reads the published JSON files.

**Q: How current is the data?**

A: Each file carries the date of its data, and the same dates are on the pages. The MCP server reads the files from the site at request time and keeps them for five minutes, so it is never ahead of the site and at most five minutes behind it. Community data is read again from its sources from time to time and a patch can make it out of date.

**Q: Does COD Loadout publish damage or time to kill?**

A: No. Activision has not published a damage table or time to kill, and the site does not estimate them. One community tier list reports a time-to-kill figure in milliseconds, and the tier file shows it labelled as that list's own measure.

**Q: What does null or "not reported" mean?**

A: The source does not give that value. It does not mean zero and it does not mean the weapon or attachment has no effect.

**Q: Should I read llms.txt or llms-full.txt?**

A: Start with llms.txt, a short index with links. llms-full.txt holds every table of the site as Markdown for a model that needs the numbers in one request.