ToolsMCP
siGit CLI
Listed in the official MCP Registry with an installable cargo package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- sigit.si
- Prerequisites
- Install sigit-si-cli from cargo (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.3.1 · updated
- Official links
Publisher’s description
Run sigit.si locally: browse repos, search code, manage PRs, issues, and Cloud Sessions.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.3.1, registry status active. 1 package (cargo)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- sigit.si
- Version observed
- 1.3.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/si.sigit%2Fcli/versions/1.3.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Work with issues and pull requests | Publisher description mentions “repos”, “prs”, “issues”. | No connection check or task run. Capability is as described by the publisher. | Rule code-repositories matched: “repos”, “prs”, “issues”. Rule code-repositories. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
sigit-si-cli(cargo, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
si.sigit/cli
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.