# apaxas (remote · apaxas.com)

Reparte los gastos de un grupo y dice quién le debe a quién. Tu IA los ve y los apunta.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `apaxas.com`: 39/100, [markdown](https://verifymcp.io/servers/com-apaxas-apaxas/apaxas.md), [page](https://verifymcp.io/servers/com-apaxas-apaxas/apaxas)
- remote · `apaxas.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-apaxas-apaxas/mcp-abierto.md), [page](https://verifymcp.io/servers/com-apaxas-apaxas/mcp-abierto)

## Channel facts

- Endpoint: `https://apaxas.com/mcp/abierto`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.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-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1332 tokens (~266/item across 5 items; 5 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**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the apaxas MCP server?

apaxas is a hosted endpoint at https://apaxas.com/mcp/abierto, 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-apaxas-apaxas 'https://apaxas.com/mcp/abierto'
```

### Cursor

```json
{
  "mcpServers": {
    "com-apaxas-apaxas": {
      "url": "https://apaxas.com/mcp/abierto"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-apaxas-apaxas": {
      "type": "http",
      "url": "https://apaxas.com/mcp/abierto"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-apaxas-apaxas]
url = "https://apaxas.com/mcp/abierto"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-apaxas-apaxas": {
      "type": "remote",
      "url": "https://apaxas.com/mcp/abierto",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-apaxas-apaxas --url 'https://apaxas.com/mcp/abierto' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-apaxas-apaxas:
    url: "https://apaxas.com/mcp/abierto"
```

### Netclaw

```json
{
  "McpServers": {
    "com-apaxas-apaxas": {
      "Transport": "http",
      "Url": "https://apaxas.com/mcp/abierto"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-apaxas-apaxas -t streamable-http -u 'https://apaxas.com/mcp/abierto'
```

### Other

```json
{
  "mcpServers": {
    "com-apaxas-apaxas": {
      "type": "http",
      "url": "https://apaxas.com/mcp/abierto"
    }
  }
}
```

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-11-21 (score 75, +1)

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

### 2026-11-19 (score 74, +2)

- [security improvement] DNSSEC: fail → pass

### 2026-11-17 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 71)

First indexed and scored.

## MCP tools (5)

### `ver_grupos` (~75 tokens)

Ver tus grupos

Use this when the user asks about their apaxas groups or how their shared expenses stand overall, or to find out which group and which names to use. Lists the user's groups: name, code, currency, members (with the exact names to use when logging), which member is the user and the user's balance in each.

### `ver_grupo` (~149 tokens)

Ver un grupo

Use this when the user asks how a group's shared expenses stand: who owes whom, how much someone owes or is owed, how to settle up or what has been spent lately. Shows one apaxas group: what each person owes or is owed, the payments that would even everyone up and the latest expenses.

Input parameters:

- `gastos` (integer): How many of the latest expenses to include (30 if not given).
- `grupo` (string, required): The group's code, the end of its link. Its name or its link also work.
- `llave` (string): The key that came with this group when it was created without an apaxas account. Not needed when the user's account is connected.

### `crear_grupo` (~348 tokens)

Crear un grupo

Use this when the user wants to split costs with other people (a trip, a shared flat, a couple, a dinner, any shared plan) and has no apaxas group for it yet. Creates the group with the user in it and the others by name and, if the user already said what was spent, logs those expenses in the same call. Returns the group link, which the user sends to the others so each one opens it and says who they are. It also works without an apaxas account: then the user's name is needed, and the reply brings a key to keep using this group from this conversation. With the account, calling it again right away with the same name does not create a second group or log the expenses twice. Do not use it when the user already has a group for this plan or was sent the link to one.

Input parameters:

- `gastos` (array): Optional: the expenses the user has already mentioned, to log them in the new group. The names are the user's and those in «personas».
- `moneda` (string): ISO 4217 code of the currency the group keeps its accounts in (EUR, USD, GBP…). EUR if not given.
- `nombre` (string, required): The group's name: «Lisboa», «Piso de Lavapiés», «Marta's birthday».
- `personas` (array): The other people in the group, without the user, by the name everyone knows them by.
- `tu_nombre` (string): The user's name in this group, the one the others know them by. Needed without the user's apaxas account; with it, the name on the account if not given.

### `entrar_en_grupo` (~192 tokens)

Entrar en un grupo

Use this when the user was sent the link or the code of an apaxas group and wants to join it. Joins as one of the people nobody has claimed yet or, if they are not listed, under the user's own name, like opening the link in the app. Without a name it does not join, and the reply says who is free. It cannot join as someone who is already in the group. Do not use it for a group the user is already in, or to start a new one.

Input parameters:

- `grupo` (string, required): The group link (apaxas.com/k7m2qx9pr4tb), the message that brings it or its code, the end of the link. The group's name does not work here.
- `tu_nombre` (string): Who the user is in the group: one of the free names, or their own if they are not listed.

### `apuntar_gastos` (~217 tokens)

Apuntar gastos

Use this when the user says what someone paid or wants to add costs to an existing apaxas group («dinner was 86 euros, I paid», «Ana paid the taxi»), including a repayment between two people or money the group received. Logs one or several entries on the user's behalf, only to work out who owes whom. Names must be people in the group; if one is not, the reply lists them. All or nothing: if anything is wrong, nothing is logged and the reply says what to fix. Up to 50 at once. The others in the group get a phone notification. Do not use it to pay, send or request money: apaxas never moves money.

Input parameters:

- `gastos` (array, required)
- `grupo` (string, required): The group's code, the end of its link. Its name or its link also work.
- `llave` (string): The key that came with this group when it was created without an apaxas account. Not needed when the user's account is connected.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-apaxas-apaxas/mcp-abierto#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 72
- 2026-11-17: 72
- 2026-11-16: 71

## Common questions

### What is the apaxas MCP server?

apaxas is an MCP server listed in the public MCP registry as com.apaxas/apaxas. Reparte los gastos de un grupo y dice quién le debe a quién. Tu IA los ve y los apunta. This page covers its hosted endpoint (https://apaxas.com/mcp/abierto).

### Is the apaxas MCP server safe to use?

apaxas scores 75 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 apaxas MCP server expose?

apaxas exposes 5 tools: ver_grupos, ver_grupo, crear_grupo, entrar_en_grupo, apuntar_gastos. Their descriptions and schemas cost roughly 981 tokens of context every time the server is loaded.

### Does the apaxas MCP server require authentication?

No. We connected to apaxas without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the apaxas MCP server still maintained?

apaxas is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the apaxas MCP server?

VerifyMCP ran 13 checks on apaxas, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://apaxas.com/mcp/abierto
- Website: https://apaxas.com/ia
- Changelog RSS feed: https://verifymcp.io/servers/com-apaxas-apaxas/mcp-abierto.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-apaxas-apaxas/mcp-abierto/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-apaxas-apaxas/mcp-abierto.json
- HTML version of this page: https://verifymcp.io/servers/com-apaxas-apaxas/mcp-abierto
