Not verified. No source names an endpoint for Plane; the connector tried mcp.plane.so as a guess and it did not answer a handshake on 4 November 2026, so nothing is counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8).
78, grade B; Ora scanned the domain on 18 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for plane.so, a vendor-published score)
Company found through
Ora's public leaderboard
Last verified
4 November 2026
MCP server
Endpoint
https://mcp.plane.so/mcp
How it was found
mcp.plane.so was tried as a guess and did not answer
HTTP status
404
Connected
4 November 2026, 20:04 UTC
Handshake time
949 ms over 2 attempts
Result
no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8)
Connector log
2 connections on 4 November 2026, read-only methods only
19:58:53Z https://mcp.plane.so/mcp sent initialize result no-answer (HTTP 404) 980 ms
20:04:02Z https://mcp.plane.so/mcp sent initialize result no-answer (HTTP 404) 949 ms
Authentication
Auth type
Auth not determined
The sign-in route, step by step
Request https://mcp.plane.so/mcp. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 text/plain; charset=utf-8).
Check the vendor's docs for the sign-in route before wiring a client.
No CLI is on record for Plane. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.