Developer · Remote MCP server

Latchkey

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

Visit Latchkey's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.that-developer-kaveh/latchkey
Version
1.0.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-09-14
Updated
2026-09-14
Publisher
that-developer-kaveh (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/that-developer-kaveh) · how
Listed under
GitHub MCP servers, GitHub Actions MCP servers
Website
latchkey.dev
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://latchkey.dev/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; a Bearer token is asked for
Checked on
2026-10-05

How the live check works

How to connect Latchkey

Latchkey is a remote MCP server: there is nothing to install. Its endpoint is https://latchkey.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Langfuse APILangfuse public API (Cloud and self-hosted): traces, prompts, datasets and gated writes.Local · stdionpm: langfuse-api-mcp
LastestRun visual regression tests, review diffs, and manage baselines on a Lastest instance.Local · stdionpm: @lastest/mcp-server
LastPingMonitoring that agents set up for themselves: cron jobs, CI/CD pipelines and AI agent runs.Remote · HTTPLive check: sign-in requiredmcp.lastping.dev
lastseen mortalityCheck whether an npm package, GitHub Action, MCP server or Docker image is dead or abandoned.Local · stdioPyPI: lastseen-mcp
LatentGateRead large logs, JSON and docs in a fraction of the tokens. Offline, fact-preserving optimizer.Local · stdioPyPI: latent-gate
Latex MCPEnable AI agents to compile TeX files with LaTeX inside a Docker container.Local · stdioPyPI: latex-mcp
Latex Submission LintSeventeen rules on your.tex file: the statements the editorial office looks for, and the source tha.Local · stdionpm: @readystack/latex-submission-lint
LatgalianGrounds LLMs in real Latgalian: Wiktionary lemmas, inflections, romanization.Remote · HTTPLive check: ✓ handshakelatgalian.valksor.com