Legacy-Code-Migrator MCP Server

by evozim Your server? Claim it

answering

Legacy-Code-Migrator is answering right now. Last checked 15 min ago.

Automated code modernizer converting legacy logic to ESNext.

Uptime history 48 days of history · worst day 99%

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

91 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

Today is the operative word: we check Legacy-Code-Migrator 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 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add legacy-migrator --transport http https://legacy-migrator-mcp.vercel.app/api/mcp

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

{
  "mcpServers": {
    "legacy-migrator": {
      "url": "https://legacy-migrator-mcp.vercel.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.legacy-migrator]
url = "https://legacy-migrator-mcp.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "legacy-migrator": {
      "url": "https://legacy-migrator-mcp.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "legacy-migrator": {
      "url": "https://legacy-migrator-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://legacy-migrator-mcp.vercel.app/api/mcp	sse	needs auth	96 ms	15 min ago

Alternatives to Legacy-Code-Migrator

same job, measured the same way

Stack Trace Medic

by evozim

Coded error stack trace debugger and automated patch generator.

answering

MCP Aider Executor

by railkill

Model Context Protocol (MCP) server to execute aider-specific code editing operations

38 installs/wk local only

MCP Bifrost

by fixembcn

Delegate bulk code edits to a cheap worker model. Gated, atomic. PHP and Python.

176 installs/wk local only

Toon Parse MCP

by ankitpal181

MCP server that reduces LLM context by removing code comments and converting data formats to TOON

56 installs/wk local only

CleanCode AI

by evozim

Automated codebase refactoring and type safety validator.

answering

RoselineMCP

by atypical-consulting

MCP server for C# code analysis and automated fixing using Roslyn analyzers and code fix providers.

local only

GitHub to MCP Converter

by nirholas

Convert any GitHub repo to MCP server - automatic tool generation API wrap

local only

Context — ctxt.io

by ctxt

Share text, markdown, code, or HTML as auto-expiring links

3 tools answering

Legacy-Code-Migrator — questions

Answers built from our own checks of this server.

Why is there no tool list for Legacy-Code-Migrator?

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 Legacy-Code-Migrator 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 91 ms. The bar chart above shows every period we have measured.

How do I connect Legacy-Code-Migrator?

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

Does Legacy-Code-Migrator need an API key?

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

It answers our handshake in 91 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.