MCP OAuth client-interop conformance
com.textforagents/mcp-oauth-client-interop-conformancetextforagents.comstreamable-httpv1.4.2Scanned
Prove real MCP clients can connect: 5-client x 3-IdP OAuth matrix with shim fixes.
5 tools: 4 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MCP OAuth client-interop conformance can do
The MCP OAuth client-interop conformance is published by textforagents.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: conformance_check, claim_trial, subscribe_solo and run_history), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.4.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 4Claude Code: ask
claim_trialclaim 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/cha…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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)
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
conformance_checkrun 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 RE…1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "conformance_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The description's first verb is "run": a word for a change.
Description, as the server wrote it 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)
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
run_historylist only your own account's past matrix runs (the GET /history operation; Bearer token required)1 finding
Why it is in this group
- The name "run_history" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "run_history" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "run_history" says "run": a word for a change.
Description, as the server wrote it list only your own account's past matrix runs (the GET /history operation; Bearer token required)
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
subscribe_soloactivate/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 serv…No findings
Why it is in this group
- The name "subscribe_solo" says "subscribe": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
Only reads 1Show 1 read-only tool
subscription_statusyour account's subscription status (the GET /subscription operation; Bearer token required)No findings
Why it is in this group
- The name "subscription_status" says "status": a word for reading.
Description, as the server wrote it your account's subscription status (the GET /subscription operation; Bearer token required)
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:25 UTC, unchanged since Oct 28, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcp: tools/list returned 5 tools to an anonymous client, including conformance_check (write), claim_trial (write), subscribe_solo (write), run_history (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "conformance_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The description's first verb is "run": a word for a change.
- Warnrun_history
The server marks "run_history" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "run_history" says "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:claim_trialChanges thingstitledescriptioninputSchemaannotations
- Changed:conformance_checkChanges thingstitleannotations
- Changed:run_historyChanges thingstitleannotations
- Changed:subscribe_soloChanges thingstitledescriptioninputSchemaannotations
- Changed:subscription_statusOnly readstitleannotations
Install
Pinned to version 1.4.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http oauth-client-interop-conformance https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcpclaude mcp add --transport http oauth-client-interop-conformance https://textforagents.com/products/mcp-oauth-client-interop-conformance/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__oauth-client-interop-conformance__subscription_status"
],
"ask": [
"mcp__oauth-client-interop-conformance__conformance_check",
"mcp__oauth-client-interop-conformance__claim_trial",
"mcp__oauth-client-interop-conformance__subscribe_solo",
"mcp__oauth-client-interop-conformance__run_history"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as oauth-client-interop-conformance. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.textforagents/mcp-oauth-client-interop-conformance/verify?hash=5fd766083ae649acf4de2b5d4be4ad9beb3d69b20635943f12be1f960bb76651" | jq -e '.changed == false'Pinned hash 5fd766083ae6, from Nov 9, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.textforagents/mcp-oauth-client-interop-conformance/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.textforagents/mcp-oauth-client-interop-conformance)Source: MCP Registry. Synced Nov 9, 2026, 00:17 UTC.
MCP OAuth client-interop conformance: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MCP OAuth client-interop conformance safe?
- No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MCP OAuth client-interop conformance delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MCP OAuth client-interop conformance do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the MCP OAuth client-interop conformance have?
- 5 tools: 4 write, 1 read. conformance_check, claim_trial, subscribe_solo, run_history and subscription_status.
Does the MCP OAuth client-interop conformance need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MCP OAuth client-interop conformance send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the MCP OAuth client-interop conformance changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.