apaxas
REMOTE · APAXAS.COM · 2 COMPONENTS
Reparte los gastos de un grupo y dice quién le debe a quién. Tu IA los ve y los apunta.
Available components
Last scanned (17 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 19 Nov 26 +2
- DNSSEC: fail → pass ▲ security
- 17 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Nov 26 71
First indexed and scored.
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 21 Nov 2026 · Probed https://apaxas.com/mcp/abierto
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=apaxas.com | CN=WE1,O=Google Trust Services,C=US | 7 Nov 2026 | 5 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 9f92255d7372e74e132d60b53a3e0068 |
| SANs: apaxas.com, www.apaxas.com, *.www.apaxas.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of apaxas.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| apaxas.com. | DS published | 2371 | 13 | Verified |
| apaxas.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apaxas.com/mcp/abierto | Verified | 200 | |
| http (plaintext) | http://apaxas.com/mcp/abierto | HTTPS enforced | 301 | https://apaxas.com/mcp/abierto |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
apuntar_gastos Apuntar gastos ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gastos | array | yes | – |
| grupo | string | yes | 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. |
No output schema declared.
No examples provided.
crear_grupo Crear un grupo ~348
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
entrar_en_grupo Entrar en un grupo ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| grupo | string | yes | 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. |
No output schema declared.
No examples provided.
ver_grupo Ver un grupo ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gastos | integer | – | How many of the latest expenses to include (30 if not given). |
| grupo | string | yes | 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. |
No output schema declared.
No examples provided.
ver_grupos Ver tus grupos ~75
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · apaxas.com
claude mcp add --transport http com-apaxas-apaxas 'https://apaxas.com/mcp/abierto'
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.