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.

Warframe

NPM · @PIPEWORX/MCP-WARFRAME · 2 COMPONENTS

Warframe MCP (WarframeStat API).

+3 this week 84 Trust /100

Last scanned (6 hours ago)

Scores higher than 81% 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-warframe). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 369 tokens (~92/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 3 Nov 26 +3
    • Stability: unverified → 0.17 ▲ functional
  • 29 Oct 26 81

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-warframe@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-warframe
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-warframe/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3561003925
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d5b7b677f6104f74fd24276f0b55b0e37e1bbe53dda8473befd1d7b7070c4a2e9648119c720c45813d9480c7bf87e91434ee68aaae90a1c3413b0b0a2

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~317 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
get_fissures ~78

List the active Void Fissures (Lith / Meso / Neo / Axi relic missions, including Steel Path and Void Storm variants) with node, mission type, enemy and time remaining. Keyless, live.

NameTypeReqDescription
platformstring–Platform: one of pc, ps4, xb1, swi. Default "pc".

No output schema declared.

No examples provided.

get_invasions ~65

List the active (non-completed) faction Invasions — node, description, attacking/defending factions and completion percentage. Keyless, live.

NameTypeReqDescription
platformstring–Platform: one of pc, ps4, xb1, swi. Default "pc".

No output schema declared.

No examples provided.

search_items ~71

Fuzzy-search Warframe item data — warframes, weapons, mods, and more — by name. Returns name, type, category and description. Keyless.

NameTypeReqDescription
querystringyesItem name to search for, e.g. "Excalibur", "Soma Prime", "Serration".

No output schema declared.

No examples provided.

world_state ~103

One-call summary of Warframe's live worldstate: the Plains of Eidolon (Cetus) day/night cycle, Cambion Drift (fass/vome), Orb Vallis (warm/cold), the current daily Sortie, Baro Ki'Teer's void-trader status, and the active Void Fissure count. Keyless, live.

NameTypeReqDescription
platformstring–Platform: one of pc, ps4, xb1, swi. Default "pc".

No output schema declared.

No examples provided.

Install

How do I install the Warframe MCP server?

Warframe runs locally as an npm package, launched with npx -y @pipeworx/mcp-warframe. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-warframe

# add to Claude Code
claude mcp add pipeworx-io-warframe -- npx -y @pipeworx/mcp-warframe
Common questions

What is the Warframe MCP server?

Warframe is an MCP server listed in the public MCP registry as io.github.pipeworx-io/warframe. Warframe MCP (WarframeStat API). This page covers its npm package (@pipeworx/mcp-warframe).

Is the Warframe MCP server safe to use?

Warframe scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Warframe MCP server expose?

Warframe exposes 4 tools: world_state, get_fissures, get_invasions, search_items. Their descriptions and schemas cost roughly 317 tokens of context every time the server is loaded.

Is the Warframe MCP server still maintained?

Warframe 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 licence is the Warframe MCP server under?

Warframe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.