primer-mcp@0.1.8
VERIFIED· not startedPublisher claims: "A Jira-lite MCP server that guides planning-first workflows for AI-assisted development — tickets as markdown files, your AI agent as the interface." 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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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-15 and scored it 93/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
| `init_project` | Create the `primer/` ticket store and add the workflow section to CLAUDE.md |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.… `init_project`), this section is appended to your agent config file (CLAUDE.md, AGENTS.md) to guide the agent. If you prefer to add it manually: ```markdown ## primer-mcp This project uses primer-mcp for plann…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.| `init_project` | Create the `primer/` ticket store and add the workflow section to CLAUDE.md |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…er, so it can't separate them. The obvious ablation is a third arm with only the CLAUDE.md instructions. What the tools add in principle is structure and a durable record, but the eval hasn't shown that …Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.… `init_project`), this section is appended to your agent config file (CLAUDE.md, AGENTS.md) to guide the agent. If you prefer to add it manually: ```markdown ## primer-mcp This project uses primer-mcp for plann…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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 primer-mcp@0.1.8 as of 2 h ago. This is the package itself, not its dependencies.