Latchkey MCP Server

by that-developer-kaveh Your server? Claim it

answering

Latchkey is answering right now. Last checked 3 min ago.

Triage failing GitHub Actions jobs and see what self-heal repaired, in natural language.

Uptime history 5 days of history

5 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

351 ms

Response time

average over 24h

API key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Latchkey every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add latchkey --transport http https://latchkey.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "latchkey": {
      "url": "https://latchkey.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.latchkey]
url = "https://latchkey.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "latchkey": {
      "url": "https://latchkey.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "latchkey": {
      "url": "https://latchkey.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://latchkey.dev/mcp	streamable-http	needs key	209 ms	3 min ago

Alternatives to Latchkey

same job, measured the same way

I18n Agent Action

by samyuan1990

An i18n github action for language translate

local only

Github Actions

by ofershap

GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD.

37 installs/wk local only

GitHub

by github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

answering

Reportcraft

by rharper105

Generate Splunk dashboards, reports, and alerts from natural language. No API key required.

26 installs/wk local only

MCP Github Organization Signal Scanner

by mambabuilt

Resolve a company domain to its GitHub organization with repo, language and activity signals.

35 installs/wk local only

Github Repo MCP

by thedhruv-07

MCP server for GitHub repo health, commit summaries, issue triage, and RAG Q&A.

143 installs/wk local only

Hotin

by abe238

What's hot in AI right now, ranked with receipts from GitHub, HN, npm and Hugging Face.

2 710 installs/wk local only

Dep Diff MCP

by digicatalyst-systems

Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions.

165 installs/wk 2 tools answering

Latchkey — questions

Answers built from our own checks of this server.

Why is there no tool list for Latchkey?

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 Latchkey working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 351 ms. The bar chart above shows every period we have measured.

How do I connect Latchkey?

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: it refuses anonymous clients.

Does Latchkey need an API key?

Yes. Every time we knock, Latchkey 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 Latchkey?

It answers our handshake in 351 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.