Skip to content

MCP servers › io.github.headlesshq › headlessmc-mcp

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.headlesshq/headlessmc-mcp

Install, launch and control Minecraft: Java Edition clients and servers, also headless. — the publisher's description

8 of 9 record checks metRead-only · tools listed 2026-10-23Topic: other · AI-classifiedversion 0.1.0JavaMITstandard input/output21 tools

Summary

io.github.headlesshq/headlessmc-mcp is a local MCP server listed in the official MCP registry at version 0.1.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 21 tools, 0 resources and 0 prompts.

Record checks

8 of 9 record checks met

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • met: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: no download figure available
  • Not ranked by stars: 8 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
local package
Transport
standard input/output
Package
npm · listed version current
License
MIT
Dependencies
no known high or critical advisories
Repository
public
Tools
21
Described as changing data
14 of 21 toolsAI-classified
Mainly works on
files and code on the machine it runs onAI-classified
Topic
otherAI-classified
Last tested
2026-10-23

Add to your client

Worth knowing before you connect it

  • 14 tools are described as changing something (chat, click, connect, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
  • Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
0.1.0, published 2026-10-19 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-19 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.1.0 (published 2026-10-19).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
21tools
0resources
0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.

14 of 21 tools are described as changing something (creating, editing, deleting, sending or running).

  • chaton 28 other serverssends messagesdescribed as changing data

    “Sends a chat message, or a command if it starts with a slash, e.g.”

    2 inputs, 2 required
    • instancestringrequired“The instance id.”
    • messagestringrequired“The message or /command.”
  • clickon 27 other serverscontrols a browser or desktopdescribed as changing data

    “Clicks a button of the current screen, by the id from get_screen.”

    3 inputs, 2 required
    • instancestringrequired“The instance id.”
    • elementIdintegerrequired“The id of the element from get_screen.”
    • buttoninteger“Mouse button, 0 is left, 1 is right.”
  • connecton 1,144 other serversdescribed as changing data

    “Connects the client to a server.”

    3 inputs, 2 required
    • instancestringrequired“The instance id.”
    • hoststringrequired“Host name or ip of the server.”
    • portinteger“Port of the server.”
  • create_profileon 10 other serversdescribed as changing data

    “Creates a profile with its own game directory and installs its version.”

    4 inputs, 2 required
    • namestringrequired“Name of the profile: letters, digits, '.', '_' and '-'.”
    • versionstringrequired“Minecraft version, e.g.”
    • loaderstring“Modloader: fabric, forge, neoforge or vanilla.”
    • timeoutSecondsinteger“How long to wait for installing the version.”
  • delete_profileon 7 other serversdeletesdescribed as changing data

    “Deletes a profile.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 1 required
    • namestringrequired“Name of the profile.”
    • deleteFilesboolean“Also delete the game directory of the profile.”
  • disconnecton 13 other serversdescribed as changing data

    “Disconnects the client from the server or leaves the singleplayer world.”

    1 input, 1 required
    • instancestringrequired“The instance id.”
  • game_commandruns code or commandsdescribed as changing data

    “Executes any HMC-Specifics command inside the client and returns its output, e.g.”

    3 inputs, 2 required
    • instancestringrequired“The instance id.”
    • commandstringrequired“The command line.”
    • timeoutSecondsinteger“How long the game may take to execute the command.”
  • get_screenon 6 other serversreads or searches

    “Returns the screen the client currently displays as JSON: its class name and all buttons and text fields with their ids, texts, positions and whether they are enabled.”

    Publisher declares: read-only yes · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • instancestringrequired“The instance id.”
  • get_stateon 13 other serversreads or searches

    “Returns the state of the client as JSON: whether it is in a world, dead, the current screen, and metrics like position, health, food, dimension, server address, ping, TPS and the player list.”

    Publisher declares: read-only yes · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • instancestringrequired“The instance id.”
  • hmcruns code or commandsdescribed as changing data

    “Runs a HeadlessMc command line and returns its output, like the `headlessmc` CLI, without the leading `headlessmc`.”

    2 inputs, 1 required
    • commandstringrequired“The command line, e.g.”
    • timeoutSecondsinteger“How long to wait for the command.”
  • hmc_jobreads or searches

    “Returns the output and status of a HeadlessMc command started by the hmc tool.”

    Publisher declares: read-only yes · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • jobIdstringrequired“The job id returned by the hmc tool.”
  • instance_logreads or searches

    “Returns the latest lines of an instance's output (the game or server log).”

    Publisher declares: read-only yes · destructive yes · idempotent no · open-world yes

    3 inputs, 1 required
    • instancestringrequired“The instance id.”
    • linesinteger“How many lines to return.”
    • filterstring“Only return lines matching this regular expression.”
Show 9 more tools
  • launch_clientdescribed as changing data

    “Installs (if needed) and launches a Minecraft client and returns its instance id, once it shows the main menu.”

    8 inputs
    • versionstring“Minecraft version, e.g.”
    • loaderstring“Modloader: fabric, forge, neoforge or vanilla.”
    • profilestring“A profile (see list_profiles), created for version and loader if it does not exist.”
    • headlessboolean“Patch LWJGL so that nothing is rendered, works without a display or GPU.”
    • offlineboolean“Use an offline account, for headless testing only.”
    • serverstring“A server address to join right after the game started.”
    • jvmArgsstring“Additional JVM arguments, e.g.”
    • timeoutSecondsinteger“How long to wait for installing and starting the game.”
  • list_instanceson 12 other serversreads or searches

    “Lists the clients and servers launched by this MCP server, and the clients the user started with another launcher (attached instances, they need the HMC-Specifics and HMC-MCP-Bridge mods).”

    Publisher declares: read-only yes · destructive yes · idempotent no · open-world yes

    Takes no inputs.

  • list_profileson 48 other serversreads or searches

    “Lists the HeadlessMc profiles: name, version, game directory and the instance running it, if any.”

    Publisher declares: read-only yes · destructive yes · idempotent no · open-world yes

    Takes no inputs.

  • press_keyon 20 other serversdescribed as changing data

    “Presses a key in the client, see the HMC-Specifics `key` command, e.g.”

    2 inputs, 2 required
    • instancestringrequired“The instance id.”
    • keystringrequired“The arguments of the key command, e.g.”
  • server_commandon 2 other serversdescribed as changing data

    “Writes a line to the console (stdin) of a server instance, e.g.”

    3 inputs, 2 required
    • instancestringrequired“The instance id.”
    • commandstringrequired“The console command, without a leading slash.”
    • waitSecondsinteger“How long to collect output.”
  • set_texton 11 other serverscreates or changes datadescribed as changing data

    “Sets the text of a text field of the current screen, by the id from get_screen.”

    3 inputs, 3 required
    • instancestringrequired“The instance id.”
    • elementIdintegerrequired“The id of the text field from get_screen.”
    • textstringrequired“The text.”
  • start_serveron 2 other serversdescribed as changing data

    “Installs (if needed) and starts a dedicated server and returns its instance id once the world has loaded.”

    6 inputs
    • typestring“Server type: paper, fabric, purpur, forge, neoforge or vanilla.”
    • versionstring“Minecraft version, e.g.”
    • namestring“Name of an existing server, instead of type and version.”
    • acceptEulaboolean“The user explicitly agreed to the Minecraft EULA.”
    • jvmArgsstring“Additional JVM arguments, e.g.”
    • timeoutSecondsinteger“How long to wait for installing and starting the server.”
  • stop_instanceon 2 other serversdescribed as changing data

    “Stops a client or server.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 1 required
    • instancestringrequired“The instance id.”
    • forceboolean“Kill the process immediately instead of asking it to exit.”
  • wait_foron 16 other serversreads or searches

    “Waits until a condition holds for an instance, instead of polling: `in_world` (joined a world or server), `menu` (a screen with buttons is open, not a loading screen), `screen:<Name>` (a screen whose…”

    Publisher declares: read-only yes · destructive yes · idempotent no · open-world yes

    3 inputs, 2 required
    • instancestringrequired“The instance id.”
    • conditionstringrequired“The condition, e.g.”
    • timeoutSecondsinteger“How long to wait.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 21 tools
Says what it returns
44% of 18 tools
States limits, defaults or errors
33% of 21 tools
Says when to use it
0% of 21 tools
Items covered per tool
1.8 of 4 on average

Counted from the listing

Parameters with a description
100% of 53
Tools with a description
100% of 21
Typical description length
267 characters

The tool set

Counted from the listing

Tools
21
Size of the list
about 3,386 tokens for an agent to load (characters ÷ 4)
Naming
16 of 21 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 21 of 21 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package @headlesshq/headlessmc-mcp

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "headlessmc-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@headlesshq/headlessmc-mcp@0.1.0"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "headlessmc-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@headlesshq/headlessmc-mcp@0.1.0"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "headlessmc-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@headlesshq/headlessmc-mcp@0.1.0"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"headlessmc-mcp","type":"stdio","command":"npx","args":["-y","@headlesshq/headlessmc-mcp@0.1.0"]}'
Claude Code
claude mcp add --transport stdio headlessmc-mcp -- npx -y @headlesshq/headlessmc-mcp@0.1.0
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @headlesshq/headlessmc-mcp@0.1.0
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.1.0
Latest stable
0.1.0
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-M4X6+PjF//+HIWquU…
Signature
signed and attested
License
MIT

Source: the package registry · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Published package can be startedStarted and answeredmatchesour test · 2026-10-23
Version 0.1.0 on npmExists and can be installedmatchesnpm · 2026-10-23
Repository github.com/headlesshq/headlessmc-mcpOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.headlesshq
GitHub owner
an organization (headlesshq)
Build record
signed and attested
Repository
github.com/headlesshq/headlessmc-mcp
Stars
8
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

8 of 9 record checks met

  • Not ranked by downloads: no download figure available
  • Not ranked by stars: 8 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.headlesshq/headlessmc-mcp

Answered from the data above

Is io.github.headlesshq/headlessmc-mcp safe to install?

We do not rate servers as safe or unsafe. 8 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 14 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.headlesshq/headlessmc-mcp been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.headlesshq/headlessmc-mcp do?

It lists 21 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, send messages, run code or commands and control a browser or desktop. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.headlesshq/headlessmc-mcp change or delete data?

14 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.headlesshq/headlessmc-mcp publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 0.1.0, the latest stable release on npm.

Where is the source code of io.github.headlesshq/headlessmc-mcp?

In github.com/headlesshq/headlessmc-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “other” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not applicable
  17. Consent handling: not applicable
  18. Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 10
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
Does not apply to this server · 6
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted the published package in an isolated sandbox (read-only mode)
  2. 22,131 msConnected after 0 redirects.
  3. Read the inventory: 21 tools, 0 resources, 0 prompts.
  4. 23,401 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.
Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
logging, resources, tools
our test · 2026-10-23
Transport
standard input/output
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
registry · 2026-10-23
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
package registry · 2026-10-23
Integrity hash
declared (sri)
package registry · 2026-10-23
Signature / provenance
package registry · 2026-10-23
Dependency advisories
none known
npm audit · 2026-10-23
Popularity
not known (our limit)
Our lookup failed (network error, timeout or rate limit). This is our limit, not the server's.
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9 · build record: signed and attested
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
your machine
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.headlesshq/headlessmc-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.headlesshq/headlessmc-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 8 of 9 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.headlesshq/headlessmc-mcp)](https://protocolprobe.com/mcp/servers/io.github.headlesshq/headlessmc-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology