Auth-Sentinel

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

SSO identity auditor protecting SAML and OpenID configurations.

VerifiedSSEWeb executableSecurity & Monitoring

Overview

AI-generated overview

Audits SSO identity configurations, checking SAML and OpenID Connect setups for security issues.

What you can do
Auth-Sentinel is a remote MCP server that acts as an SSO identity auditor, focused on SAML and OpenID configurations. It lets an assistant inspect and review single sign-on identity settings for weaknesses. No tool list is published, so the exact operations available are not documented.
When to use it
Consider it when you maintain SAML or OpenID Connect single sign-on and want an assistant to help audit those identity configurations. It is less useful if you do not manage SSO or identity provider settings.
Requirements
A remote SSE endpoint; no local package or runtime is needed. The manifest declares no authentication and no environment variables, but a payment-signature header is listed as a secret, described as required for premium settlement.
Before you install
The server asks for a payment-signature header, a Base64-encoded EIP-3009 TransferWithAuthorization signature, which is a payment authorization credential; treat it as sensitive and be aware that using it may move funds. The endpoint is third-party hosted, so identity configuration data you send leaves your environment. No tool list is published, so review behavior before use.

Installation

In SourceWeft

  1. Open Auth-Sentinel 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%2Fauth-sentinel/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": {
    "auth-sentinel": {
      "type": "sse",
      "url": "https://auth-sentinel-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.