Signadot MCP Server
io.github.signadot/cli·vv1.9.0·8 starsConnect to Signadot to manage ephemeral environments and route traffic to local services.
not scanned yet
8 stars
Reviews
Write oneNobody has reviewed Signadot MCP Server yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Signadot MCP Server tools
No tool declarations could be read from the package source. They show once the server is installed.
How Signadot MCP Server compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 45% of 48,255 servers
- GitHub stars
- 8
- more than 86% of 28,688 servers
Release history: 2 versions in the registry since 2026-08-04, latest 2026-10-02, typically one every 60 days.
Install Signadot MCP Server in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Signadot MCP Server repository's README, as published. We do not edit it. Read it on GitHub
Signadot CLI
This is the source repository for the Signadot command-line interface.
Please see the CLI reference for installation and usage instructions.
To file an issue, please use our community issue tracker.
NOTE: Starting next release, and hence in the main branch, this repository has a dependency on a private repository, and hence building or running from source will not work. Previous releases should continue to work.
Install
To install the CLI, run:
curl -sSLf https://raw.githubusercontent.com/signadot/cli/main/scripts/install.sh | shBy default, the script will install the latest version at /usr/local/bin/signadot. The target version can be selected by setting the SIGNADOTCLIVERSION variable, while you can specify the install directory with SIGNADOTCLIPATH.
Build
To build the CLI from source, such as to test changes, you'll need Go 1.27.1+.
The main package is in cmd/signadot:
go build ./cmd/signadotRelease
To release the CLI, you can use the release Github action. Push a new tag that matches the format v[0-9]+.[0-9]+.[0-9] and it will push new release artifacts and update brew.
Post-release: publish to the MCP Registry
After the GitHub release artifacts are live, publish the MCP server entry manually. goreleaser does not yet support the fileSha256 integrity field required by the MCP registry for mcpb packages.
Prerequisites:
(create one here), owned by an Owner of the signadot org. Since registry#1383 the registry grants the io.github.signadot/* namespace only to org Owners, and the interactive mcp-publisher login github device flow cannot read org roles — logging in with a PAT is what makes org publishing work.
- install mcp-publisher
- a classic GitHub PAT with only the read:org scope
./scripts/gen-mcp-server-json.sh <version> # e.g. v1.8.0 — writes server.json
MCP_GITHUB_TOKEN=<pat-with-read:org> mcp-publisher login github
mcp-publisher publish server.jsonThe script writes the v-prefixed tag (e.g. v1.8.0) as the version in server.json. Don't hand-edit it to the bare form — the registry treats 1.4.0 and v1.4.0 as distinct versions, and mixing the two has created duplicate entries in the past.
This covers the official MCP registry only. For getting the MCP server listed in other directories (Claude Desktop extensions, Docker MCP Catalog, and others), see docs/mcp-distribution.md.
See Also
The CLI is built on top of the Go SDK.
The CLI is built using libconnect.
Nothing above is checked by us. What we check is on the safety report.
Signadot MCP Server: common questions
- Is Signadot MCP Server safe?
- Mostly: it is graded B (75/100). Read the Signadot MCP Server safety report
- Does Signadot MCP Server need an API key?
- Yes. The registry entry asks for
SIGNADOT_API_KEY. - Is Signadot MCP Server maintained?
- The last commit was 41 days ago (2026-09-24). The latest release is vv1.9.0.
- How does Signadot MCP Server compare with other MCP servers?
- safety score 75/100 (higher than 45% of 48,255 servers); github stars 8 (more than 86% of 28,688 servers). Full comparison.