Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.gregario/warhammer-oracle

NPM · WARHAMMER-ORACLE

Warhammer 40K and Kill Team rules, stats, and game flow MCP server

Available components

0 this week 80 Trust /100

Last scanned (16 hours ago)

Scores higher than 66% of npm servers

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 611 tokens (~101/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 −2
    • Stability: pass → 0.87 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/warhammer-oracle@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 101 packages
Packages resolved 101
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~611 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_units ~91

Compare 2-4 Warhammer 40K units or Kill Team operatives side by side. Shows stats, weapons, abilities, and keywords for each.

NameTypeReqDescription
game_modestring–Game mode: '40k' (default) compares 40K units, 'kill_team' compares Kill Team operatives
unitsarrayyesUnit/operative names to compare (2-4 names)

No output schema declared.

No examples provided.

game_flow ~87

Show the full turn sequence for a game mode, or highlight the current phase and what comes next.

NameTypeReqDescription
current_phasestring–Name of the phase you're currently in (e.g. 'Shooting', 'Command'). If omitted, shows the full turn sequence overview.
game_modestring–Game mode (default: 40k). Use kill_team for Kill Team phases.

No output schema declared.

No examples provided.

lookup_keyword ~89

Look up a Warhammer 40K keyword or rule. Returns the official definition, a plain English explanation, examples, and applicable game modes.

NameTypeReqDescription
game_modestring–Optional game mode filter — only show keywords applicable to this mode
keywordstringyesName or partial name of the keyword to look up (e.g. 'Devastating Wounds', 'Feel No Pain')

No output schema declared.

No examples provided.

lookup_phase ~88

Look up a game phase by name. Returns step-by-step instructions and tips for the phase in the specified game mode.

NameTypeReqDescription
game_modestring–Game mode (default: 40k). Use kill_team for Kill Team phases.
phase_namestringyesName or partial name of the phase to look up (e.g. 'Shooting', 'Command', 'Firefight')

No output schema declared.

No examples provided.

lookup_unit ~113

Look up a Warhammer 40K unit or Kill Team operative datasheet by name. Returns stats, weapons, abilities, and keywords.

NameTypeReqDescription
factionstring–Optional faction name to narrow results (e.g. 'Chaos Space Marines', 'Astartes')
game_modestring–Game mode: '40k' (default) searches 40K units, 'kill_team' searches Kill Team operatives
unit_namestringyesName or partial name of the unit to search for

No output schema declared.

No examples provided.

search_units ~143

Search Warhammer 40K units or Kill Team operatives by name, faction, or keywords. Returns a compact list of matching results (max 10).

NameTypeReqDescription
factionstring–Optional faction filter to narrow results (e.g. 'Necrons', 'Aeldari')
game_modestring–Game mode: '40k' (default) searches 40K units, 'kill_team' searches Kill Team operatives
max_pointsnumber–Optional max points filter — only return units costing this many points or fewer (40K only)
querystringyesSearch query — matches against name, faction, and keywords

No output schema declared.

No examples provided.

Install

How do I install the io.github.gregario/warhammer-oracle MCP server?

io.github.gregario/warhammer-oracle runs locally as an npm package, launched with npx -y warhammer-oracle. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · warhammer-oracle

# add to Claude Code
claude mcp add gregario-warhammer-oracle -- npx -y warhammer-oracle
Common questions

What is the io.github.gregario/warhammer-oracle MCP server?

io.github.gregario/warhammer-oracle is an MCP server listed in the public MCP registry as io.github.gregario/warhammer-oracle. Warhammer 40K and Kill Team rules, stats, and game flow MCP server. This page covers its npm package (warhammer-oracle).

Is the io.github.gregario/warhammer-oracle MCP server safe to use?

io.github.gregario/warhammer-oracle scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.gregario/warhammer-oracle MCP server expose?

io.github.gregario/warhammer-oracle exposes 6 tools: lookup_unit, lookup_keyword, lookup_phase, search_units, compare_units, game_flow. Their descriptions and schemas cost roughly 611 tokens of context every time the server is loaded.

Is the io.github.gregario/warhammer-oracle MCP server still maintained?

io.github.gregario/warhammer-oracle is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.gregario/warhammer-oracle MCP server under?

io.github.gregario/warhammer-oracle declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.gregario/warhammer-oracle MCP server?

VerifyMCP ran 16 checks on io.github.gregario/warhammer-oracle, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.