SSO Auth Bridge

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

SAML and OIDC authentication integration orchestrator.

VerifiedSSEWeb executableSecurity & Monitoring

Overview

AI-generated overview

An authentication bridge that orchestrates SAML and OIDC sign-in flows for an assistant.

What you can do
SSO Auth Bridge is a remote MCP endpoint described as a SAML and OIDC authentication integration orchestrator. It is meant to coordinate single sign-on authentication between systems rather than to expose a documented set of tools; no tool list is published in the manifest. It is reached over an SSE connection to a hosted endpoint.
When to use it
Consider it when an assistant needs to work with SAML or OIDC single sign-on integrations and you want that handled by a hosted service instead of building the flow yourself. Because no tools are documented, verify the actual capabilities before relying on it.
Requirements
A remote SSE connection to the hosted endpoint; no local package or runtime is declared. The manifest declares a payment-signature header, described as a Base64-encoded EIP-3009 TransferWithAuthorization signature, required for premium settlement. No accounts, environment variables, or other credentials are declared.
Before you install
The only declared credential is the payment-signature header, an EIP-3009 TransferWithAuthorization signature, which authorizes a token transfer and can move funds if misused; treat it as spending authority and never share it. The service is remote, so authentication data passes to a third party, and no tool list or README is available to confirm what it does with that data.

Installation

In SourceWeft

  1. Open SSO Auth Bridge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fsso-auth-bridge/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.