Nifra docs MCP Server

What the code does

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

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

        return { contents: readFileSync(args.path, "utf8"), loader: "js" }

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.

  "^AKIAABCDEFGHIJKLMNOP$",

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.

  exec(
    command: string,

  for (const insert of inserts) {
    out += shell.slice(from, insert.at) + insert.html

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 11 min ago.

claude mcp add nifra-docs --transport http https://mcp.nifra.dev

https://mcp.nifra.dev

[mcp_servers.nifra-docs]
url = "https://mcp.nifra.dev"

{
  "mcpServers": {
    "nifra-docs": {
      "url": "https://mcp.nifra.dev"
    }
  }
}

{
  "servers": {
    "nifra-docs": {
      "type": "http",
      "url": "https://mcp.nifra.dev"
    }
  }
}

Available tools 7

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

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

Endpoints