io.github.daedalus/mcp-capstone
PYPI · MCP-CAPSTONE · SCANNED SEP 20
MCP server exposing Capstone 5.0.7 disassembly framework
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 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 native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 18 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 (MIT).Pass
- Actively maintained (last published 163 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the io.github.daedalus/mcp-capstone server?
io.github.daedalus/mcp-capstone runs locally as a PyPI package, launched with uvx mcp-capstone. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-capstone
claude mcp add daedalus-mcp-capstone -- uvx mcp-capstone
{
"mcpServers": {
"daedalus-mcp-capstone": {
"command": "uvx",
"args": [
"mcp-capstone"
]
}
}
} {
"servers": {
"daedalus-mcp-capstone": {
"command": "uvx",
"args": [
"mcp-capstone"
]
}
}
} codex mcp add daedalus-mcp-capstone -- uvx mcp-capstone
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"daedalus-mcp-capstone": {
"type": "local",
"command": [
"uvx",
"mcp-capstone"
],
"enabled": true
}
}
} openclaw mcp add daedalus-mcp-capstone --command uvx --arg mcp-capstone
mcp_servers:
daedalus-mcp-capstone:
command: "uvx"
args: ["mcp-capstone"] {
"McpServers": {
"daedalus-mcp-capstone": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-capstone"
]
}
}
} assistant mcp add daedalus-mcp-capstone -t stdio -c uvx -a mcp-capstone
{
"mcpServers": {
"daedalus-mcp-capstone": {
"command": "uvx",
"args": [
"mcp-capstone"
]
}
}
} 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.
- 18 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 6 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 5 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 20 Sept 2026 · Analysed pypi/mcp-capstone@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 |
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 18 packages
| Packages resolved | 18 |
|---|---|
| Stale | 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the io.github.daedalus/mcp-capstone server?
io.github.daedalus/mcp-capstone is listed in the public MCP registry as io.github.daedalus/mcp-capstone. MCP server exposing Capstone 5.0.7 disassembly framework. This page covers its PyPI package (mcp-capstone).
Is the io.github.daedalus/mcp-capstone server safe to use?
io.github.daedalus/mcp-capstone scores 24 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.
Is the io.github.daedalus/mcp-capstone server still maintained?
io.github.daedalus/mcp-capstone is still listed as active in the MCP registry. We last reached this channel on 20 September 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.daedalus/mcp-capstone server under?
io.github.daedalus/mcp-capstone declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.