3 findingsStatic scanned
Labby
dinglebear · MCP server
Sits between your AI clients and the MCP servers they use. It connects HTTP and stdio upstream servers, lets you inspect their tools, resources and prompts, filter what is exposed, and publish protected routes with bearer or OAuth authentication. A Code Mode option collapses the upstream catalogue into search and execute tools, and stored JavaScript snippets can run against it. Setup, a health check and server log search come with it, and current releases publish Linux and macOS builds but no Windows binaries.
Written by ooruby from the README of @dinglebear/labby 2.6.2.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your AI clients can reach several MCP servers through one place where authentication and exposure filters are applied.
What you could do with it
- Connect several upstream MCP servers and publish them as protected routes behind bearer or OAuth authentication.
- Expose one stdio MCP server unchanged over a Tailscale Serve HTTPS port with tailnet or bearer access.
- Run the built-in health audit that checks environment, reachability, authentication and versions.
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 (scripts/check-package.js:9)
- synchronous shell execution (scripts/check-package.js:67)
- synchronous shell execution (scripts/check-package.js:298)
- node child_process (scripts/install.js:10)
- 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
Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI.
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.6.2, the file with digest sha512-U7bbNmoEYAp6ViTbl+8ESmegjwzRKm6N5qgg0xbkuJSnyGtgsow9OhLeEKPRh8Np8HsfdrbCLgO4XZ4UWIICEA==, 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": {
"labby": {
"command": "npx",
"args": [
"-y",
"-p",
"@dinglebear/labby@2.6.2",
"labby"
]
}
}
}Or run it directly.
npx -y -p @dinglebear/labby@2.6.2 labbyPinned to 2.6.2, 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
- @dinglebear/labby
- Version read
- 2.6.2
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
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/dinglebear-labby)About this listing
- Kind
- MCP server
- Category
- Infrastructure
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
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.