mcp-server-exogram@0.1.3
VERIFIED· not startedPublisher claims: "A Model Context Protocol server providing tools to evaluate, commit, and audit actions through the Exogram Authority Runtime" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
EXOGRAM_BEARER_TOKENConfiguration, not credentials: EXOGRAM_API_URL- Where it talks to
- exogram.ai (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for EXOGRAM_BEARER_TOKEN and talks to exogram.ai. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-09 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
@patch("mcp_server_exogram.server.httpx.Client.post")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.@patch("mcp_server_exogram.server.httpx.Client.post")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.@patch("mcp_server_exogram.server.httpx.Client.post")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.@patch("mcp_server_exogram.server.httpx.Client.post")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.@patch("mcp_server_exogram.server.httpx.Client.post")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mcp-server-exogram@0.1.3 as of 5d ago. This is the package itself, not its dependencies.