Flameox
PYPI · FLAMEOX · SCANNED SEP 21
Bounded local runtime evidence from explicit artifacts and typed direct targets.
Available components
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
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 5 of 52 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 498 tokens (~83/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 Management0
- Stability check failed: the tool surface changed between 0.1.12 and 0.2.7: 87 tool removals, 0 breaking changes, 6 additions. See how to fix → Fail
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Flameox MCP server?
Flameox runs locally as a PyPI package, launched with uvx flameox. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · flameox
claude mcp add morluto-flameox -- uvx flameox
{
"mcpServers": {
"morluto-flameox": {
"command": "uvx",
"args": [
"flameox"
]
}
}
} {
"servers": {
"morluto-flameox": {
"command": "uvx",
"args": [
"flameox"
]
}
}
} codex mcp add morluto-flameox -- uvx flameox
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"morluto-flameox": {
"type": "local",
"command": [
"uvx",
"flameox"
],
"enabled": true
}
}
} openclaw mcp add morluto-flameox --command uvx --arg flameox
mcp_servers:
morluto-flameox:
command: "uvx"
args: ["flameox"] {
"McpServers": {
"morluto-flameox": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"flameox"
]
}
}
} assistant mcp add morluto-flameox -t stdio -c uvx -a flameox
{
"mcpServers": {
"morluto-flameox": {
"command": "uvx",
"args": [
"flameox"
]
}
}
} 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.
- 21 Sept 26 0
- Package version: 0.1.11 → 0.2.7 functional
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 0
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Tool coverage: 100% → 88% ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: fail → pass ▲ functional
- Destructive annotations: 100 → pass functional
- Package version: 0.2.6 → 0.2.7 functional
- 9 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 7 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.5 → 0.2.6 functional
- 6 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Sept 26 −11
- Malware scan: pass → unverified ▼ security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: fair → good functional
- Package version: 0.2.4 → 0.2.5 functional
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 Sept 2026 · Analysed pypi/flameox@0.2.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 52 packages
| Packages resolved | 52 |
|---|---|
| Stale | 4 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
analyze ~37
Analyze existing native artifacts with one typed evidence capability.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Maximum evidence rows returned on this page. |
| request | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
capture_and_analyze ~44
Capture a target once, or supply an experiment design for paired cases.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | integer | – | Maximum evidence rows returned on this page. |
| request | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
prepare_providers ~56
Prepare managed providers and return any required MCP reconnection action.
| Name | Type | Req | Description |
|---|---|---|---|
| provider_ids | array | yes | Complete desired set of Flameox-managed and host provider IDs. |
| timeout_seconds | integer | – | Maximum uvx environment preparation time in seconds. |
Structured output declared, but exposes no named fields.
No examples provided.
preserve_evidence ~39
Idempotently preserve one session analysis and its native artifacts.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_id | string | yes | Session analysis handle returned by an analysis or capture tool. |
Structured output declared, but exposes no named fields.
No examples provided.
query_evidence ~129
Search an immutable, request-pinned manifest inventory in deterministic order.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | – | – | Exact capability ID filter. |
| created_after | – | – | Inclusive lower creation-time bound with timezone. |
| created_before | – | – | Inclusive upper creation-time bound with timezone. |
| cursor | – | – | Opaque cursor from the preceding query page; reuse the same filters. |
| evidence_kind | – | – | Exact preserved evidence-kind filter. |
| input_sha256 | – | – | Lowercase SHA-256 digest of a contributing input. |
| page_size | integer | – | Maximum matching manifests returned on this page. |
| provider_id | – | – | Exact provider ID filter. |
Structured output declared, but exposes no named fields.
No examples provided.
rescue_evidence ~63
Rescue one live session analysis to a distinct empty store before restart.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_id | string | yes | Live session analysis handle to rescue before reconnecting. |
| destination | string | yes | Explicit absolute path to a distinct empty evidence directory. The active configured repository is not changed. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Flameox MCP server?
Flameox is an MCP server listed in the public MCP registry as io.github.morluto/flameox. Bounded local runtime evidence from explicit artifacts and typed direct targets. This page covers its PyPI package (flameox).
Is the Flameox MCP server safe to use?
Flameox scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 Flameox MCP server expose?
Flameox exposes 6 tools: prepare_providers, analyze, capture_and_analyze, preserve_evidence, rescue_evidence, query_evidence. Their descriptions and schemas cost roughly 368 tokens of context every time the server is loaded.
Is the Flameox MCP server still maintained?
Flameox is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.