2 findingsStatic scanned
Adds Storybook component and story documentation tools to an MCP server you run yourself.
9.4M installs/moMIT
Loopctl MCP Server
shopkeeper2 · MCP server
Loopctl MCP Server connects your AI agents to loopctl, a service for AI development loops. Agents can check the current tenant, list and resolve projects, create and delete work projects, import stories from a structured payload and read progress by story status. They can create knowledge-only scopes that group articles by repository, and post or hand off work on a repo coordination channel so another session can claim it. Per-tenant Context Retriever tools are added at runtime.
Written by ooruby from the README of loopctl-mcp-server 2.113.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Several agent sessions working in one repository can share project state and pass work to each other through the same server.
What you could do with it
- Resolve a repository to its project from a repo URL or slug before reading or writing its knowledge.
- Import a set of stories into a project, then read its progress with story counts by status.
- Hand a piece of work off on a repository channel so another agent session can claim it.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (lib/client-context.js:45)
- synchronous shell execution (lib/client-context.js:67)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
MCP server for loopctl — structural trust for AI development loops
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 2.113.0, the file with digest sha512-4E6KH9Q+MgLGNqVOXmHE60BXVDfHDM+okcCnQgw485vQImUXvllIDpTltKBzjXbn07TmlT9rr02niXxye5ckvA==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"loopctl-mcp-server": {
"command": "npx",
"args": [
"-y",
"loopctl-mcp-server@2.113.0"
]
}
}
}Or run it directly.
npx -y loopctl-mcp-server@2.113.0Pinned to 2.113.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- loopctl-mcp-server
- Version read
- 2.113.0
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/mkreyman/loopctl
- Commit
- 30c6a694c898
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/loopctl-mcp-server)About this listing
- Kind
- MCP server
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.