MCP OAuth remediation verification

com.textforagentsPublished by textforagents.comOfficial publisherv1.0.0Updated Oct 26, 2026

Three-leg MCP OAuth remediation verdicts, proven behaviourally against a canary server.

The publisher's own server: Agent NOTAMs: hazard bulletins for agents

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that returns three-leg OAuth remediation verdicts for MCP servers, checked behaviourally against a canary server.

What you can do
  • Produces OAuth remediation verdicts for MCP servers, structured as three legs.
  • Verifies behaviour against a canary server rather than relying on configuration claims.
  • No tool list is published, so the exact operations an assistant can call are not documented in the supplied material.
When to use it
Useful when you need to confirm whether an MCP server's OAuth setup has actually been remediated, and want a behavioural check rather than a static review.
Requirements
A remote streamable HTTP endpoint at the provider's site; OAuth authentication is required. No environment variables or headers are declared.
Before you install
OAuth access is required, so the provider receives identity and authorization data. The tool set is undocumented, so what the server can read or change is unclear before connecting.

Installation

In SourceWeft

  1. Open MCP OAuth remediation verification in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/com.textforagents%2Fmcp-oauth-remediation-verification/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "oauth-remediation-verification": {
      "type": "http",
      "url": "https://textforagents.com/products/mcp-oauth-remediation-verification/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 22, 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 listed15 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.

Other Textforagents integrations