# Focxle: virtual cards, spend limits and procurement for AI agents (remote · focxle.com)

Virtual cards and spend budgets for AI agent procurement: SaaS, API and subscription checkout.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `focxle.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-focxle-agent-payments-virtual-cards/api-v1-mcp-cards.md), [page](https://verifymcp.io/servers/com-focxle-agent-payments-virtual-cards/api-v1-mcp-cards)

## Channel facts

- Endpoint: `https://focxle.com/api/v1/mcp/cards`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2002 tokens (~286/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 77% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the Focxle: virtual cards, spend limits and procurement for AI… MCP server?

Focxle: virtual cards, spend limits and procurement for AI… is a hosted endpoint at https://focxle.com/api/v1/mcp/cards, 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.

### Claude

```bash
claude mcp add --transport http com-focxle-agent-payments-virtual-cards 'https://focxle.com/api/v1/mcp/cards'
```

### Cursor

```json
{
  "mcpServers": {
    "com-focxle-agent-payments-virtual-cards": {
      "url": "https://focxle.com/api/v1/mcp/cards"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-focxle-agent-payments-virtual-cards": {
      "type": "http",
      "url": "https://focxle.com/api/v1/mcp/cards"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-focxle-agent-payments-virtual-cards]
url = "https://focxle.com/api/v1/mcp/cards"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-focxle-agent-payments-virtual-cards": {
      "type": "remote",
      "url": "https://focxle.com/api/v1/mcp/cards",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-focxle-agent-payments-virtual-cards --url 'https://focxle.com/api/v1/mcp/cards' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-focxle-agent-payments-virtual-cards:
    url: "https://focxle.com/api/v1/mcp/cards"
```

### Netclaw

```json
{
  "McpServers": {
    "com-focxle-agent-payments-virtual-cards": {
      "Transport": "http",
      "Url": "https://focxle.com/api/v1/mcp/cards"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-focxle-agent-payments-virtual-cards -t streamable-http -u 'https://focxle.com/api/v1/mcp/cards'
```

### Other

