MCP, MCP server
Substack Publisher Mcp
MCP server for Substack's official Publisher API
Compatibility: Not stated.
Grade B
Minor issues only, no Medium or High. Worth a quick look at the findings below before installing.
Not a guarantee. A hygiene check of the source at the commit shown, not a security audit.
NETWORK_NO_FIXED_HOST SECRETS_PATH_DOTENV SECRETS_ENV_READ
Why this grade
- NETWORK_NO_FIXED_HOST Low
Makes a network call whose host is not written as a fixed address.
src/substack.ts, line 134
response = await fetch(url.toString(), { - SECRETS_PATH_DOTENV Low
Mentions a .env file.
.github/pull_request_template.md, line 25
- [ ] No API keys, subscriber data, or `.env` contents in the diff or description - SECRETS_ENV_READ Note
Reads an environment variable whose name contains KEY, SECRET, TOKEN, PASSWORD or CREDENTIAL.
CLAUDE.md, line 19
- Read directly from `process.env`; the server never loads `.env` files. Set vars in the MCP client config, or in your shell for `npm start`.
Any High, or two or more Medium findings, give D. One Medium gives C. Low findings or a security Note give B. Each code names a finding behind the letter.
Grades are a hygiene check of the source at the commit shown, on the date checked, not a security audit or a guarantee. The free directory grades are automated. Before release, a PlugVet engineer reviews every paid report and any grade we hold back, including all F grades, against the source code and the evidence we quote.
What was checked
Plain notes from the hygiene checks.
Permissions
Pass
No shell or command execution found, and no extra permission was declared.
Install and update
Pass
No install-time script found, and dependencies are pinned or absent.
Network
Concern
can reach a host that is not written as a fixed address.
NETWORK_NO_FIXED_HOST
src/substack.ts, line 134
response = await fetch(url.toString(), {
Secrets
Concern
reads a credential or environment file.
SECRETS_ENV_READ SECRETS_PATH_DOTENV
.github/pull_request_template.md, line 25
- [ ] No API keys, subscriber data, or `.env` contents in the diff or description
.gitignore, line 2
dist/
CLAUDE.md, line 19
- Read directly from `process.env`; the server never loads `.env` files. Set vars in the MCP client config, or in your shell for `npm start`.
Show more
AGENTS.md, line 14
- Keep secrets out of committed files - env vars come from the MCP client config or shell (the server never loads `.env`)
CHANGELOG.md, line 66
- Removed stale dotenv/`.env` references from contributor docs (the server reads env vars directly and never loaded `.env`); deleted `.env.example`.
CONTRIBUTING.md, line 15
2. Export your API key in your shell (the server reads env vars directly; it does not load `.env` files):
SECURITY.md, line 28
- Misconfigured deployments (e.g., committing your own `.env`). The repo ships `.gitignore` rules for the obvious files; you are responsible for not bypassing them.
SECURITY.md, line 42
- Treat `.env` as a credential file. Do not commit it. Do not paste its contents into chat logs or issue trackers.
Agent instructions
Pass
No instruction to ignore earlier instructions or to hide a step.
Obfuscation
Pass
No encoded or minified payload found.
Licence
Pass
A licence file is present (LICENSE).
Maintainer activity
Pass
The latest commit is within the last 365 days.
Note
Hygiene check of commit 3da3d26c0347. can reach a host that is not written as a fixed address. reads a credential or environment file.
Date and source
Date checked:
github.com
Commit graded: 3da3d26c034736b5a3d207e574e2da3d6b5b5f8a
This link goes to the original host. PlugVet does not host or check what you download from there, and installing it is your own decision and risk.