# MCP OAuth client-interop conformance (remote · textforagents.com)

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

- Trust score: 69/100 (medium)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `textforagents.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-textforagents-mcp-oauth-client-interop-conformance/products-mcp-oauth-client-interop-conformance-mcp.md), [page](https://verifymcp.io/servers/com-textforagents-mcp-oauth-client-interop-conformance/products-mcp-oauth-client-interop-conformance-mcp)

## Channel facts

- Endpoint: `https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 521 tokens (~104/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 13% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the MCP OAuth client-interop conformance server?

MCP OAuth client-interop conformance is a hosted endpoint at https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-textforagents-mcp-oauth-client-interop-confo 'https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-textforagents-mcp-oauth-client-interop-confo": {
      "url": "https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-textforagents-mcp-oauth-client-interop-confo": {
      "type": "http",
      "url": "https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-textforagents-mcp-oauth-client-interop-confo]
url = "https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-textforagents-mcp-oauth-client-interop-confo": {
      "type": "remote",
      "url": "https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-textforagents-mcp-oauth-client-interop-confo --url 'https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-textforagents-mcp-oauth-client-interop-confo:
    url: "https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-textforagents-mcp-oauth-client-interop-confo": {
      "Transport": "http",
      "Url": "https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-textforagents-mcp-oauth-client-interop-confo -t streamable-http -u 'https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-textforagents-mcp-oauth-client-interop-confo": {
      "type": "http",
      "url": "https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 68, +7)

- [security improvement] Authorization: unverified → partial
- [cosmetic] Tool “claim_trial” changed its title: Claim the free trial month
- [cosmetic] Tool “conformance_check” changed its title: MCP OAuth conformance check
- [cosmetic] Tool “run_history” changed its title: Run history
- [cosmetic] Tool “subscribe_solo” changed its title: Subscribe (Solo or Fleet)
- [cosmetic] Tool “subscription_status” changed its title: Subscription status

### 2026-11-03 (score 61, 0)

- [functional] Server version: 1.3.0 → 1.4.2

### 2026-11-02 (score 61, +1)

- [security] Tool “claim_trial” rewrote its description, which is the text the model reads
- [security] Tool “subscribe_solo” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 59 → 104
- [functional improvement] Tool coverage: 0% → 13%
- [functional] Server version: 1.1.0 → 1.3.0
- [cosmetic] “claim_trial” added an optional parameter “apply_shims”
- [cosmetic] “claim_trial” added an optional parameter “check”
- [cosmetic] “claim_trial” added an optional parameter “clients”
- [cosmetic] “claim_trial” added an optional parameter “full_matrix”
- [cosmetic] “claim_trial” added an optional parameter “idp_shape”
- [cosmetic] “claim_trial” added an optional parameter “nonce”
- [cosmetic] “claim_trial” added an optional parameter “server_config”
- [cosmetic] “claim_trial” added an optional parameter “signature”
- [cosmetic] “claim_trial” added an optional parameter “wallet”
- [cosmetic] “subscribe_solo” added an optional parameter “apply_shims”
- [cosmetic] “subscribe_solo” added an optional parameter “check”
- [cosmetic] “subscribe_solo” added an optional parameter “clients”
- [cosmetic] “subscribe_solo” added an optional parameter “full_matrix”
- [cosmetic] “subscribe_solo” added an optional parameter “idp_shape”
- [cosmetic] “subscribe_solo” added an optional parameter “server_config”

### 2026-11-01 (score 60, 0)

- [security] Tool “subscribe_solo” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 47 → 59
- [functional] Server version: 1.0.0 → 1.1.0
- [cosmetic] “subscribe_solo” added an optional parameter “servers”
- [cosmetic] “subscribe_solo” added an optional parameter “tier”

### 2026-10-31 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 59, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 58)

First indexed and scored.

## MCP tools (5)

### `conformance_check` (~94 tokens)

MCP OAuth 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)

Input parameters:

- `apply_shims` (boolean)
- `clients` (array)
- `full_matrix` (boolean)
- `idp_shape` (string)
- `server_config` (object)

### `claim_trial` (~182 tokens)

Claim the free trial month

claim the one-time free first Solo month for your first server (the POST /trial/claim operation; Bearer token required; EIP-191 proof required — first call the REST POST /trial/challenge, sign the returned message with your registered wallet, then pass nonce + signature here, exactly as REST)

Input parameters:

- `apply_shims` (boolean)
- `check` (object)
- `clients` (array)
- `full_matrix` (boolean)
- `idp_shape` (string)
- `nonce` (string): single-use nonce from POST /trial/challenge
- `server_config` (object)
- `server_name` (string)
- `signature` (string): EIP-191 personal_sign signature of the challenge message by the claimed wallet
- `wallet` (string): optional; must equal the account's registered payer wallet

### `subscribe_solo` (~191 tokens)

Subscribe (Solo or Fleet)

activate/extend a subscription via x402 X-PAYMENT header (the POST /subscribe operation; Bearer token required): Solo $9/mo per server by default, or Fleet $29/mo for up to 10 servers with tier=fleet (WO-F-P22-17/RT-20 — the tier parameter is advertised here exactly as in the REST OpenAPI). The embedded check shape (server_config / idp_shape / full_matrix / clients / apply_shims / check) is accepted and stored for hourly re-runs, exactly as REST.

Input parameters:

- `apply_shims` (boolean)
- `check` (object)
- `clients` (array)
- `full_matrix` (boolean)
- `idp_shape` (string)
- `server_config` (object)
- `server_name` (string)
- `servers` (array)
- `tier` (string)

### `run_history` (~29 tokens)

Run history

list only your own account's past matrix runs (the GET /history operation; Bearer token required)

### `subscription_status` (~25 tokens)

Subscription status

your account's subscription status (the GET /subscription operation; Bearer token required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-textforagents-mcp-oauth-client-interop-conformance/products-mcp-oauth-client-interop-conformance-mcp#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 68
- 2026-11-03: 61
- 2026-11-02: 61
- 2026-11-01: 60
- 2026-10-31: 60
- 2026-10-30: 59
- 2026-10-29: 59
- 2026-10-28: 58

## Common questions

### What is the MCP OAuth client-interop conformance server?

MCP OAuth client-interop conformance is listed in the public MCP registry as com.textforagents/mcp-oauth-client-interop-conformance. Prove real MCP clients can connect: 5-client x 3-IdP OAuth matrix with shim fixes. This page covers its hosted endpoint (https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp).

### Is the MCP OAuth client-interop conformance server safe to use?

MCP OAuth client-interop conformance scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MCP OAuth client-interop conformance server expose?

MCP OAuth client-interop conformance exposes 5 tools: conformance_check, claim_trial, subscribe_solo, run_history, subscription_status. Their descriptions and schemas cost roughly 521 tokens of context every time the server is loaded.

### Does the MCP OAuth client-interop conformance server require authentication?

No. We connected to MCP OAuth client-interop conformance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MCP OAuth client-interop conformance server still maintained?

MCP OAuth client-interop conformance is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp
- Website: https://textforagents.com/products/mcp-oauth-client-interop-conformance/
- Changelog RSS feed: https://verifymcp.io/servers/com-textforagents-mcp-oauth-client-interop-conformance/products-mcp-oauth-client-interop-conformance-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-textforagents-mcp-oauth-client-interop-conformance/products-mcp-oauth-client-interop-conformance-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-textforagents-mcp-oauth-client-interop-conformance/products-mcp-oauth-client-interop-conformance-mcp