io.github.lambdasec/frame-mcp
PYPI · FRAME-MCP
MCP server for the Frame security scanner: scan, verify, fix, exploit, packs and separation logic.
Available components
Last scanned (1 hour ago)
Scores higher than 56% of PyPI servers
Category Security
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 774 tokens (~96/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 53
First indexed and scored.
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 pypi/frame-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 33 packages
| Packages resolved | 33 |
|---|---|
| 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 →
exploit ~136
Drive an LLM agent to exploit a live target. Authorized use only. Run this only against systems you own or are explicitly authorized to test. ``target`` is a URL such as http://app:8080. Optionally prime the agent with ``findings_json`` from ``scan``, a plain-language ``goal``, a ``success_check`` shell command (exit 0 means solved), and ``max_steps``. Needs the FRAME_LLM_* environment variables.
| Name | Type | Req | Description |
|---|---|---|---|
| findings_json | – | – | – |
| goal | – | – | – |
| max_steps | – | – | – |
| success_check | – | – | – |
| target | string | yes | – |
No output schema declared.
No examples provided.
fix ~113
Generate and verify fixes for scan findings. By default this returns a unified diff and does not touch any files. Set ``in_place=True`` to write the patches to the source files. Each patch is verified by re-scanning the patched code. This tool needs the FRAME_LLM_* environment variables (FRAME_LLM_BASE_URL, FRAME_LLM_MODEL, and an API key when the endpoint requires one).
| Name | Type | Req | Description |
|---|---|---|---|
| findings_json | – | yes | – |
| in_place | boolean | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
packs_check ~28
Validate one or more framework pack .toml files or directories.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | – |
No output schema declared.
No examples provided.
packs_list ~55
List the framework packs a scan would load. Packs teach Frame a framework's sources, sinks, sanitizers and entry points. Pass ``path`` to include a project directory's .frame/packs.
| Name | Type | Req | Description |
|---|---|---|---|
| path | – | – | – |
No output schema declared.
No examples provided.
scan ~189
Scan a file or directory for security vulnerabilities with Frame. Runs taint analysis plus separation logic verification and returns the findings as JSON. Set ``ai=True`` to add the LLM detection and triage layer (needs the FRAME_LLM_* environment variables). ``changed_ref`` scans only files that differ from a git ref; ``files`` restricts the scan to a list of files; ``baseline`` reports only findings absent from a baseline file; ``packs`` loads extra framework packs. This tool does not modify any files.
| Name | Type | Req | Description |
|---|---|---|---|
| ai | boolean | – | – |
| baseline | – | – | – |
| changed_ref | – | – | – |
| fail_on | string | – | – |
| files | – | – | – |
| language | – | – | – |
| min_severity | – | – | – |
| no_cross_file | boolean | – | – |
| packs | – | – | – |
| path | string | yes | – |
| root | – | – | – |
No output schema declared.
No examples provided.
solve ~73
Check whether a separation logic entailment ``P |- Q`` is valid. Example entailment: ``x |-> 5 |- x |-> 5``. Set ``model=True`` to return a countermodel when the entailment is invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| entailment | string | yes | – |
| model | boolean | – | – |
No output schema declared.
No examples provided.
verify ~96
Re-scan the files behind earlier findings and report their status. ``findings_json`` is the JSON produced by ``scan`` (a JSON string or the parsed object). Each finding comes back as fixed, file_removed, present, suppressed, uncertain or unverifiable. Pass ``ids`` (finding fingerprints) to check only specific findings. This tool does not modify any files.
| Name | Type | Req | Description |
|---|---|---|---|
| findings_json | – | yes | – |
| ids | – | – | – |
No output schema declared.
No examples provided.
write_baseline ~84
Scan ``path`` and record the findings as a baseline file. Writes ``baseline_file`` to disk (creating or overwriting it) and uses ``--fail-on none`` so the current state is accepted. Later scans can pass this file as ``baseline`` to report only new findings.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_file | string | yes | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.lambdasec/frame-mcp server?
io.github.lambdasec/frame-mcp runs locally as a PyPI package, launched with uvx frame-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · frame-mcp
claude mcp add lambdasec-frame-mcp -- uvx frame-mcp
What is the io.github.lambdasec/frame-mcp server?
io.github.lambdasec/frame-mcp is listed in the public MCP registry as io.github.lambdasec/frame-mcp. MCP server for the Frame security scanner: scan, verify, fix, exploit, packs and separation logic. This page covers its PyPI package (frame-mcp).
Is the io.github.lambdasec/frame-mcp server safe to use?
io.github.lambdasec/frame-mcp scores 57 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 io.github.lambdasec/frame-mcp server expose?
io.github.lambdasec/frame-mcp exposes 8 tools: scan, write_baseline, verify, fix, exploit, and 3 more. Their descriptions and schemas cost roughly 774 tokens of context every time the server is loaded.
Is the io.github.lambdasec/frame-mcp server still maintained?
io.github.lambdasec/frame-mcp 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 io.github.lambdasec/frame-mcp server under?
io.github.lambdasec/frame-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.