Home / MCP registry index / com.tidybutton/migration-mapper

Migration Mapper

com.tidybutton/migration-mapper in the official MCP registry. Endpoint https://mapper.tidybutton.com/mcp.

The registry describes it as: Map an old website's URLs to the new site and get redirect rules for nginx, Apache or Cloudflare.

On 2026-11-17 this server asked for credentials before it would list its tools, so we could not read them. Nothing was checked: this is not a clean result.

Connect it

The endpoint is live and asks for credentials before it lists its tools. Add it to your client:

Claude Code
claude mcp add --transport http migration-mapper https://mapper.tidybutton.com/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "migration-mapper": {
      "url": "https://mapper.tidybutton.com/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"migration-mapper","type":"http","url":"https://mapper.tidybutton.com/mcp"}'

Most clients open the server's sign-in page the first time they connect. If it wants an API key instead, the server's own docs say where to put it.

Check its tools after you sign in

We could not read this server's tools without an account, so nothing above says they are clean. Once you are signed in, your agent can pass the tool list it received to the check_mcp_tools tool on our MCP server, which runs the same tool-poisoning rules. A free developer key covers 10 checks a day, and your agent can get one in the same session with get_free_key. No account or card.

Add Lazaretto to Claude Code
claude mcp add --transport http --scope user lazaretto "https://lazaretto.dev/mcp?ref=site"

Then ask your agent: Use Lazaretto to check the npm packages chalk@5.6.1 and chalk@5.3.0.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-tidybutton-migration-mapper/badge.svg)](https://lazaretto.dev/mcp-registry/com-tidybutton-migration-mapper)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Cloudflare MCP servers

Dados Abertos Senado BR MCP
io.github.SidneyBissoli/senado-br-mcp-cloudflare
69 tools, nothing matched
2026-11-14
Cloudflare Radar
io.github.pipeworx-io/cloudflare-radar
51 tools, nothing matched
2026-11-06
Mat Web & Data Toolkit (x402, Cloudflare)
dev.workers.matt-d59.automatom/web-data-toolkit
46 tools, nothing matched
2026-11-06
Bulk B2B Email Verifier — DNS MX, Disposable & Catch-All Check
io.github.ceadigital/email-verifier-catch-all-validator
28 tools, nothing matched
2026-11-11
falcon.sol agents
io.github.ygfalcon/falcon-sol
23 tools, nothing matched
2026-11-07
Sundogs
gs.sundo/sundogs
16 tools, nothing matched
2026-11-08