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

ONE — pagos en Monero y trueque de cómputo

REMOTE · MCP.ALICELABS.SPACE

MCP del agente ONE: cobros y pagos XMR, libro auditable y trueque de cómputo. AliceLabs LLC.

+4 this week 62 Trust /100

Last scanned (16 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 623 tokens (~89/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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 →

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 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.

  • 13 Nov 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.

  • 11 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 57

    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 21 Nov 2026 · Probed https://mcp.alicelabs.space/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=alicelabs.space CN=WE1,O=Google Trust Services,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA256 60bb4e0794928b900eb30c8466f7af22
SANs: alicelabs.space, mcp.alicelabs.space, *.mcp.alicelabs.space
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 insecure

Validation of mcp.alicelabs.space. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
space. DS published 51168 13 Verified
alicelabs.space. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.alicelabs.space/api/mcp Verified 200
http (plaintext) http://mcp.alicelabs.space/api/mcp Inconclusive 405
MCP tools · 7 exposed · ~561 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. 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 →

Tool Tokens
one_cobrar ~110

Crea una factura a nombre de ONE (AliceLabs LLC) y la registra. Por defecto en Monero (XMR) con tasa de mercado; también USD. Devuelve id, monto, dirección de pago y estado.

NameTypeReqDescription
clientestring–Nombre del cliente (opcional)
conceptostringyesQué se está cobrando
monedastring–Moneda de pago (por defecto XMR)
monto_usdnumberyesMonto en USD

No output schema declared.

No examples provided.

one_estado ~48

Estado vivo del agente ONE: hora de Guayaquil (UTC−5), cuenta regresiva al ciclo 07:00 EC, herramientas activas, configuración de pagos y tasa XMR/USD.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

one_pagar ~123

Registra o ejecuta un pago a nombre de ONE. Si ONE_XMR_WALLET_URL está configurada (monero-wallet-rpc) envía XMR de verdad; si no, queda como intención auditada.

NameTypeReqDescription
a_direccionstringyesDirección destino (XMR)
a_nombrestring–Nombre del receptor (opcional)
conceptostringyesConcepto del pago
monedastring–Moneda (por defecto XMR)
monto_usdnumberyesMonto en USD a convertir

No output schema declared.

No examples provided.

one_pagos_listar ~26

Lista las últimas facturas y pagos registrados por ONE (auditoría).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

one_trueque_cerrar ~59

Cierra un trueque del libro registrando la contraparte con la que se pactó.

NameTypeReqDescription
contrapartestringyesCon quién se cierra
idstringyesId del trueque (TRQ-…)

No output schema declared.

No examples provided.

one_trueque_listar ~41

Lista el libro de trueques de potencia de cálculo (abiertos por defecto).

NameTypeReqDescription
estadostring–Filtro por estado (opcional)

No output schema declared.

No examples provided.

one_trueque_ofrecer ~154

Publica en el libro de trueque una oferta o demanda de potencia de cálculo (GPU-h, CPU-h, RAM-GB-h, red-GB…) y qué se pide a cambio (otro recurso, XMR, trabajo).

NameTypeReqDescription
cambiostringyesQué se pide a cambio
cantidadnumberyesCantidad del recurso
peerstring–Contraparte sugerida (opcional)
recursostringyesRecurso: GPU-h, CPU-h, RAM-GB-h, red-GB, almacenamiento-GB…
tipostringyesOfrezco o busco
valida_hnumber–Vigencia en horas (por defecto 72)

No output schema declared.

No examples provided.

Install

How do I install the ONE — pagos en Monero y trueque de cómputo MCP server?

ONE — pagos en Monero y trueque de cómputo is a hosted endpoint at https://mcp.alicelabs.space/api/mcp, 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 · mcp.alicelabs.space

# add to Claude Code
claude mcp add --transport http eddyflores100-lang-one 'https://mcp.alicelabs.space/api/mcp'
Common questions

What is the ONE — pagos en Monero y trueque de cómputo MCP server?

ONE — pagos en Monero y trueque de cómputo is an MCP server listed in the public MCP registry as io.github.eddyflores100-lang/one. MCP del agente ONE: cobros y pagos XMR, libro auditable y trueque de cómputo. AliceLabs LLC. This page covers its hosted endpoint (https://mcp.alicelabs.space/api/mcp).

Is the ONE — pagos en Monero y trueque de cómputo MCP server safe to use?

ONE — pagos en Monero y trueque de cómputo scores 62 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 ONE — pagos en Monero y trueque de cómputo MCP server expose?

ONE — pagos en Monero y trueque de cómputo exposes 7 tools: one_estado, one_cobrar, one_pagar, one_pagos_listar, one_trueque_ofrecer, and 2 more. Their descriptions and schemas cost roughly 561 tokens of context every time the server is loaded.

Does the ONE — pagos en Monero y trueque de cómputo MCP server require authentication?

No. We connected to ONE — pagos en Monero y trueque de cómputo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ONE — pagos en Monero y trueque de cómputo MCP server still maintained?

ONE — pagos en Monero y trueque de cómputo 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 ONE — pagos en Monero y trueque de cómputo MCP server?

VerifyMCP ran 11 checks on ONE — pagos en Monero y trueque de cómputo, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about ONE — pagos en Monero y trueque de cómputo: Authorization and HTTPS. 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.