mcp@0.51.3
CAUTION· not startedPublisher claims: "Model Context Protocol server that exposes the Macula mesh to any agent harness" 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: Caution 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
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try mcp` runs it now and prints the full answer.
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-07 and scored it 78/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationsStatic findings
// A .env-style (or YAML-style) KEY=value/KEY: value line where KEY readsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// The group is already gone; the child's own kill below is a no-op then.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.// that's secret-bearing by convention (.env, id_rsa, .npmrc, ...)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// realistic bypass, an agent restructuring a .env file's lines intoFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// zero, at the honest cost of not catching a truly novel/unknown-formatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.return { kind: "skipped", path: rel, reason: "filename matches a known secret-bearing convention (.env/.pem/.key/id_rsa/.ssh/.aws/.npmrc/credentials.json) -- refusing to read it at all" };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose./(^|[/\\])\.env(\.|$)/, // .env, .env.local, .env.production, ...Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// `npx -y @macula-io/mcp` launch command that fails outright because thisFix: Pin versions and sources; vendor anything fetched at install time.* stdin is a real terminal (curl|bash installs have no TTY and mustFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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 @macula-io/mcp@0.51.3 as of 7d ago. This is the package itself, not its dependencies.
What would make this Verified
2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim macula-io: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Destructive file system command detected≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.