Chipp Legacy code MCP Server

by chipp Your server? Claim it

answering

Chipp Legacy code is answering right now. Last checked 8 min ago.

Chipp: the code of an app being rebuilt: the imported GitHub repo and the legacy codebase

Uptime history 6 days of history

6 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

476 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Chipp Legacy code 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 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add chipp-legacy-code --transport http https://mcp.chipp.ai/mcp/legacy-code

Settings → Connectors → Add custom connector, then paste this address

https://mcp.chipp.ai/mcp/legacy-code

~/.codex/config.toml

[mcp_servers.chipp-legacy-code]
url = "https://mcp.chipp.ai/mcp/legacy-code"

.cursor/mcp.json

{
  "mcpServers": {
    "chipp-legacy-code": {
      "url": "https://mcp.chipp.ai/mcp/legacy-code"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "chipp-legacy-code": {
      "type": "http",
      "url": "https://mcp.chipp.ai/mcp/legacy-code"
    }
  }
}

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.chipp.ai/mcp/legacy-code	streamable-http	sign-in	421 ms	8 min ago

Alternatives to Chipp Legacy code

same job, measured the same way

Sexai MCP

by sexai

The network where AI agents breed — publish, import a GitHub repo as an agent, cross them.

134 installs/wk local only

Repo Memory

by yubinkim444

Shared, git-tracked working memory for AI agents on the same codebase.

135 installs/wk local only

Gread

by nitrorcr

An MCP server that gives your AI access to the source code and docs of all public github repos

5 tools answering

Samebase

by samebase

Build and manage repository-backed web apps with Samebase, GitHub, Convex, and Cloudflare.

answering

Github

by davidweb3-ctrl

GitHub MCP Server - List PRs, issues, repo info, and search code

34 installs/wk local only

Delphi Code

by markdorof

Let coding agents browse code across all your local, GitHub and Bitbucket repos, offline

349 installs/wk local only

Github MCP

by mrfentmen

Query the GitHub REST API: profile, repos, repo details, code search.

820 installs/wk local only

Myopic

by surajkgoyal

Code-review MCP: review a GitLab MR or GitHub PR against the whole codebase, not just the diff.

80 installs/wk local only

Chipp Legacy code — questions

Answers built from our own checks of this server.

Why is there no tool list for Chipp Legacy code?

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 Chipp Legacy code 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 476 ms. The bar chart above shows every period we have measured.

How do I connect Chipp Legacy code?

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 Chipp Legacy code?

No API key is involved. Chipp Legacy code 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 Chipp Legacy code?

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