
Ghost Mcp Server
io.github.ghostsecurityPublished by GitHub account ghostsecurityv1.0.1Updated Oct 24, 2026
Minimal MCP server for Ghost Security API - compatible with all MCP clients
Overview
A minimal local MCP server that connects MCP clients to the Ghost Security API, letting an assistant work with Ghost Security data.
- What you can do
- The input lists no tools, so capabilities are inferred from the description only.
- It is described as a minimal MCP server for the Ghost Security API, compatible with all MCP clients.
- It runs locally over stdio, so an assistant can reach Ghost Security through the same client it already uses.
- No specific operations, endpoints or data types are documented in the supplied material.
- When to use it
- Worth considering if you already use Ghost Security and want an MCP-capable assistant to reach its API from a local client, rather than switching tools. Because no tools or README are provided, check the package itself before relying on it for a specific task.
- Requirements
- Runs as a local process over stdio, installed from the npm package ghostsecurity-mcp, so a Node.js runtime and an MCP client that supports stdio servers are needed. The manifest declares no authentication, environment variables or headers, but the description points to the Ghost Security API, so access to that API is presumably required; confirm how credentials are supplied.
Installation
In SourceWeft
- Open Ghost Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.