What Talandor observed
Mcp
https://mcp.stripe.com/
Authentication required
Authentication required
Server checked October 28
Finish Mcp sign-in with the provider from your assistant. This is not an outage.
- Address availability
- Reachable
- HTTP 401 was received.
- MCP protocol
- Not verified
- HTTP 401 does not establish an MCP exchange.
- Public tools
- Blocked by authentication
- The public tool list was not read. This is not an outage.
Use in your assistant: not verified · authentication details
- Authentication
- Required
- Public OAuth metadata found: protected resource metadata URL; authorization servers: https://access.stripe.com/mcp; scopes: mcp. A full OAuth sign-in was not tested.
- Your assistant
- Not verified
- Talandor does not check the local setup in Cursor, ChatGPT, Claude, or Windsurf. Private tools were not verified. No tool call was executed.
What should I do next?
Still blocked in your assistant? Diagnose the symptom →
- Add the connector to your assistant
Open the configuration guide below. Keep your existing connectors when adding this one.
- Finish signing in to the provider
If your assistant asks you to sign in, finish that step there and check the access you grant. Never paste credentials into Talandor.
- Check that the tools appear
Open the connector in your assistant and check its available tools. Talandor has not tested that connection or executed those tools.
The tools still do not appear?
These are checks you can carry out. A public result does not identify a fault in your assistant.
- Check your client's MCP support
Check your client's documentation for support of this remote HTTP endpoint and how to enable its tools. Local-server and remote-server configuration can differ.
- Check provider access
If sign-in is requested, check the account and permissions in the assistant. An accessible public endpoint does not establish access to private tools.
- Read the error shown by the assistant
Compare its configured address with this report, then use the provider's or assistant's official help. If you contact Talandor, share the error with tokens and private data removed.
Sign-in information is consistent.
Continue setting up your assistant to finish connecting to Mcp.
The actual connection in your assistant remains unverified.
View technical details
Only public discovery documents were read. No account, client registration, token exchange or complete OAuth login was tested.
- Resource metadata
- Read and matched to this address
- Authorization server
- 1 public document validated
- Client registration
- Dynamic registration announced
- Dynamic registration is optional. If it is not announced, the provider may use client metadata documents or pre-registration. Its absence is not itself an outage.
Declared issuer : https://access.stripe.com/mcp
Document inspected : https://access.stripe.com/.well-known/oauth-authorization-server/mcp
Check details
Official Registry
Official Registry · com.stripe/mcp · Publisher namespace: com.stripe
What changed
This public check is complete. There is no public tools contract to diff. Surface Watch can follow the authentication challenge.
Tools and declared exposure
Server annotations are declarations, not verified behavior.
Evidence and limitations
Method: anonymous Streamable HTTP probe. We never invoke a tool.
Attempted protocols: 2026-07-28
OAuth metadata: https://access.stripe.com/mcp
AUTH_REQUIRED — The endpoint requires authentication; no credentials were used.
Observation history
No snapshots have been stored yet.
Deep monitoring eligibility
Surface Watch eligible
This authentication-surface result is a complete public check. Deep tool-contract diffs need a public tools/list; Surface Watch can follow the sign-in challenge.
A Watch starts from the payment section on this page, and only after a verified payment.
See public monitoringWatch this MCP
Optional. Setting up the connector does not require Watch.
Authentication-surface coverage: Availability, TLS, protocol and public authentication-surface changes can be compared; private tools are not included.
Early access currently activates this first endpoint; adding more endpoints up to the planned limit of five is not open in this deployment. Live checkout is open. A Watch activates only after a verified payment event; a browser return never starts monitoring.
Start Watch