Leadpages: MCP server, CLI and agent surfaces
Sign-in required, tools not seen, not counted. The MCP endpoint listed for Leadpages at mcp.leadpages.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.
Fact sheet
| Company | Leadpages (registry title: leadpages.com) |
|---|---|
| Domain | leadpages.com |
| Category | Marketing (Ora leaderboard category) |
| MCP server | Sign-in required (OAuth with client registration) |
| Ora score | 80, grade B; Ora scanned the domain on 19 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for leadpages.com, a vendor-published score) |
| Company found through | Ora's public leaderboard |
| Last verified | 4 November 2026 |
MCP server
| Endpoint | https://mcp.leadpages.com/mcp |
|---|---|
| How it was found | listed in Ora's public leaderboard |
| Transport | streamable-http |
| HTTP status | 401 |
| Connected | 4 November 2026, 20:03 UTC |
| Handshake time | 1,214 ms over 1 attempt |
The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.
Connector log
2 connections on 4 November 2026, read-only methods only
- 19:58:10Z https://mcp.leadpages.com/mcp sent initialize result auth-required (HTTP 401) 1255 ms
- 20:03:30Z https://mcp.leadpages.com/mcp sent initialize result auth-required (HTTP 401) 1214 ms
Authentication
| Auth type | OAuth with client registration |
|---|---|
| What the challenge said | Bearer resource_metadata="https://mcp.leadpages.com/.well-known/oauth-protected-resource/mcp" |
| Protected resource metadata | mcp.leadpages.com |
| Authorization server metadata | mcp.leadpages.com |
| Registration endpoint | https://mcp.leadpages.com/api/mcp/oauth/register |
The sign-in route, step by step
- Request
https://mcp.leadpages.com/mcpwithout a token. It answers 401 and aWWW-Authenticateheader. - Read the protected resource metadata at
https://mcp.leadpages.com/.well-known/oauth-protected-resource/mcpto find the authorization server. - Register a client at the registration endpoint
https://mcp.leadpages.com/api/mcp/oauth/register(dynamic client registration), so no human has to create an app first. - Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.
See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.
CLI
No CLI is on record for Leadpages. 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.
Other agent surfaces
| Surface | Result |
|---|---|
| OpenAPI file | Found: leadpages.com (JSON, via a direct request). |
| WebMCP in the initial HTML | Not detected on the home page by the shared crawl. |
| MCP discovery file | Not found (the crawl got a non-200 answer). |
| A2A agent card | Found: leadpages.com/.well-known/agent-card.json answered with a valid document in the shared crawl. |
| A2A agent card (older path) | Not found (the crawl got a non-200 answer). |
| agents.json | Not found (the crawl got a non-200 answer). |
| OAuth authorization server metadata | Found: leadpages.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. |
| NLWeb endpoint | Not checked in this edition. |
Registry listings
| Registry | Listed |
|---|---|
| Official MCP Registry | Yes: com.leadpages/leadpages-mcp |
| GitHub MCP Registry | No |
| awesome-remote-mcp-servers | No |
| Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. |
| Glama | Not checked: Glama's API needs a key and attribution terms. |