siGit
MCP server for siGit (sigit.si): browse repos, search code, manage PRs/issues, web search.
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://sigit.si/api/v1/mcp | registry |
|---|---|---|
| Website | sigit.si | registry |
| Handshake | Answers, but requires sign-in before the handshake (609 ms) | our check, 2026-11-18 |
| GitHub stars | 6 | github.com/getsigit/si |
| Last push | 2026-11-09 | GitHub API |
| Registry version | 1.2.5 · active · updated 2026-10-28 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
claude mcp add --transport http sigit https://sigit.si/api/v1/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- siGit CLI Run sigit.si locally: browse repos, search code, manage PRs, issues, and Cloud Sessions.
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/si.sigit/sigit)<a href="https://openforallofus.com/tools/si.sigit/sigit"><img src="https://openforallofus.com/badge/si.sigit/sigit.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name si.sigit/sigit.