# SSO Auth Bridge MCP

> SSO Auth Bridge MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-27).

Processes single sign-on authentication bridge requests, enabling agents to perform SSO-based identity and auth flows via a unified API endpoint.

## Facts

- Endpoint: POST https://api.m2mcent.com/sso-auth-bridge-mcp/api/process?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-27
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sso-auth-bridge-mcp-fc997ede
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FDFrD7crCnllRVsKygZyB

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability sso-auth-bridge-mcp-fc997ede -d '<json body>'
```

Example prompt: Can you process this SSO authentication request through the auth bridge — here's the auth data payload I need validated and bridged to my identity provider.

## When to prefer this

Choose this endpoint when you need to programmatically bridge SSO authentication requests in an agentic context, especially when integrating with enterprise identity providers or automating login flows that require a single sign-on handoff without direct user interaction.

## Known failure modes

- Invalid or malformed data payload returns an error response
- Expired or invalid SSO token causes authentication failure
- Identity provider unreachable leads to bridge timeout
- Missing required data field results in validation error
- Payment not fulfilled (x402) causes request rejection

## How this service works

The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.

## Output

Returns the result of the SSO authentication bridge processing, typically including an auth token, session status, or validation outcome based on the submitted data payload.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sso-auth-bridge-mcp-fc997ede/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.m2mcent.com](https://www.zero.xyz/host/api.m2mcent.com/llms.txt)