Stripe: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Stripe at mcp.stripe.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	Stripe
Domain	stripe.com
Category	Payments & Fintech (Ora leaderboard category)
MCP server	Sign-in required (OAuth with client registration)
Tranco rank	205 on the list of 4 November 2026
Ora score	74, grade B; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for stripe.com, a vendor-published score)
Company found through	the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard
Last verified	4 November 2026

MCP server

Endpoint	`https://mcp.stripe.com`
How it was found	listed in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard
Transport	streamable-http
HTTP status	401
Connected	4 November 2026, 20:06 UTC
Handshake time	1,083 ms over 1 attempt
Documentation	docs.stripe.com

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

3 connections on 4 November 2026, read-only methods only

19:55:53Z https://mcp.stripe.com sent initialize result auth-required (HTTP 401) 1027 ms
20:01:28Z https://mcp.stripe.com sent initialize result auth-required (HTTP 401) 1052 ms
20:06:07Z https://mcp.stripe.com sent initialize result auth-required (HTTP 401) 1083 ms

Authentication

Auth type	OAuth with client registration
What the challenge said	`Bearer resource_metadata="https://mcp.stripe.com/.well-known/oauth-protected-resource"`
Protected resource metadata	mcp.stripe.com
Authorization server metadata	access.stripe.com
Registration endpoint	`https://access.stripe.com/mcp/oauth2/register`
Auth as listed by a registry	OAuth2.1 API Key (a claim, not checked by connecting)

The sign-in route, step by step

Request https://mcp.stripe.com without a token. It answers 401 and a WWW-Authenticate header.
Read the protected resource metadata at https://mcp.stripe.com/.well-known/oauth-protected-resource to find the authorization server.
Register a client at the registration endpoint https://access.stripe.com/mcp/oauth2/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 Stripe. 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

Agent surfaces other than MCP and CLI
Surface	Result
OpenAPI file	Found: raw.githubusercontent.com (JSON, via vendor docs).
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	Not found (the crawl got a non-200 answer).
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	Not found (the crawl got a non-200 answer).
NLWeb endpoint	Not checked in this edition.

Registry listings

Registry listings
Registry	Listed
Official MCP Registry	Yes: com.stripe/mcp
GitHub MCP Registry	Yes
awesome-remote-mcp-servers	Yes
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.