MCP OAuth client-interop conformance

by FastDrop

MCP MCP VERIFIED Verified 3 hours ago Registry import free

Prove real MCP clients can connect: 5-client x 3-IdP OAuth matrix with shim fixes.

Prove real MCP clients can connect: 5-client x 3-IdP OAuth matrix with shim fixes. Official MCP Registry: com.textforagents/mcp-oauth-client-interop-conformance@1.0.0. Remote endpoint: https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.textforagents/mcp-oauth-client-interop-conformance and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 28 Oct 2026. Not supplied by the maker.

conformance_check
run one full client x IdP-shape conformance matrix (the POST /check operation; x402 $0.01 per check unless your account has an active Solo subscription/trial, metered exactly as REST)
claim_trial
claim the one-time free first Solo month for your first server (the POST /trial/claim operation; Bearer token required)
subscribe_solo
activate/extend a Solo month, $9 via x402 X-PAYMENT header (the POST /subscribe operation; Bearer token required)
run_history
list only your own account's past matrix runs (the GET /history operation; Bearer token required)
subscription_status
your account's subscription status (the GET /subscription operation; Bearer token required)