SISA is answering right now. Last checked 8 min ago.
SISA（現場のインシデント対応）を AI エージェントから使う: 対応中のインシデント・月ごとの件数・傾向分析を聞く／公開 API の仕様を正確に読ませる。
Uptime history
70 hours of history · worst hour 75%
70 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
911 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http
SISA missed one check this week
Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.
run in your terminal
claude mcp add mcp --transport http https://mcp.sisa.jp/mcpSettings → Connectors → Add custom connector, then paste this address
https://mcp.sisa.jp/mcp~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.sisa.jp/mcp".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.sisa.jp/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.sisa.jp/mcp"
}
}
}This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.sisa.jp/mcp | streamable-http | sign-in | 866 ms | 8 min ago |
SISA — questions
Answers built from our own checks of this server.
Why is there no tool list for SISA?
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 SISA 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 911 ms. The bar chart above shows every period we have measured.
How do I connect SISA?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to SISA?
No API key is involved. SISA answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is SISA?
It answers our handshake in 911 ms on average, which is faster than 7% 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.