MCP.Market

Pilot5 MCP server

online · 100% uptime
by pilot5.ai·ai.pilot5/pilot5·v1.0.1
No reviews yet

Five AI models debate your decision blind, then give one recommendation and the strongest objection.

A97/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Pilot5 yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pilot5 tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-26 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 180ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Pilot5 compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
260 ms
faster than 54% of 30,031 servers

Release history: 2 versions in the registry since 2026-10-19, latest 2026-10-26, typically one every 7 days.

Install Pilot5 in Claude Code, Cursor or VS Code

claude mcp add --transport http pilot5 https://mcp.pilot5.ai/mcp
Add to Cursor

What the publisher says

From the Pilot5 repository's README, as published. We do not edit it. Read it on GitHub

Pilot5 MCP server

Pilot5 runs a panel of AI models from different providers on a decision and returns one recommendation, with its sources and the strongest counter-argument.

This repository holds connection details only. Pilot5 is a hosted service; there is nothing to install or run.

  • Server URL: https://mcp.pilot5.ai/mcp (Streamable HTTP)
  • Sign-in: OAuth 2.1 with Dynamic Client Registration. Your client registers itself and opens the Pilot5 sign-in; there is no key to paste.
  • Account: sign up at pilot5.ai. Runs use credits from your Pilot5 account.
  • MCP Registry name: ai.pilot5/pilot5

Modes

  • The Expert: one model, 1-2 minutes.
  • The A-Team: five models, 10-20 minutes. It can stop once after Round 1 to ask you one detail.
  • The Dream Team: five models. It pauses after every round so you can steer.

Before The A-Team or The Dream Team starts, you see the question exactly as the panel will receive it. The run starts only when you confirm.

Connect

Step-by-step instructions for Claude, ChatGPT, VS Code, Perplexity and Le Chat: pilot5.ai/docs/mcp.

Support

support@pilot5.ai · Privacy · Terms

Pilot5 is operated by Pilot5 Inc.

This license covers the files in this repository (connection configuration and documentation). It does not cover the Pilot5 service, which is provided under the Pilot5 Terms of Service: https://pilot5.ai/terms

Nothing above is checked by us. What we check is on the safety report.

Pilot5: common questions

Is Pilot5 MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Pilot5 safety report
How do I install Pilot5?
It runs remotely at mcp.pilot5.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Pilot5 need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Pilot5 maintained?
The last commit was 9 days ago (2026-10-26). The latest release is v1.0.1.
Is Pilot5 up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Pilot5 compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 260 ms (faster than 54% of 30,031 servers). Full comparison.