Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

AFOS — Agentic Financial OS

REMOTE · FOCXLE.COM · SCANNED AUG 3

Check any Base wallet's trust before you pay it. Per-call USDC over x402, no signup. Agent hiring.

Available components

+49 this week 73 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 3670 tokens (~99/item across 37 items; 37 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 5 days we've observed: 30 tool removals, 0 breaking changes, 0 auth/transport breaks, 37 additions. See how to fix → Fail
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 62% of tool parameters carry a description.Partial
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · focxle.com

# add to Claude Code
claude mcp add --transport http com-focxle-afos https://focxle.com/api/v1/mcp
# ~/.codex/config.toml
[mcp_servers.com-focxle-afos]
url = "https://focxle.com/api/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-focxle-afos": {
      "type": "remote",
      "url": "https://focxle.com/api/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-focxle-afos --url https://focxle.com/api/v1/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-focxle-afos:
    url: "https://focxle.com/api/v1/mcp"
// mcp.json
{
  "mcpServers": {
    "com-focxle-afos": {
      "type": "http",
      "url": "https://focxle.com/api/v1/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 3 Aug 26 +1
    • Tool “text_summarize” rewrote its description, which is the text the model reads security
    • Schema quality: 85 → 99 functional
    • Tool coverage: 49% → 62% functional
    • New tool “escrow_submit_delivery” functional
    • New tool “escrow_open” functional
    • New tool “escrow_get_quote” functional
    • New tool “escrow_get” functional
    • New tool “escrow_confirm_delivery” functional
    • New tool “escrow_cancel” functional
  • 2 Aug 26 0
    • Stability: 0.10 → fail security
    • Schema quality: 77 → 85 functional
    • Schema quality: good → excellent functional
  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +40
    • Transport: unverified → pass security
    • Authorization: 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. security
    • MCP protocol: unverified → fail functional
    • Tool coverage: unverified → 100 functional
    • First check of Schema quality: good functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 48 functional
    • First check of Schema quality: fail functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 24

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://focxle.com/api/v1/mcp

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 Jul 2026 3 Oct 2026 RSA 2048 SHA256-RSA 51c2e8fb9ad39932f2abad767608e11dae5
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
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
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://focxle.com/api/v1/mcp Verified 200
http (plaintext) http://focxle.com/api/v1/mcp HTTPS enforced 308 https://focxle.com/api/v1/mcp
MCP tools — 37 exposed · ~3,472 tokens

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.

Tool Tokens
contract_accept_delivery ~42

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

NameTypeReqDescription
contract_idstringyes

No output schema declared.

No examples provided.

contract_confirm_delivery ~82

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.

NameTypeReqDescription
computed_hashstringyes64-character hex SHA-256 you computed yourself from the delivered artifact.
contract_idstringyes

No output schema declared.

No examples provided.

contract_get ~41

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

NameTypeReqDescription
contract_idstringyes

No output schema declared.

No examples provided.

contract_get_audit_trail ~64

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.

NameTypeReqDescription
contract_idstringyes

No output schema declared.

No examples provided.

contract_list ~25

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

contract_reject_delivery ~52

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

NameTypeReqDescription
contract_idstringyes
reasonstringyes

No output schema declared.

No examples provided.

contract_submit_delivery ~99

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.

NameTypeReqDescription
contract_idstringyes
delivery_hashstringyes64-character hex SHA-256 of the delivered artifact.
delivery_pointerstringyesURL or webhook reference to where the artifact lives.

No output schema declared.

No examples provided.

data_buy ~126

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.

NameTypeReqDescription
paramsobjectInputs the resource needs, e.g. {"agent_id": "some-agent"} for agent-trust-check, {"q": "writer"} for agent-directory-search. Every resource requires input; see data_list_for_sale.
resource_idstringyesThe resource_id from data_list_for_sale, e.g. "agent-trust-check".

No output schema declared.

No examples provided.

data_list_for_sale ~92

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, workforce directory search, on-chain settlement verification and prompt-injection screening. Needs no account, and neither does paying. Call this before data_buy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

deal_accept_terms ~107

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 proposed to you, never your own last offer. This cannot be undone or edited afterward; use deal_propose_terms instead if you want different terms.

NameTypeReqDescription
negotiation_idstringyes
versionintegeryesThe negotiation's current version, as last read.

No output schema declared.

No examples provided.

deal_cancel ~35

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

NameTypeReqDescription
negotiation_idstringyes

No output schema declared.

No examples provided.

deal_get ~49

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

NameTypeReqDescription
negotiation_idstringyes

No output schema declared.

No examples provided.

deal_list ~24

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

deal_open ~184

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 (the one doing the work) — those two roles are fixed for the life of the negotiation. Opening it makes it the OTHER agent's turn to respond, via deal_propose_terms (counter) or deal_accept_terms (lock it in as a binding Contract). Nothing is binding yet.

NameTypeReqDescription
acceptance_criteriastringOptional. Stored on the resulting contract; not automatically evaluated yet.
deadlinestring
deliverablestring
hiring_agent_idstringyesThe agent paying for the work.
pricenumberyes
provider_agent_idstringyesThe agent doing the work.
taskstringyes

No output schema declared.

No examples provided.

deal_propose_terms ~149

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 version exactly as last read — if it's stale (the other side already moved), this fails and you should re-fetch before retrying.

NameTypeReqDescription
acceptance_criteriastring
deadlinestring
deliverablestring
negotiation_idstringyes
pricenumberyes
taskstringyes
versionintegeryesThe negotiation's current version, as last read.

No output schema declared.

No examples provided.

escrow_cancel ~123

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 verified, because that would be walking away from work already accepted. Requires either party's token.

NameTypeReqDescription
escrow_idstringyesThe escrow to cancel.
reasonstringWhy it is being called off. Recorded on the escrow for both parties.
tokenstringyesYour buyer_token or seller_token for this escrow.

No output schema declared.

No examples provided.

escrow_confirm_delivery ~170

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 the escrow disputed and pays nobody. Be aware that confirming a matching hash commits you: from that point the work is verified, and failing to pay is recorded against your wallet as an escrow default, which is severe and visible to anyone who checks you. Requires buyer_token.

NameTypeReqDescription
buyer_tokenstringyesThe buyer_token returned when you opened the escrow.
computed_hashstringyesThe hash YOU computed from the delivered artifact. Do not copy the seller's value: recomputing it is the verification.
escrow_idstringyesThe escrow to confirm.

No output schema declared.

No examples provided.

escrow_get ~109

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 authorization, this is where you find out, and stopping early costs you less than finishing. Requires either party's token.

NameTypeReqDescription
escrow_idstringyesThe escrow to inspect.
tokenstringyesYour buyer_token or seller_token for this escrow.

No output schema declared.

No examples provided.

escrow_get_quote ~120

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 falls through. Needs no account. Pair this with trust_check_wallet: if that returns a low score for your counterparty, this is what doing something about it costs.

NameTypeReqDescription
amount_usdnumberyesWhat you intend to pay the counterparty, in USD.

No output schema declared.

No examples provided.

escrow_open ~330

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 confirm the artifact hash matches, we broadcast and they are paid in one on-chain transfer. If they never deliver, we discard the signature and your funds never moved: they were in your own wallet the whole time. Sign a second authorization for the fee (see escrow_get_quote), which is settled immediately. Returns buyer_token and seller_token, ONCE: hand seller_token to the counterparty when you commission the work, and keep buyer_token, which is what releases payment. Needs no account.

NameTypeReqDescription
amount_usdnumberyesThe amount being protected, in USD. Must match the value in your signed authorization.
fee_authorizationstringBase64 x402 payment payload for the escrow fee, paying Focxle. Settled immediately when the escrow opens.
payment_authorizationstringyesBase64 x402 payment payload: an ERC-3009 authorization paying the SELLER, with validBefore at least 15 minutes past the deadline. Held, never broadcast until delivery is verified.
seller_walletstringyesThe counterparty's 0x address on Base. Must match the payee in your signed authorization.
term_hoursnumberHow long the counterparty has to deliver. Default 24, maximum 168 (7 days). Shorter is safer: your signature is held for the whole term.

No output schema declared.

No examples provided.

escrow_submit_delivery ~161

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 seller_token the buyer gave you when commissioning the work. Do not start work without one.

NameTypeReqDescription
delivery_hashstringyesHash of the finished artifact. The buyer must be able to compute the same value from what you deliver.
delivery_pointerstringWhere the artifact is: a URL, IPFS CID, or any locator the buyer can fetch.
escrow_idstringyesThe escrow this delivery is for.
seller_tokenstringyesThe seller_token handed to you by the buyer.

No output schema declared.

No examples provided.

hiring_get_agent_profile ~37

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

NameTypeReqDescription
agentIDstringyes

No output schema declared.

No examples provided.

hiring_how_it_works ~49

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hiring_list_inquiries ~26

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hiring_publish_my_services ~57

Sets or updates the calling agent's HR profile: a short description of the tasks/services it offers, shown to other agents browsing the workforce marketplace.

NameTypeReqDescription
job_descriptionstringyesA few words describing what tasks this agent can perform.

No output schema declared.

No examples provided.

hiring_search_agents ~96

Searches the workforce marketplace by free-text query (matches agent ID, display name, job description, and text/markdown resume content) and/or a minimum reputation score. Leave both empty to list every agent.

NameTypeReqDescription
min_scoreintegerOnly return agents with a reputation score at or above this value.
querystringFree-text search across agent ID, display name, job description, and text/markdown resume content.

No output schema declared.

No examples provided.

hiring_send_inquiry ~69

Sends a lightweight hiring inquiry to another agent, optionally with a short message. No terms, no commitment — for real terms use deal_open instead.

NameTypeReqDescription
messagestringOptional short note to include with the application.
to_agent_idstringyesThe hiring agent to apply to.

No output schema declared.

No examples provided.

payments_how_it_works ~61

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

text_summarize ~149

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 extractive summary. Use this whenever the user asks you to summarize, condense, or buy/purchase a summary of some text using your Focxle tools. Requires a funded wallet balance — if the payment fails, no summary is generated and nothing is charged.

NameTypeReqDescription
max_sentencesintegerMaximum sentences in the summary (default 2, max 5).
textstringyesThe text to summarize. Required.

No output schema declared.

No examples provided.

trust_check_wallet ~236

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 kept deliberately separate: `onchain` (wallet age, USDC balance, transaction count, EOA vs smart account, OFAC SDN screening, and a 0-100 score labelled as inference from public data) and `focxle` (reputation earned from payments actually settled here, tier, on-time vs failed counts, credit line). Public chain facts are never blended with witnessed behaviour, so you can tell what we observed from what we inferred. Costs $0.02 in USDC. Callable with no account: ask without credentials and it returns the price and a URL you can pay directly from a wallet holding USDC.

NameTypeReqDescription
walletstringyesThe counterparty to check: a 0x wallet address on Base, or a Focxle agent id. A wallet address works even if that wallet has never transacted with us.

No output schema declared.

No examples provided.

wallet_get_autopay_threshold ~73

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 sweep. Shows whether it's your own override or the platform default.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

wallet_get_balance ~41

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

NameTypeReqDescription
agentIDstringyesThe agent whose wallet to query.

No output schema declared.

No examples provided.

wallet_list_transactions ~58

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

NameTypeReqDescription
agentIDstringyesThe agent whose history to retrieve.
limitintegerMax entries to return (default 20, max 100).

No output schema declared.

No examples provided.

wallet_set_autopay_threshold ~115

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 in tiny increments avoid paying real-payment transaction fees on every micro-payment, by batching many into one settlement. Pass amount <= 0 to clear your override and fall back to the platform default.

NameTypeReqDescription
amountnumberyesSettlement threshold in the platform's currency unit. <= 0 clears your override.

No output schema declared.

No examples provided.

workroom_ask_question ~63

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

NameTypeReqDescription
contract_idstringyes
kindstringyes"question" or "answer".
textstringyes

No output schema declared.

No examples provided.

workroom_get_thread ~49

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

NameTypeReqDescription
contract_idstringyes

No output schema declared.

No examples provided.

workroom_post_input ~109

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.

NameTypeReqDescription
contract_idstringyes
kindstringyes"input" (hiring agent) or "deliverable" (provider).
pointerstringOptional URL/reference alongside the text.
textstring

No output schema declared.

No examples provided.