Skip to content
MCPSTAMP
MCP server report

Focxle MCP server

com.focxle/afos

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 69 of 100 (grade C), higher than 9.4% of the 33,003 registry servers that responded over HTTPS that day. Ready for MCP Registry. Not ready for Claude, ChatGPT and Gemini.

Measured facts

Score
69C
Sign-in
OAuth
Tools listed
58
Protocol version
2024-11-05
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC), PKCE S256 advertised, readOnlyHint or destructiveHint on every tool and Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC), PKCE S256 advertised, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT) and Human-readable title on every tool.
Gemini Connected Apps Not ready Blocked by Supported protocol version negotiated, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields and PKCE S256 advertised.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

10 checks to fix

  1. Fails

    readOnlyHint or destructiveHint on every tool

    tool_annotations

    Blocks Claude and ChatGPT.

    Measured 58/58 tools set neither readOnlyHint nor destructiveHint: negotiation_open, payment_heads_up, agent_register, owner_invite, negotiation_join and 53 more

    Set annotations.readOnlyHint: true on read-only tools and destructiveHint: true on tools that modify or delete data (Claude needs one of them on every tool; ChatGPT needs all three hints, see tool_open_world).

  2. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks Claude, ChatGPT and Gemini.

    Measured https://focxle.com/.well-known/oauth-authorization-server lacks authorization_endpoint, response_types_supported:["code"]

    Add authorization_endpoint, response_types_supported:["code"] to the authorization server metadata.

  3. Fails

    Supported protocol version negotiated

    protocol_version

    Blocks Gemini.

    Measured Negotiated 2024-11-05

    Return protocolVersion "2025-11-25" (or "2025-06-18") in the initialize result. Gemini Connected Apps requires 2025-03-26 to 2025-11-25.

  4. Fails

    PKCE S256 advertised

    auth_pkce

    Blocks Claude, ChatGPT and Gemini.

    Measured code_challenge_methods_supported missing

    Support PKCE and advertise "code_challenge_methods_supported": ["S256"] (MCP clients refuse to proceed without it).

  5. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 58/58 tools miss an explicit hint: negotiation_open, payment_heads_up, agent_register, owner_invite, negotiation_join and 53 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  6. Fails

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 58/58 without title: negotiation_open, payment_heads_up, agent_register, owner_invite, negotiation_join and 53 more

    Add a short human-readable "title" to every tool (shown in store UIs and consent screens).

  7. Fails

    First metadata URL Gemini tries answers 200 with the required fields

    auth_gemini_discovery

    Blocks Gemini.

    Measured https://focxle.com/.well-known/oauth-authorization-server (first URL Gemini tries) lacks authorization_endpoint, response_types_supported:["code"]

    Make https://focxle.com/.well-known/oauth-authorization-server answer HTTP 200 with the authorization server metadata (authorization_endpoint, token_endpoint, response_types_supported ["code"], registration_endpoint). Gemini tries https://f

  8. Fails

    GET answers SSE or 405

    get_stream

    Measured HTTP 200 application/json

    Return HTTP 405 Method Not Allowed on GET (or a text/event-stream), not a page or 404.

  9. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured HTTP 401 instead of a JSON-RPC error

    Route the method first and answer unknown methods with JSON-RPC error -32601 before the auth check, or return a JSON-RPC error body with the 401.

  10. Warning

    refresh_token grant advertised

    auth_refresh

    Measured grant_types_supported: ["client_credentials"]

    Issue refresh tokens and list "refresh_token" in grant_types_supported so users are not logged out hourly.

17 checks passed

Passed. Served over HTTPS, initialize over Streamable HTTP, JSON or SSE response Content-Type, initialize latency, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), Client registration (DCR or Client ID Metadata Documents), tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, Tool descriptions.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Focxle

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Ffocxle.com%2Fapi%2Fv1%2Fmcp)](https://www.mcpstamp.com/r/com-focxle-afos/)

HTML

<a href="https://www.mcpstamp.com/r/com-focxle-afos/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Ffocxle.com%2Fapi%2Fv1%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

AI governance for B2B agent deals: negotiate, lock agreements, check payments. Plus x402 USDC.
Registry name
com.focxle/afos
Remote URL
https://focxle.com/api/v1/mcp
Version
3.0.0
Website
focxle.com
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade C servers

All grade C servers · All server reports · State of MCP readiness, November 2026