mcpbeat

siGit MCP Server

si.sigit/sigit
answering

siGit is answering right now. Last checked 15 min ago. Last commit 28 Jul 2026.

MCP server for siGit (sigit.si): browse repos, search code, manage PRs/issues, web search.

Uptime history 39 hours of history · worst hour 67%
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
397 ms
Response time
average over 24h
25
Stars
last commit 28 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add sigit --transport http https://sigit.si/api/v1/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "sigit": {
      "url": "https://sigit.si/api/v1/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.sigit]
url = "https://sigit.si/api/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sigit": {
      "url": "https://sigit.si/api/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "sigit": {
      "url": "https://sigit.si/api/v1/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://sigit.si/api/v1/mcp streamable-http needs key 2100 ms 15 min ago

siGit — questions

Answers built from our own checks of this server.

Why is there no tool list for siGit?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is siGit working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 397 ms. The bar chart above shows every period we have measured.
How do I connect siGit?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does siGit need an API key?
Yes. Every time we knock, siGit answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is siGit?
It answers our handshake in 397 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is siGit open source?
Yes — it is published under the NOASSERTION licence, written in Rust, 25 stars on GitHub and 3 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.