Altscan explorers MCP Server

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

    const v = (await (await redis()).eval(TAKE, 1, `oauth:code:${code}`)) as string | null

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const v = (await (await redis()).eval(TAKE, 1, `oauth:code:${code}`)) as string | null

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

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

claude mcp add explorers --transport http https://altscan.io/mcp

https://altscan.io/mcp

[mcp_servers.explorers]
url = "https://altscan.io/mcp"

{
  "mcpServers": {
    "explorers": {
      "url": "https://altscan.io/mcp"
    }
  }
}

{
  "servers": {
    "explorers": {
      "type": "http",
      "url": "https://altscan.io/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints