@storyshelf/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: STORYSHELF_URL
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 @storyshelf/mcp@0.13.0
Installing a package runs its code. Use a sandbox for anything you have not read.
Its error output names these settings: STORYSHELF_URL.
What it said when it did not start
STORYSHELF_URL is required (or pass --url)
Written by the package or by npm, not by this site.
Install facts
| License | MIT |
|---|---|
| Needs | node >=24 |
| Source | github.com/GuptaSiddhant/StoryShelf |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-WrvUkUAXTIu/gEMX4C+FQUuGNfXvrZxyZM8F7QVbEU85yD/ChLCb7gjQ2FmJEmQ3M1Yo4CmuMoW6gzhJ894EFg== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 0.13.0 | 2026-11-16 | Needs setup before it starts | 0 |
| 0.10.1 | 2026-11-12 | Needs setup before it starts | 0 |
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/%40storyshelf/mcp)
New version out? Ask for a fresh report.