com.textforagents/mcp-oauth-remediation-verification
MCP OAuth remediation verification
Is the MCP OAuth remediation verification MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Three-leg MCP OAuth remediation verdicts, proven behaviourally against a canary server.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401
Streamable HTTP error: Error POSTing to endpoint: {"error": "unauthorized \u2014 register at POST /register to get a token, then send it as a Bearer token"}- Endpoint
- https://textforagents.com/products/mcp-oauth-remediation-verification/mcp (streamable-http)
- Host
- textforagents.com
- Getting access
- The server answers HTTP 401 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://textforagents.com/products/mcp-oauth-remediation-verification/
- Registry
- active, updated 2026-10-22 · registry entry
Compare this server with others.
More servers
Other registry entries on textforagents.com, the ones next to this name; all of them.
- Matchmaking rating for agent selection com.textforagents/matchmaking-rating-for-agent-selection · alive
- MCP answer-quality canary com.textforagents/mcp-answer-quality-canary · needs auth
- MCP host-behaviour census com.textforagents/mcp-host-behaviour-census · alive
- MCP OAuth client-interop conformance com.textforagents/mcp-oauth-client-interop-conformance · alive
- Meaning Contract com.textforagents/meaning-contract-semantic-handshake · alive
- Minimum Equipment List dispatch for agents com.textforagents/minimum-equipment-list-dispatch · needs auth
- Moneyless clearinghouse: barter netting for agent services com.textforagents/moneyless-clearinghouse-barter-netting · alive
- Namespace guard for merged toolboxes com.textforagents/namespace-guard-for-merged-toolboxes · alive
Servers that mention verification.
- ai.atlasverified/atlas-mcp · needs auth
- DeployIt Product Expert ai.deployit/product-expert · alive
- ai.facesign/facesign-mcp · alive
- Human4AI Human Task Network ai.human4ai/collaboration · alive
- Licensy ai.licensy/mcp-server · needs auth
- ScamVerify Threat Verification ai.scamverify/mcp · no DNS
- ai.tachyo/tachyo · alive
- Sigil ai.tunnelmind/sigil · not found
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.