mcp-server-exogram@0.2.0
VERIFIED· install onlyPublisher claims: "Connects external AI tools into Exogram—a Personal AI Agent and workspace that understands your work, people, and life, coordinates specialist agents, renders interactive deliverables, and executes tasks with your approval." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
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_API_KEYEXOGRAM_BEARER_TOKENConfiguration, not credentials: EXOGRAM_API_URL, EXOGRAM_DB_PATH, EXOGRAM_LOCAL_MODE- Where it talks to
- exogram.ai (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard. It asks for EXOGRAM_API_KEY, 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 (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-12 and scored it 89/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 · 1 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.chmod +x mcp-publisherFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.@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. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.