@conorbronsdon/substack-mcp
It exited or refused to answer until it is given configuration, such as a key or an argument. Run 2026-11-16.
Needs to start: SUBSTACK_PUBLICATION_URL, SUBSTACK_SESSION_TOKEN, SUBSTACK_USER_ID
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y -p @conorbronsdon/substack-mcp@1.3.0 substack-mcp
Installing a package runs its code. Use a sandbox for anything you have not read.
Its error output names these settings: SUBSTACK_PUBLICATION_URL, SUBSTACK_SESSION_TOKEN, SUBSTACK_USER_ID.
What it said when it did not start
Warning: Missing credentials: SUBSTACK_PUBLICATION_URL, SUBSTACK_SESSION_TOKEN, SUBSTACK_USER_ID Set them as SUBSTACK_* env vars, or run `substack-mcp-login` to sign in via browser. See README.md. Fatal error: Invalid configuration for publication "default": Invalid publication URL: use an HTTPS origin without a path, query, credentials or custom port. Run substack-mcp doctor --json to inspect each publication; run substack-mcp-login to set up a session.
Written by the package or by npm, not by this site.
Install facts
| License | MIT |
|---|---|
| Needs | node >=22.0.0 |
| Source | github.com/conorbronsdon/substack-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-wKAHgioqUDoVQO5fIBo10MbOUltGLAGBkMnM4s2vmCyCqPKy6twPSec0kId3BIG7enZ6X5OjuJusfytu3STVHA== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40conorbronsdon/substack-mcp)
New version out? Ask for a fresh report.