io.github.daedalus/mcp-capstone

Name: io.github.daedalus/mcp-capstone
Rating: 60 (1 reviews)
Author: io.github.daedalus

MCPcommunity

v0.1.0io.github.daedalusUnknownUpdated 2mo agoGitHub

MCP server exposing Capstone 5.0.7 disassembly framework

MCP server that exposes Capstone 5.0.7 disassembly framework functionalities as tools and resources, enabling LLMs to perform binary disassembly, reverse engineering, and instruction analysis. ARM (ARM, Thumb, ARM mode) MIPS (MIPS32/64, MIPS2/3, R6) PowerPC (32/64-bit, SPE, QPX) M680X (6301/6309/6800/6805/6808/6809/6811/CPU12/HCS08) BPF (Classic/Extended) EVM (Ethereum Virtual Machine)…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

2mo agoLast update

Package

Authorio.github.daedalus

LicenseUnknown

Version0.1.0

Sourcemcp-registry

GitHubdaedalus/mcp-capstone

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface—

Security scan✓ Cleanv0.1.0 · 19d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp