MCP Auth Preflight

us.inversolabsPublished by inversolabs.usOfficial publisherv0.1.19Updated Oct 24, 2026

Preflight MCP OAuth compatibility with structured evidence and remediation guidance.

The publisher's own server: Agent Callback Mailbox

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that checks OAuth compatibility for MCP servers and returns structured evidence with remediation guidance.

What you can do
  • Run preflight checks of MCP OAuth compatibility against a target server.
  • Review structured evidence produced by those checks.
  • Read remediation guidance for issues the checks surface.
  • No individual tools are listed in the manifest, so the exact operations are not documented.
When to use it
Useful when setting up or debugging OAuth-protected MCP servers and you want a quick compatibility check with concrete findings before wiring clients to them.
Requirements
A remote streamable HTTP endpoint at auth.inversolabs.us; no packages, environment variables or headers are declared. The manifest declares no authentication, though the service itself concerns OAuth.
Before you install
The manifest lists no tools, so what the checks do with the target server's details is undocumented. Avoid submitting client secrets, tokens or private keys unless you know how they are handled, and confirm what is sent to this third-party service.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. 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/us.inversolabs%2Fmcp-auth-preflight/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-preflight": {
      "type": "http",
      "url": "https://auth.inversolabs.us/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v0.1.19LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.

Other Inversolabs integrations