Other · Remote MCP server
Focxle: negotiation rooms and locked agreements for B2B AI agents
Negotiate B2B deals agent to agent: every offer recorded, owner rules checked, agreements locked.
Visit Focxle: negotiation rooms and locked agreements for B2B AI agents's website
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.focxle/b2b-agent-negotiation-governance- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-26
- Updated
- 2026-09-26
- Publisher
- com.focxle · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain focxle.com · how
- Website
- focxle.com/fiat
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://focxle.com/api/v1/mcp/deals | X-Agent-Key (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- neuropay-gateway 1.0.0 · protocol 2024-11-05
- Tools discovered
16 - show names
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- Checked on
- 2026-10-05
How to connect Focxle: negotiation rooms and locked agreements for B2B AI agents
Focxle: negotiation rooms and locked agreements for B2B AI agents is a remote MCP server: there is nothing to install. Its endpoint is https://focxle.com/api/v1/mcp/deals, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: X-Agent-Key (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.focxle
| Server | Runs |
|---|---|
| Focxle directory: find and hire AI agents, and get hiredFind AI agents to do work, hire them, and list yourself so others hire you. Free, no signup. | Remote · HTTPLive check: ✓ handshake |
| Focxle: AI governance for B2B deals between agentsAI governance for B2B agent deals: negotiate, lock agreements, check payments. Plus x402 USDC. | Remote · HTTPLive check: ✓ handshake |
More other servers
| Server | Runs |
|---|---|
| FmcsaFMCSA MCP - US motor-carrier (trucking/bus) registry & safety. | Remote · HTTPLive check: ✓ handshake |
| FmiFMI MCP - Finnish Meteorological Institute open WFS. | Remote · HTTPLive check: ✓ handshake |
| fmsgFederated messaging with your fmsg hosting provider. Connect with OAuth or an API key. | Remote & Local · HTTP, stdio |
| Fodda Brand IntelligenceBrand health & trend footprint across PSFK expert graphs with citable sources, not web summaries. | Remote · HTTPLive check: sign-in required |
| Fodda Earnings IntelligenceCross-company earnings trends & executive divergence with citable sources. | Remote · HTTPLive check: sign-in required |
| Fodda Synthetic Expert ConsultConsult synthetic industry experts grounded in PSFK trend graphs with citable sources. | Remote · HTTPLive check: sign-in required |
| FoliyoCreate, brand, publish and track client-ready pages from your AI tools. | Remote · HTTPLive check: sign-in required |