io.github.0xmortuex/acpi-mcp
PYPI · ACPI-MCP
Read ACPI tables from a live QEMU guest or files and explain them for OS developers.
Available components
Last scanned (9 hours ago)
Scores higher than 64% of PyPI servers
Category Developer Tools
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 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 (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 908 tokens (~113/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 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
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 14 Oct 26 +26
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 39
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 17 Oct 2026 · Analysed pypi/acpi-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 →
acpi_disassemble ~119
Disassemble a DSDT/SSDT's AML to ASL source with ACPICA's `iasl -d`. Needs iasl on PATH (Debian/Ubuntu: apt install acpica-tools; macOS: brew install acpica; Windows: the ACPICA release from intel.com/acpi). acpi_table already lists devices and \_S5_ without iasl.
| Name | Type | Req | Description |
|---|---|---|---|
| index | integer | – | – |
| max_chars | integer | – | – |
| name | string | yes | – |
| signature | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
acpi_dump ~65
Hexdump a table's raw bytes (offset/length within the table, max 4096 bytes).
| Name | Type | Req | Description |
|---|---|---|---|
| index | integer | – | – |
| length | integer | – | – |
| name | string | yes | – |
| offset | integer | – | – |
| signature | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
acpi_find ~94
Answer an OS-developer question from the tables, with the exact ports, addresses and values to use. Understands: shutdown / power off, reset / reboot, hpet, pci config / ecam, cpus / smp, irq routing / ioapic, pm timer, keyboard / ps2, serial, rtc century, sci.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| question | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
acpi_interrupt_routing ~71
Map every legacy ISA IRQ (0-15) to its GSI and I/O APIC pin, with polarity and trigger mode, from the MADT's interrupt source overrides. This is the table to program I/O APIC redirection entries from.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
acpi_load ~253
Load a set of ACPI tables and register it under `name`. Pass exactly one source: - port: a live VM's gdbstub (QEMU -s is port 1234). Tables are read from guest PHYSICAL memory, so this works even after the guest enables paging. QEMU allows one debugger at a time - disconnect gdbstub-mcp first. QEMU pauses the guest while attached; resume=True detaches afterwards (the guest runs on, even one started with -S), resume=False leaves it paused. If QEMU was started with -S the firmware hasn't built the tables yet: set boot_wait_s=5: it runs the guest until the tables exist, then stops. - path: a directory of raw tables - /sys/firmware/acpi/tables on Linux (needs root), or the output of `acpidump -b` (any OS). Tables are a snapshot; load again to re-read.
| Name | Type | Req | Description |
|---|---|---|---|
| boot_wait_s | number | – | – |
| host | string | – | – |
| name | string | yes | – |
| path | – | – | – |
| port | – | – | – |
| resume | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
acpi_sets ~14
List loaded table sets.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
acpi_table ~97
Decode one table and explain what it means for an OS. signature: FACP/FADT, APIC/MADT, HPET, MCFG, DSDT, SSDT, FACS, RSDT, XSDT, WAET, RSDP. index picks among duplicates (e.g. several SSDTs).
| Name | Type | Req | Description |
|---|---|---|---|
| index | integer | – | – |
| name | string | yes | – |
| signature | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
acpi_tables ~35
List every table: signature, address, length, checksum, OEM, and what it's for.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.0xmortuex/acpi-mcp server?
io.github.0xmortuex/acpi-mcp runs locally as a PyPI package, launched with uvx acpi-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 · acpi-mcp
claude mcp add 0xmortuex-acpi-mcp -- uvx acpi-mcp
What is the io.github.0xmortuex/acpi-mcp server?
io.github.0xmortuex/acpi-mcp is listed in the public MCP registry as io.github.0xmortuex/acpi-mcp. Read ACPI tables from a live QEMU guest or files and explain them for OS developers. This page covers its PyPI package (acpi-mcp).
Is the io.github.0xmortuex/acpi-mcp server safe to use?
io.github.0xmortuex/acpi-mcp scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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.0xmortuex/acpi-mcp server expose?
io.github.0xmortuex/acpi-mcp exposes 8 tools: acpi_load, acpi_tables, acpi_table, acpi_interrupt_routing, acpi_find, and 3 more. Their descriptions and schemas cost roughly 748 tokens of context every time the server is loaded.
Is the io.github.0xmortuex/acpi-mcp server still maintained?
io.github.0xmortuex/acpi-mcp is still listed as active in the MCP registry. We last reached this channel on 17 October 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.0xmortuex/acpi-mcp server under?
io.github.0xmortuex/acpi-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.