SSO Auth Bridge MCP Server

by evozim Your server? Claim it

answering

SSO Auth Bridge is answering right now. Last checked 8 min ago.

SAML and OIDC authentication integration orchestrator.

Uptime history 47 days of history · worst day 99%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

93 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

Today is the operative word: we check SSO Auth Bridge every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add sso-auth-bridge --transport http https://sso-auth-bridge-mcp.vercel.app/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "sso-auth-bridge": {
      "url": "https://sso-auth-bridge-mcp.vercel.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.sso-auth-bridge]
url = "https://sso-auth-bridge-mcp.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "sso-auth-bridge": {
      "url": "https://sso-auth-bridge-mcp.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "sso-auth-bridge": {
      "url": "https://sso-auth-bridge-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://sso-auth-bridge-mcp.vercel.app/api/mcp	sse	needs auth	93 ms	8 min ago

Alternatives to SSO Auth Bridge

same job, measured the same way

Laviya Agent Skills

by kartegagithub

Laviya AI Orchestration MCP runtime for IDE and agent integrations.

61 installs/wk local only

Ruv Swarm

by ruvnet

Neural network swarm orchestration with WebAssembly acceleration and MCP integration

4 025 installs/wk local only

LLM Orchestration Agent D0a1a1

by getvda

LLM Orchestration Agent

2 tools answering

LLM Orchestration Agent 2 Df5979

by getvda

LLM Orchestration Agent 2

2 tools answering

LLM Orchestration Agent Langsmith

by getvda

LLM Orchestration Agent (Langsmith)

2 tools answering

LLM Orchestration Agent Langgraph

by getvda

LLM Orchestration Agent (Langgraph)

2 tools answering

Agentled

by agentled

Intelligent AI workflow orchestration with long-term memory, 100+ integrations, and unified credits.

279 installs/wk local only

LLM Orchestration JWT Agent

by getvda

LLM Orchestration JWT Agent

2 tools answering

SSO Auth Bridge — questions

Answers built from our own checks of this server.

Why is there no tool list for SSO Auth Bridge?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is SSO Auth Bridge working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 93 ms. The bar chart above shows every period we have measured.

How do I connect SSO Auth Bridge?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does SSO Auth Bridge need an API key?

Yes. Every time we knock, SSO Auth Bridge answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is SSO Auth Bridge?

It answers our handshake in 93 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.