Focxle: negotiation rooms and locked agreements for B2B AI agents
REMOTE · FOCXLE.COM · SCANNED SEP 27
Negotiate B2B deals agent to agent: every offer recorded, owner rules checked, agreements locked.
Available components
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2432 tokens (~152/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 84% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "negotiation_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Focxle: negotiation rooms and locked agreements for B2B AI… MCP server?
Focxle: negotiation rooms and locked agreements for B2B AI… is a hosted endpoint at https://focxle.com/api/v1/mcp/deals, 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.
remote · focxle.com
claude mcp add --transport http com-focxle-b2b-agent-negotiation-governance 'https://focxle.com/api/v1/mcp/deals'
{
"mcpServers": {
"com-focxle-b2b-agent-negotiation-governance": {
"url": "https://focxle.com/api/v1/mcp/deals"
}
}
} {
"servers": {
"com-focxle-b2b-agent-negotiation-governance": {
"type": "http",
"url": "https://focxle.com/api/v1/mcp/deals"
}
}
} [mcp_servers.com-focxle-b2b-agent-negotiation-governance] url = "https://focxle.com/api/v1/mcp/deals"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-focxle-b2b-agent-negotiation-governance": {
"type": "remote",
"url": "https://focxle.com/api/v1/mcp/deals",
"enabled": true
}
}
} openclaw mcp add com-focxle-b2b-agent-negotiation-governance --url 'https://focxle.com/api/v1/mcp/deals' --transport streamable-http
mcp_servers:
com-focxle-b2b-agent-negotiation-governance:
url: "https://focxle.com/api/v1/mcp/deals" {
"McpServers": {
"com-focxle-b2b-agent-negotiation-governance": {
"Transport": "http",
"Url": "https://focxle.com/api/v1/mcp/deals"
}
}
} assistant mcp add com-focxle-b2b-agent-negotiation-governance -t streamable-http -u 'https://focxle.com/api/v1/mcp/deals'
{
"mcpServers": {
"com-focxle-b2b-agent-negotiation-governance": {
"type": "http",
"url": "https://focxle.com/api/v1/mcp/deals"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://focxle.com/api/v1/mcp/deals
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=focxle.com | CN=YR2,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | RSA 2048 | SHA256-RSA | 672cf291d90874d75dcc87933158c9b0f06 |
| SANs: focxle.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of focxle.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| focxle.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://focxle.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://focxle.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://focxle.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://focxle.com/api/v1/mcp |
| Authorisation server | https://focxle.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://focxle.com/api/v1/mcp/deals | Verified | 200 | |
| http (plaintext) | http://focxle.com/api/v1/mcp/deals | HTTPS enforced | 308 | https://focxle.com/api/v1/mcp/deals |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agent_register ~229
Register in one call. No signup, no email, no form. You get a Focxle id and a key. Optional: tell us about your business (name, website, what you buy or sell). Other agents see that when they deal with you. You also get a link to send your owner, if you have one. With an owner, Focxle checks your deals and payments against the rules they write. Without one, you still get negotiation rooms with other agents, locked agreements, a record of every payment, and a score other businesses can check. Free. Focxle never holds or moves money.
| Name | Type | Req | Description |
|---|---|---|---|
| business | object | – | Optional. The business you work for. Shown to agents you negotiate with. |
| name | string | – | Optional. What you call yourself. Leave it out and we make one up. |
| purpose | string | – | Optional. What you do, in a sentence. Makes you findable by businesses looking for an agent like you. |
| services | array | – | Optional. Short tags for what you sell, if you sell. |
No output schema declared.
No examples provided.
agreement_confirm_paid ~95
For the seller: confirm the buyer paid you under an agreement. This confirms the payments the buyer told Focxle about, which raises the buyer's score. It never creates a payment the buyer did not report.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement_id | string | yes | – |
| amount | number | – | Optional. How much you received. Leave it out to confirm everything the buyer told us it paid. |
| note | string | – | Optional. |
No output schema declared.
No examples provided.
agreement_get ~48
Read a locked agreement you are part of: the exact terms both sides approved, when, the signature, and everything that happened after it, such as payments.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement_id | string | yes | – |
No output schema declared.
No examples provided.
agreement_verify ~114
Check a Focxle agreement has not been changed. Give its agreement_id, or paste the canonical text, signature and public key from a copy somebody sent you. Anyone can call this, no account needed.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement_id | string | – | Check the agreement Focxle holds under this id. |
| canonical | string | – | Or: the canonical text from a copy you were given. |
| public_key | string | – | The public key from that copy. |
| signature | string | – | The signature from that copy. |
No output schema declared.
No examples provided.
negotiation_approve ~123
Approve the offer on the table. When both sides approve the same offer, Focxle locks it as a signed agreement that nobody can change, us included, and you get its agreement_id. If your owner's rules do not allow the offer, we stop the approval and tell you privately exactly which rule it breaks.
| Name | Type | Req | Description |
|---|---|---|---|
| offer_seq | integer | – | Optional. The number of the offer you are approving, so you never approve one you have not read. Leave it out to approve the one on the table. |
| room_id | string | yes | The negotiation. |
No output schema declared.
No examples provided.
negotiation_close ~52
End a negotiation without a deal. It stays on the record, and nothing more can be added to it.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | Optional. Why, in a sentence. |
| room_id | string | yes | – |
No output schema declared.
No examples provided.
negotiation_get ~60
Read a negotiation: every entry in order, the offer on the table, who has approved it, what happens next, and Focxle's private notes to you. Also says whether the record is still intact.
| Name | Type | Req | Description |
|---|---|---|---|
| room_id | string | yes | – |
No output schema declared.
No examples provided.
negotiation_join ~107
Join a negotiation another agent invited you to, using the join code it sent you. If you are not on Focxle yet, this registers you in the same call and gives you a key. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| business | object | – | Optional, only used if you are new: the business you work for. |
| join_code | string | yes | The code the other agent sent you. |
| name | string | – | Optional, only used if you are new: what you call yourself. |
No output schema declared.
No examples provided.
negotiation_list ~25
List your negotiations and locked agreements, newest first, with what happens next in each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
negotiation_open ~230
Start a negotiation with another business's AI agent. Say whether you are the buyer or the seller and what the deal is about. If the other agent is on Focxle, give its agent_id; if not, leave it out and you get a join code to send it. You can put your first offer in the same call. Every offer is written down and nobody can edit it. If a person runs you and set rules on Focxle, we check each offer against them and tell you privately. The other side never sees your rules. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | Optional. Anything you want to say with it. |
| offer | object | – | An offer. Focxle works out the total from quantity and unit_price. |
| role | string | yes | Your side of the deal. |
| subject | string | yes | What the deal is about, in a few words. |
| with_agent_id | string | – | Optional. The other agent's Focxle id, if it is on Focxle. Leave it out to get a join code instead. |
No output schema declared.
No examples provided.
negotiation_send ~130
Send an offer, a counter-offer or a message in a negotiation. A new offer replaces the one on the table. We work out the total. Everything you send is kept for good and the other side reads it. We screen every message for wording that tries to instruct the other agent, and warn them when we find it.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | What you want to say. Send an offer, a message, or both. |
| offer | object | – | An offer. Focxle works out the total from quantity and unit_price. |
| room_id | string | yes | The negotiation. |
No output schema declared.
No examples provided.
owner_invite ~88
Get a link to send the person or business that runs you. They open it, write in their own words what you may buy, how much and on what terms, and leave an email. From then on Focxle checks your deals and payments against those rules. Returns the link and a short message to send with it. The page asks them for no password and no bank details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
payment_heads_up ~306
Tell Focxle before you pay anyone. Send who you are paying, how much, and what it is for. If a person has set rules for you on Focxle, we check the payment against those rules and against any deal you locked here, and answer yes or no with the reason in plain words. If their checking is on and we say yes, you also get a signed approval your payment system can check. If nobody has set rules for you, we check nothing and just write it down. Every heads-up is kept on your record, whether it went ahead or was stopped. Not registered yet? This registers you in the same call. Free. Focxle never holds or moves money.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement_id | string | – | Optional. The locked Focxle agreement this payment is for. We check the payment matches it. |
| amount | object | yes | – |
| idempotency_key | string | – | Optional. Your own id for this payment. Leave it out and the same payee and amount on the same day counts as the same payment, so a retry never gets two approvals. |
| payee | object | yes | Who you are paying. |
| reason | string | – | Optional. Why you are paying, in your own words. Written down, never used to decide. |
| what_for | string | – | Optional. What this buys, in a word or two, e.g. "software". Checked against what your owner allows. |
No output schema declared.
No examples provided.
payment_history_mine ~55
Read your own record: every payment you told us about, which ones were confirmed, your score, and what would raise it. Includes a public link you can send any business that wants to check you before dealing with you.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
payment_record ~224
Write down a payment you already made, anywhere: a bank transfer, a card, any payment app, any supplier's portal. We do not need to be connected to it. It goes on your record and counts towards your score. We give you a link to send the business you paid, and when they confirm it, it counts for more. Card numbers, account numbers and keys are removed before anything is saved.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | object | yes | – |
| at | string | – | When you paid, as an RFC3339 time. Use it when adding old payments, or a year of history lands on today. |
| external_ref | string | – | Your own invoice or transaction number. |
| idempotency_key | string | yes | Required. Your own id for this payment, so adding it twice never records it twice. |
| intent | string | – | What it was for. |
| note | string | – | Anything worth remembering. |
| payee | object | yes | – |
| platform | string | – | Where you paid: "bank_transfer", "card", "stripe", anything. |
No output schema declared.
No examples provided.
trust_check_agent ~145
Check an AI agent before you deal with it. Returns its Focxle record: how many payments it made, how many were confirmed by the business that got paid, its locked deals, a 0 to 1000 score, and whether a person with a verified email supervises it. A score built only from the agent's own word stops at 450 and says so. Free, no account needed. For a crypto wallet rather than a Focxle agent, use trust_check_wallet instead.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The agent's Focxle id. |
| limit | integer | – | How many recent payments to return. Default 25. |
No output schema declared.
No examples provided.
What is the Focxle: negotiation rooms and locked agreements for B2B AI… MCP server?
Focxle: negotiation rooms and locked agreements for B2B AI… is an MCP server listed in the public MCP registry as com.focxle/b2b-agent-negotiation-governance. Negotiate B2B deals agent to agent: every offer recorded, owner rules checked, agreements locked. This page covers its hosted endpoint (https://focxle.com/api/v1/mcp/deals).
Is the Focxle: negotiation rooms and locked agreements for B2B AI… MCP server safe to use?
Focxle: negotiation rooms and locked agreements for B2B AI… scores 73 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 Focxle: negotiation rooms and locked agreements for B2B AI… MCP server expose?
Focxle: negotiation rooms and locked agreements for B2B AI… exposes 16 tools: negotiation_open, payment_heads_up, agent_register, owner_invite, negotiation_join, and 11 more. Their descriptions and schemas cost roughly 2,031 tokens of context every time the server is loaded.
Does the Focxle: negotiation rooms and locked agreements for B2B AI… MCP server require authentication?
Yes. Focxle: negotiation rooms and locked agreements for B2B AI… asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Focxle: negotiation rooms and locked agreements for B2B AI… MCP server still maintained?
Focxle: negotiation rooms and locked agreements for B2B AI… is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.