```json
{
  "mcpServers": {
    "com-focxle-agent-payments-virtual-cards": {
      "type": "http",
      "url": "https://focxle.com/api/v1/mcp/cards"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 73, +1)

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

### 2026-09-22 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-21 (score 72)

First indexed and scored.

## MCP tools (7)

### `card_get_virtual` (~242 tokens)

Get a single-use virtual card to buy something right now. For agent procurement of any kind: a SaaS subscription, API credits, cloud hosting, a domain on Namecheap, a GitHub or AWS plan, or checkout on any vendor or merchant website. The card is created at the moment you ask, capped at exactly the amount you need and locked to that one merchant, so it cannot be spent twice or anywhere else. It is issued by your owner's own corporate card platform on their own account: Focxle never holds money, never issues cards, and never stores card or account numbers. If you are not registered yet, this registers you. If your owner has not set your budget yet, you get a link to send them, and after that you can buy without asking a human every time. Free.

Input parameters:

- `amount` (object, required)
- `idempotency_key` (string): Your own id for this purchase, so a retry does not buy it twice.
- `payee` (object, required): Who you are paying.
- `reason` (string): Why you are buying this, in your own words. Recorded, never used to decide.

### `spend_request_approval` (~114 tokens)

Ask your owner for a bigger budget, or for permission to buy something they have not allowed yet. Returns a link to send them plus the words to send with it. They open it, write down what you may buy and how much in ordinary English, and turn on checking. After that every payment you make is measured against their own rules before the money moves, which is exactly why they can safely give you more room than they would when nobody is watching. The page asks them for no password and no bank details.

### `agent_register` (~185 tokens)

Register this agent for spending, in ONE call with no signup, no email and no account. You get an identity and a payment record any supplier can read before deciding whether to deal with you, and it follows YOU across every payment platform you use, because you report it rather than the platform reporting it. Then send your owner the link we give you: when they turn on checking, they can safely give you a bigger budget and a longer list of things to buy. Free. We never hold money and never store card or account numbers.

Input parameters:

- `name` (string): Optional. What you call yourself. Leave it out and we generate one.
- `purpose` (string): Optional. What you buy. Also makes you findable by businesses looking to hire an agent like you.
- `services` (array): Optional. Short skill tags, if you also sell work to other agents.

### `payment_record` (~270 tokens)

Submit a receipt or invoice for a payment you already made, on ANY platform, so it counts towards your record. Bank transfer, corporate card, any payment provider, any procurement system nobody has heard of: you tell us, so it does not matter whether we integrate with it. Each payment moves your score. We hand back a one-click link to send the business you paid, and when they confirm it your score's ceiling rises. Account numbers, card numbers and keys are stripped before anything is written down, so what you build here is safe to show a stranger.

Input parameters:

- `amount` (object, required)
- `at` (string): RFC3339 time of the payment. Use it when importing history, or a year of trading lands on today and looks like one afternoon.
- `external_ref` (string): Your own invoice or transaction reference.
- `idempotency_key` (string, required): Required. Your own id for this payment, so a retried import never records it twice.
- `intent` (string): What it was for.
- `note` (string): Anything worth remembering.
- `payee` (object, required)
- `platform` (string): Where you paid: "stripe", "bank_transfer", "corporate_card", anything. A record spanning several platforms is worth more to a reader.

### `spend_check_limit` (~197 tokens)

Check your budget before you buy. Is this purchase inside the daily spend limit and the procurement rules your owner set? Answers in one call: allowed or not, and which limit or rule stopped it. Use this when you already have a way to pay and only need to know if you are allowed. If you need an actual card to pay with, use card_get_virtual instead. In watch-only mode we always allow and tell you what would have been stopped, so this is safe to call even before your owner has turned checking on.

Input parameters:

- `amount` (object, required)
- `idempotency_key` (string, required): Required. Asking twice about one payment returns the first answer.
- `intent` (string): What this is for. Checked against what your owner allowed.
- `payee` (object, required)
- `reasoning` (string): Why you want to make this payment, in your own words. Recorded permanently, never used to decide.

### `trust_check_agent` (~165 tokens)

Check whether an AI agent is safe to deal with before you sell to it, extend terms to it, or take work from it. Returns its payment record: how many payments, over how long, across how many suppliers and platforms, how much has been confirmed by the businesses that received it, and a 0 to 1000 score. Also says what the number is NOT built on: a record nobody else has confirmed is capped at 450 and says so, so you are never handed false confidence. Free, no account. For a crypto wallet rather than a registered agent, use trust_check_wallet instead.

Input parameters:

- `agent_id` (string, required): The agent's Focxle id.
- `limit` (integer): How many recent payments to return. Default 25.

### `payment_history_mine` (~67 tokens)

Read your own payment record and score, and find out exactly what to do next to raise it. Shows what you have logged, what has been confirmed by the businesses you paid, where your ceiling currently sits, and a link you can share with anyone deciding whether to deal with you.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-focxle-agent-payments-virtual-cards/api-v1-mcp-cards#diagnostics

## Score history

- 2026-09-26: 74
- 2026-09-25: 74
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 72
- 2026-09-21: 72

## Common questions

### What is the Focxle: virtual cards, spend limits and procurement for AI… MCP server?

Focxle: virtual cards, spend limits and procurement for AI… is an MCP server listed in the public MCP registry as com.focxle/agent-payments-virtual-cards. Virtual cards and spend budgets for AI agent procurement: SaaS, API and subscription checkout. This page covers its hosted endpoint (https://focxle.com/api/v1/mcp/cards).

### Is the Focxle: virtual cards, spend limits and procurement for AI… MCP server safe to use?

Focxle: virtual cards, spend limits and procurement for AI… scores 74 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: virtual cards, spend limits and procurement for AI… MCP server expose?

Focxle: virtual cards, spend limits and procurement for AI… exposes 7 tools: card_get_virtual, spend_request_approval, agent_register, payment_record, spend_check_limit, and 2 more. Their descriptions and schemas cost roughly 1,240 tokens of context every time the server is loaded.

### Does the Focxle: virtual cards, spend limits and procurement for AI… MCP server require authentication?

Yes. Focxle: virtual cards, spend limits and procurement for 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: virtual cards, spend limits and procurement for AI… MCP server still maintained?

Focxle: virtual cards, spend limits and procurement for AI… is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://focxle.com/api/v1/mcp/cards
- Website: https://focxle.com/fiat
- Changelog RSS feed: https://verifymcp.io/servers/com-focxle-agent-payments-virtual-cards/api-v1-mcp-cards.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-focxle-agent-payments-virtual-cards/api-v1-mcp-cards.json
- HTML version of this page: https://verifymcp.io/servers/com-focxle-agent-payments-virtual-cards/api-v1-mcp-cards