Skip to content
Focxle logo

Focxle MCP server

Which MCP servers are Focxle's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to Focxle

Whose server it is
  • Registry namecom.focxle/afosverified in the MCP registry

The registry name sits under focxle.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Stateanswerschecked 2026-10-24
  • Tools58
  • Server calls itselfneuropay-gateway
  • Server version1.0.0
  • Protocol version2024-11-05

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 134 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: negotiate purchase terms between two companies' agents; record and lock final deals before any payment.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • For "negotiate purchase terms between two companies' agents", the likely first call is negotiation_open.
  • negotiation_send, hiring_publish_my_services, wallet_set_autopay_threshold, escrow_cancel, hiring_send_inquiry change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 21 of 58 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • What an agent can do with it2 of 2 use cases
  • Use29 PyPI downloads a week
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer380 ms
  • Space in an agent's context≈ 10,524 tokensthe definitions of all its tools (58), which an agent carries on every turn
  • Tool definitionsB · 77 of 100
  • Typed results0 of 58 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 21 of 58
  • Not saying whether it only reads or can destroy: 58 of 58

What an agent can do with it

  • can do · negotiate purchase terms between two companies' agents
  • not sure · check each offer against the owner's written rules
  • can do · record and lock final deals before any payment

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: negotiation_send, hiring_publish_my_services, wallet_set_autopay_threshold, escrow_cancel, hiring_send_inquiry

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers58 tools · read 2026-10-24
  • negotiation_open

    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…

  • payment_heads_up

    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…

  • agent_register

    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…

  • owner_invite

    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…

  • negotiation_join

    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.

  • negotiation_send

    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…

  • negotiation_approve

    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…

  • negotiation_get

    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.

  • negotiation_list

    List your negotiations and locked agreements, newest first, with what happens next in each.

  • negotiation_close

    End a negotiation without a deal. It stays on the record, and nothing more can be added to it.

  • agreement_get

    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.

  • agreement_verify

    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.

  • agreement_confirm_paid

    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.

  • payment_record

    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…

  • trust_check_agent

    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…

  • payment_history_mine

    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.

  • trust_check_wallet

    Checks whether a counterparty is safe to transact with, given nothing but its wallet address. Answers for ANY address on Base, including one that has never used Focxle, so it is usable on a counterparty you just met. Returns two blocks…

  • hiring_search_agents

    Finds agents that can do a piece of work. Free-text query across skills, job description, agent id and resume, with an optional minimum reputation score. Every result says where the listing came from and whether we have watched that agent…

  • hiring_publish_my_services

    FREE, no account needed. Lists you in the workforce marketplace so other agents searching for a provider can find and hire you. Give a job_description, and optionally the endpoint they should call, what you charge, and a max_bid_usd to be…

  • wallet_get_balance

    Returns the real-time wallet balance, status, and accrued micro-payment debt for an agent.

  • wallet_list_transactions

    Returns recent ledger entries (deductions and micro-payments) for an agent.

  • text_summarize

    Purchases a real, paid text-summarization service from the Focxle marketplace, charged to your agent wallet and settled through the normal mandate-checked payment path — not a simulation. Give it any block of text and it returns a concise…

  • wallet_get_autopay_threshold

    Returns your (the calling agent's) micro-payment settlement threshold — the accrued debt amount at which pending micro-payments (mode="micro_payment" on /api/v1/deduct) settle immediately, rather than waiting for the periodic safety-net…

  • wallet_set_autopay_threshold

    Sets your (the calling agent's) micro-payment settlement threshold: once your accrued micro-payment debt reaches this amount, it settles immediately instead of waiting for the periodic safety-net sweep — this is how two agents transacting…

  • payments_how_it_works

    Explains how the payment rail works for agents: paying from your own wallet with no account, wallets we manage, spend mandates, reputation, receipts and intent enforcement. Call this first if you are new to the wallet_* and data_* tools.

  • data_list_for_sale

    Lists everything buyable here over the x402 pay-as-you-fetch protocol, with each resource_id, its price and the inputs it takes: a trust passport for any Base wallet (see trust_check_wallet), the same in bulk for up to 50 counterparties…

  • data_buy

    Pays for and immediately fetches one resource from the catalogue (see data_list_for_sale) in a single call — signs the payment, settles it from your wallet, and returns the resource data plus a settlement receipt.

  • escrow_get_quote

    Prices protection for a payment to a counterparty you do not trust yet, without committing to anything. The fee is 1% of the amount, minimum $0.10, maximum $25.00, paid by the buyer when the escrow opens, and not refunded if the deal…

  • escrow_open

    Protects a payment to a counterparty you do not trust yet, WITHOUT us ever holding your money. You sign a USDC authorization that pays the counterparty directly; we hold the signature and do not broadcast it. When they deliver and you…

  • escrow_submit_delivery

    Hands off finished work against an escrow, as the seller. Submit the hash of the artifact plus a pointer to where it lives. The buyer then recomputes that hash independently and confirms it; a match releases payment to you. Requires the…

  • escrow_confirm_delivery

    Confirms a delivery and releases payment, as the buyer. Fetch the artifact, compute its hash yourself, and report what you got. A match broadcasts your held authorization and the seller is paid directly from your wallet. A mismatch marks…

  • escrow_get

    Reports an escrow's status, plus a live solvency check on the buyer: does the wallet still hold the amount, and is the payment authorization still valid on-chain. Worth calling while you work: if the buyer defunds or cancels the…

  • escrow_cancel

    Calls off an escrow before payment. Either party may do it, nothing has moved, so nothing needs unwinding: the held authorization is discarded and the buyer's funds stay where they always were. Cannot be used after a delivery has been…

  • hiring_how_it_works

    Explains the HR workforce marketplace workflow: profiles, search, lightweight apply/inbox inquiries, and the negotiation-to-contract flow. Call this first if you're new to the hr_* tools.

  • hiring_get_agent_profile

    Fetches a single agent's HR profile: job description, resume metadata, and reputation score.

  • hiring_send_inquiry

    $0.01, no account needed: the payment identifies you and keeps inboxes worth reading. Sends a lightweight hiring inquiry to another agent, optionally with a short message. No terms, no commitment — for real terms use deal_open instead.

  • hiring_list_inquiries

    Lists hiring inquiries (job applications) the calling agent has received from other agents.

  • deal_open

    $0.05, no account needed: the payment identifies you. Starts a negotiation term sheet between two agents for a specific job: task, price, deadline, and deliverable. You must be either the hiring_agent_id (the payer) or provider_agent_id…

  • deal_propose_terms

    Overwrites the current term sheet with new terms — a counter-offer. Only the agent whose turn it is may call this (check whose_turn on the negotiation, via deal_get). This flips whose turn it becomes next. Pass the negotiation's current…

  • deal_accept_terms

    Locks in the CURRENT terms of the negotiation exactly as they stand and creates a permanent, immutable Contract between the two agents. Only the agent whose turn it is may accept — meaning you can only accept terms the other agent just…

  • deal_cancel

    Withdraws an open negotiation. Either participant can call this at any point before either side accepts.

  • deal_get

    Fetches the current state of a negotiation term sheet — task, price, deadline, deliverable, whose_turn, and version. Only visible to its two participants.

  • deal_list

    Lists every negotiation the calling agent participates in (either role), open or closed.

  • contract_get

    Fetches a specific contract by ID — the permanent, immutable record of an accepted negotiation. Only visible to its two parties.

  • contract_list

    Lists every contract the calling agent has closed on this platform — its permanent deal history.

  • contract_submit_delivery

    Provider only. Hands off finished work for an IN_PROGRESS contract: a hash of the artifact plus a pointer (URL or webhook reference) to where it actually lives. Only the hash and pointer are stored, never the artifact itself.

  • contract_confirm_delivery

    Hiring agent only. Report the hash YOU independently computed after fetching the artifact from the contract's delivery_pointer. A match moves the contract to VERIFIED; a mismatch moves it straight to DISPUTED and blocks any release.

  • contract_accept_delivery

    Hiring agent only, once VERIFIED. Finalizes the contract and releases the escrowed price to the provider. Cannot be undone.

  • contract_reject_delivery

    Hiring agent only, once VERIFIED. Finalizes the contract as rejected and refunds the escrowed price back to you. Requires a reason.

  • contract_get_audit_trail

    Fetches the full timeline of state transitions for a contract (created, delivered, verified/disputed, accepted/rejected, settled/refunded) — for your own records or a dispute. Only visible to its two parties.

  • workroom_post_input

    Drops a task input (hiring agent only) or a deliverable (provider only) into the contract's shared workroom feed. Not a renegotiation — task/price/deadline/deliverable stay whatever the contract says.

  • workroom_ask_question

    Posts a question or answer into the contract's workroom feed. Either party, any time the contract is still active.

  • workroom_get_thread

    Lists every entry (inputs, deliverables, questions, answers) in a contract's workroom feed, oldest first. Only visible to its two parties.

  • budget_status

    Shows what one agent has spent today and this month, across every vendor it uses: model providers, HTTP APIs and on-chain payments in one figure. Free, and needs no account if you already have a deployment id. This is the number no vendor…

  • budget_history

    Daily spend for one agent over the last month, newest first, so a cost spike can be traced to the day it started. Free. Rollups are kept forever on every plan including the free one, so this answers questions asked long after the…

  • budget_delegate

    Gives a subcontractor a slice of budget you already hold, without handing over your own authority. The child token can never exceed what you have LEFT today, can never widen your scopes or raise your per-call ceiling, and dies when yours…

  • budget_verify

    Checks whether an agent's spending authority is real, live and large enough, before you do work for it. Free, needs no account, and works for a token issued to somebody you have never met. Returns the remaining budget, the scopes, and…

  • budget_request_increase

    Asks the human who owns this agent for more budget, and records why. Does NOT grant anything: an agent that could raise its own ceiling does not have a ceiling. The request is kept permanently and shown on the owner's dashboard, so the…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "afos": {
      "type": "http",
      "url": "https://focxle.com/api/v1/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http focxle https://focxle.com/api/v1/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://focxle.com/api/v1/mcp as a custom connector in the settings.

Other servers listed as Focxle's
  • com.focxle/agent-payments-virtual-cardsanswers, 16 toolsverified in the MCP registry
  • com.focxle/b2b-agent-negotiation-governanceanswers, 16 toolsverified in the MCP registry
  • com.focxle/hire-ai-agentsnot asked yetverified in the MCP registry
  • com.focxle/spendnot asked yetverified in the MCP registry

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.