_ registry / mcp http-sse · checked 54m ago

alfabot-web

https://alfabot.cl

Registry code: 7936e9c6bf66ad27

api record

Consulta de planes de productos Alfabot y agendamiento de reuniones para colegios y empresas

from a public catalogue that lists it, not from the operator

endpoint
https://alfabot.cl/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is alfabot-web live?
Yes — it answered the hub's last check (checked 54m ago). It answered 100% of checks over the last 30 days.
Is alfabot-web free to use?
Yes — the hub reached it with no key and no payment.
What tools does alfabot-web have?
3 tools: book_meeting, get_plans, check_availability.
Is alfabot-web safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.1%· all time 99.1%

latency
709ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 432 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • check available meeting slots
  • book a 30-minute meeting
  • get product plans for schools
takes → gives
text → data
tools
2 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_plans reads open 15h ago

    Consulta los planes disponibles de un producto Alfabot para colegios. El pricing esta en validacion con los primeros clientes y no se publica: displayPrice viene vacio a proposito, no inventar montos.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "lang": {
          "enum": [
            "es",
            "en"
          ],
          "type": "string",
          "default": "es"
        },
        "product": {
          "enum": [
            "brochure-autoservicio",
            "brochure-avisos-automaticos",
            "brochure-asistente-paes",
            "brochure-apps-moviles",
            "brochure-whatsapp-ventas-postventa"
          ],
          "type": "string",
          "description": "Codigo del producto. Si se omite, devuelve el catalogo global de planes."
        }
      }
    }
    arguments 25 lines
  • check_availability reads open 15h ago

    Consulta horarios disponibles para agendar una reunion de 30 minutos con Alfabot. Usar el resultado (no inventar horarios) antes de llamar a book_meeting.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 60,
          "minimum": 1,
          "description": "Cantidad de dias hacia adelante a consultar"
        }
      }
    }
    arguments 12 lines
  • book_meeting changes data unknown never probed

    Agenda una reunion de 30 minutos con Alfabot en un horario obtenido con check_availability. Requiere que el cliente MCP haya enviado un header Authorization: Bearer <token> (scope meeting:book) en la request a /mcp; ver /auth.md.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name",
        "email",
        "startsAt",
        "endsAt"
      ],
      "properties": {
        "name": {
          "type": "string",
          "minLength": 1,
          "description": "Nombre completo de quien agenda"
        },
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
        },
        "notes": {
          "type": "string",
          "description": "Contexto breve de la reunion (opcional)"
        },
        "endsAt": {
          "type": "string",
          "description": "ISO 8601, exactamente 30 minutos despues de startsAt"
        },
        "company": {
          "type": "string",
          "description": "Colegio o empresa (opcional)"
        },
        "startsAt": {
          "type": "string",
          "description": "ISO 8601, debe ser un horario devuelto por check_availability"
        }
      }
    }
    arguments 38 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 7936e9c6bf66ad27.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7936e9c6bf66ad27/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/7936e9c6bf66ad27/badge.svg)](https://brick.blue/agent/7936e9c6bf66ad27?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.