mcp-emulate
PyPI
v0.1.0
Published by labguy94 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for CPU emulation via Unicorn, Capstone, and Keystone
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_server_integration.py:20`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ne: self.proc = subprocess.Popen( [sys.executable, "-m", "mcp_emulate.server"], stdin=su
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/test_server_integration.py
Each tool and what it can reach — statically extracted from the published source.
hexdumpreads sensitive dataadd_breakpointno sensitive capabilityadd_symbolno sensitive capabilityadd_watchpointno sensitive capabilityassembleno sensitive capabilityassemble_and_loadno sensitive capabilitycreate_emulatorno sensitive capabilitydestroy_emulatorno sensitive capabilitydetect_archno sensitive capabilitydiff_contextno sensitive capabilitydiff_memoryno sensitive capabilitydiff_traceno sensitive capabilitydisable_coverageno sensitive capabilitydisable_traceno sensitive capabilitydisassembleno sensitive capabilityemulateno sensitive capabilityenable_coverageno sensitive capabilityenable_traceno sensitive capabilityexport_sessionno sensitive capabilityfill_memoryno sensitive capabilityget_coverageno sensitive capabilityget_fp_registersno sensitive capabilityget_registersno sensitive capabilityget_stackno sensitive capabilityget_syscall_logno sensitive capabilityget_traceno sensitive capabilityhook_syscallno sensitive capabilityimport_sessionno sensitive capabilitylist_breakpointsno sensitive capabilitylist_regionsno sensitive capabilitylist_symbolsno sensitive capabilitylist_watchpointsno sensitive capabilityload_binaryno sensitive capabilityload_executableno sensitive capabilitymap_memoryno sensitive capabilitymemory_mapno sensitive capabilitynop_outno sensitive capabilityprotect_memoryno sensitive capabilityread_memoryno sensitive capabilityremove_breakpointno sensitive capabilityremove_symbolno sensitive capabilityremove_watchpointno sensitive capabilityrestore_contextno sensitive capabilityrun_and_diffno sensitive capabilitysave_contextno sensitive capabilitysave_traceno sensitive capabilitysearch_memoryno sensitive capabilityset_fp_registersno sensitive capabilityset_registersno sensitive capabilitysetup_stackno sensitive capabilitysnapshot_memoryno sensitive capabilitystepno sensitive capabilityunhook_syscallno sensitive capabilityunmap_memoryno sensitive capabilitywrite_memoryno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-08-25 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-emulate --online --registry pypi
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Generates production-ready UI components from natural language, inspired by v0.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.