Skip to content
Pilot-Next logo

Pilot-Next MCP server

Which MCP servers are Pilot-Next's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to Pilot-Next

Whose server it is
  • Registry namecom.pilot-next/pilot-nextverified in the MCP registry

The registry name sits under pilot-next.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19
  • Staterequires sign-inchecked 2026-10-19

On 2026-10-19 the server answered and asked for a sign-in with a Pilot-Next account (OAuth). It shows its tool list only to signed-in users, so we list none here.

Should an agent connect itNot proven either way yet

    Once connected

    • Signs in by OAuth: the client opens the sign-in on first connect.

    Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

    Measured dailydaily checks: 16, the first on 2026-10-19
    • INITE MCP score100 of 100answers 100 · connects 100
    • Answered100% of days16 of 16 daily checks
    • Median first answer478 ms
    • Sign-inOAuth: the client signs you inclients register themselves: claude.ai and ChatGPT connect with nothing set up first

    A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

    How to connect

    Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

    {
  "mcpServers": {
    "pilot-next": {
      "type": "http",
      "url": "https://pilot-next-backend.onrender.com/mcp"
    }
  }
}

    Add it

    Claude Code, in a terminal

    claude mcp add --transport http pilot-next https://pilot-next-backend.onrender.com/mcp

    Add to CursorAdd to VS Code

    claude.ai, ChatGPT and other clients: add https://pilot-next-backend.onrender.com/mcp as a custom connector in the settings.

    The first time it connects, the client opens a Pilot-Next sign-in.

    Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.