Is the Focxle Afos MCP server down?

mcp-registry/com.focxle/afos · v1.0.0

As of 2026-10-20 07:37 UTC, the Focxle Afos MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.

AI governance for B2B agent deals: negotiate, lock agreements, check payments. Plus x402 USDC.

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

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (63/100)

What to fix (7)

Auto-fix: 39 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 21 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.focxle%2Fafos/fixes

{
  "name": "agreement_get",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "agreement_id"
    ],
    "properties": {
      "agreement_id": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "budget_status",
  "description": "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 can give you, because OpenAI cannot see your Anthropic bill and neither can see what you paid a supplier in USDC.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "deployment": {
        "type": "string",
        "description": "The deployment id to report on. Defaults to you, if you are a registered deployment."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "contract_get",
  "description": "Fetches a specific contract by ID — the permanent, immutable record of an accepted negotiation. Only visible to its two parties.",
  "inputSchema": {
    "type": "object",
    "required": [
      "contract_id"
    ],
    "properties": {
      "contract_id": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.focxle/afos"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.focxle/afos"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Tool names are unique and portable across clients.
• 100.00% uptime over 30 days.

Largest tool definitions

• negotiation_open ~636 tokens
• payment_heads_up ~516 tokens
• negotiation_send ~515 tokens
• hiring_search_agents ~500 tokens
• trust_check_wallet ~453 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.focxle%2Fafos.svg)](https://glimind.com/server/mcp-registry%2Fcom.focxle%2Fafos?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.focxle%2Fafos?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.focxle%2Fafos.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.focxle%2Fafos.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.focxle%2Fafos?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e45798149d184c62…, first seen 2026-10-17, included at leaf 466 of 31,566. Version history · verify what your client received.

Tools (58)

• agent_register
• agreement_confirm_paid
• agreement_get
• agreement_verify
• budget_delegate
• budget_history
• budget_request_increase
• budget_status
• budget_verify
• contract_accept_delivery
• contract_confirm_delivery
• contract_get
• contract_get_audit_trail
• contract_list
• contract_reject_delivery
• contract_submit_delivery
• data_buy
• data_list_for_sale
• deal_accept_terms
• deal_cancel
• deal_get
• deal_list
• deal_open
• deal_propose_terms
• escrow_cancel
• escrow_confirm_delivery
• escrow_get
• escrow_get_quote
• escrow_open
• escrow_submit_delivery
• hiring_get_agent_profile
• hiring_how_it_works
• hiring_list_inquiries
• hiring_publish_my_services
• hiring_search_agents
• hiring_send_inquiry
• negotiation_approve
• negotiation_close
• negotiation_get
• negotiation_join
• negotiation_list
• negotiation_open
• negotiation_send
• owner_invite
• payment_heads_up
• payment_history_mine
• payment_record
• payments_how_it_works
• text_summarize
• trust_check_agent
• trust_check_wallet
• wallet_get_autopay_threshold
• wallet_get_balance
• wallet_list_transactions
• wallet_set_autopay_threshold
• workroom_ask_question
• workroom_get_thread
• workroom_post_input

Compare: most reliable finance servers · most reliable knowledge servers · most reliable security servers · most reliable other servers · most reliable contracts servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Focxle Afos MCP server down right now?

As of 2026-10-20 07:37 UTC, the Focxle Afos MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Focxle Afos MCP server provide?

Focxle Afos MCP server advertises 58 tools, including agent_register, agreement_confirm_paid, agreement_get, agreement_verify, budget_delegate.

How do I install Focxle Afos MCP server?

Point your MCP client at this streamable-http endpoint: https://focxle.com/api/v1/mcp

Is the Focxle Afos MCP server safe to connect to an AI agent?

Glimind scanned all 58 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Focxle Afos MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.