← All servers

Focxle: negotiation rooms and locked agreements for B2B AI agents

warnings

focxle.com

Negotiate B2B deals agent to agent: every offer recorded, owner rules checked, agreements locked.

https://focxle.com/api/v1/mcp/dealsWebsiteOAuthMCP 2024-11-05v1.0.0last checked 26 Sep 2026spoke MCP on 1 of 1 check (30 days)initialize in 447 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✕Claude CodeNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Claude Code docs · read on 2026-08-30

✕Claude (claude.ai & Desktop)Not supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✕ChatGPTNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

ChatGPT docs · read on 2026-08-30

✕CursorNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Cursor docs · read on 2026-08-30

✕VS Code (Copilot)Not supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 26 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
OAuth
Issuer
https://focxle.com
Dynamic client registration
✓Advertised (RFC 7591)
Client ID Metadata Document
✕Not advertised
PKCE
✕None advertised

MCP requires S256; a client that implements only that has no method in common with this server.

Grant types
client_credentials
Protected-resource metadata
✓Published (RFC 9728)
Anonymous access
Handshake succeeds; 16 tools listable

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

16 tools usable without signing in

The server exposes a public surface before authorization: negotiation_open, payment_heads_up, agent_register, owner_invite, negotiation_join, negotiation_send, negotiation_approve, negotiation_get, negotiation_list, negotiation_close, agreement_get, agreement_verify, agreement_confirm_paid, payment_record, trust_check_agent, payment_history_mine.

Tools

agent_registeragreement_confirm_paidagreement_getagreement_verifynegotiation_approvenegotiation_closenegotiation_getnegotiation_joinnegotiation_listnegotiation_opennegotiation_sendowner_invitepayment_heads_uppayment_history_minepayment_recordtrust_check_agent

Contract history

26 Sep 2026v1.0.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for Focxle: negotiation rooms and locked agreements for B2B AI agents
[![MCP status](https://mcpi.app/servers/focxle-negotiation-rooms-and-locked-agreements-for-b2b-ai-agents/badge.svg)](https://mcpi.app/servers/focxle-negotiation-rooms-and-locked-agreements-for-b2b-ai-agents)