mcpbeat

Sekichi MCP Server

io.github.surp-renz/sekichi
answering

Sekichi is answering right now. Last checked 4 min ago.

Knowledge accumulation for AI coding agents. Records decisions, problems, and insights as context.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 40 hours of history · worst hour 67%
40 hours agonow
98.9%
Uptime 24h
90 of 91 checks
—
Tools
hidden behind auth
1925 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add sekichi --transport http https://sekichi.fly.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "sekichi": {
      "url": "https://sekichi.fly.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.sekichi]
url = "https://sekichi.fly.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sekichi": {
      "url": "https://sekichi.fly.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "sekichi": {
      "url": "https://sekichi.fly.dev/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://sekichi.fly.dev/mcp streamable-http needs key 433 ms 4 min ago

Sekichi — questions

Answers built from our own checks of this server.

Why is there no tool list for Sekichi?
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: 98.9% of checks in the last 24 hours got a reply.
Is Sekichi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 1925 ms. The bar chart above shows every period we have measured.
Is Sekichi still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Sekichi?
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 Sekichi need an API key?
Yes. Every time we knock, Sekichi 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 Sekichi?
It answers our handshake in 1925 ms on average, which is faster than 1% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.