# io.github.0xmortuex/acpi-mcp (pypi · acpi-mcp)

Read ACPI tables from a live QEMU guest or files and explain them for OS developers.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- pypi · `acpi-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/0xmortuex-acpi-mcp/acpi-mcp.md), [page](https://verifymcp.io/servers/0xmortuex-acpi-mcp/acpi-mcp)

## Channel facts

- Registry: `pypi`
- Package: `acpi-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 33 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### 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.

### Claude

```bash
claude mcp add 0xmortuex-acpi-mcp -- uvx acpi-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "0xmortuex-acpi-mcp": {
      "command": "uvx",
      "args": [
        "acpi-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "0xmortuex-acpi-mcp": {
      "command": "uvx",
      "args": [
        "acpi-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add 0xmortuex-acpi-mcp -- uvx acpi-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "0xmortuex-acpi-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "acpi-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 0xmortuex-acpi-mcp --command uvx --arg acpi-mcp
```

### Hermes

```yaml
mcp_servers:
  0xmortuex-acpi-mcp:
    command: "uvx"
    args: ["acpi-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "0xmortuex-acpi-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "acpi-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add 0xmortuex-acpi-mcp -t stdio -c uvx -a acpi-mcp
```

### Other

```json
{
  "mcpServers": {
    "0xmortuex-acpi-mcp": {
      "command": "uvx",
      "args": [
        "acpi-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-14 (score 65, +26)

- [security improvement] 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).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] 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

### 2026-10-12 (score 39)

First indexed and scored.

## MCP tools (8)

### `acpi_load` (~253 tokens)

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.

Input parameters:

- `boot_wait_s` (number)
- `host` (string)
- `name` (string, required)
- `path`
- `port`
- `resume` (boolean)

Output parameters:

- `result` (string)

### `acpi_tables` (~35 tokens)

List every table: signature, address, length, checksum, OEM, and what it's for.

Input parameters:

- `name` (string, required)

Output parameters:

- `result` (string)

### `acpi_table` (~97 tokens)

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).

Input parameters:

- `index` (integer)
- `name` (string, required)
- `signature` (string, required)

Output parameters:

- `result` (string)

### `acpi_interrupt_routing` (~71 tokens)

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.

Input parameters:

- `name` (string, required)

Output parameters:

- `result` (string)

### `acpi_find` (~94 tokens)

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.

Input parameters:

- `name` (string, required)
- `question` (string, required)

Output parameters:

- `result` (string)

### `acpi_dump` (~65 tokens)

Hexdump a table's raw bytes (offset/length within the table, max 4096 bytes).

Input parameters:

- `index` (integer)
- `length` (integer)
- `name` (string, required)
- `offset` (integer)
- `signature` (string, required)

Output parameters:

- `result` (string)

### `acpi_disassemble` (~119 tokens)

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.

Input parameters:

- `index` (integer)
- `max_chars` (integer)
- `name` (string, required)
- `signature` (string)

Output parameters:

- `result` (string)

### `acpi_sets` (~14 tokens)

List loaded table sets.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/0xmortuex-acpi-mcp/acpi-mcp#diagnostics

## Score history

- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 65
- 2026-10-13: 39
- 2026-10-12: 39

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/acpi-mcp/
- Socket report: https://socket.dev/pypi/package/acpi-mcp
- Repository: https://github.com/0xmortuex/acpi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/0xmortuex-acpi-mcp/acpi-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/0xmortuex-acpi-mcp/acpi-mcp.json
- HTML version of this page: https://verifymcp.io/servers/0xmortuex-acpi-mcp/acpi-mcp