Alfabot MCP Server
REMOTE · ALFABOT.CL · SCANNED OCT 4
Consulta de planes de productos Alfabot y agendamiento de reuniones para colegios y empresas
Available components
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 299 tokens (~99/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Alfabot MCP Server server?
Alfabot MCP Server is a hosted endpoint at https://alfabot.cl/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 · alfabot.cl
claude mcp add --transport http cl-alfabot-mcp-server 'https://alfabot.cl/mcp'
{
"mcpServers": {
"cl-alfabot-mcp-server": {
"url": "https://alfabot.cl/mcp"
}
}
} {
"servers": {
"cl-alfabot-mcp-server": {
"type": "http",
"url": "https://alfabot.cl/mcp"
}
}
} [mcp_servers.cl-alfabot-mcp-server] url = "https://alfabot.cl/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cl-alfabot-mcp-server": {
"type": "remote",
"url": "https://alfabot.cl/mcp",
"enabled": true
}
}
} openclaw mcp add cl-alfabot-mcp-server --url 'https://alfabot.cl/mcp' --transport streamable-http
mcp_servers:
cl-alfabot-mcp-server:
url: "https://alfabot.cl/mcp" {
"McpServers": {
"cl-alfabot-mcp-server": {
"Transport": "http",
"Url": "https://alfabot.cl/mcp"
}
}
} assistant mcp add cl-alfabot-mcp-server -t streamable-http -u 'https://alfabot.cl/mcp'
{
"mcpServers": {
"cl-alfabot-mcp-server": {
"type": "http",
"url": "https://alfabot.cl/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Oct 2026 · Probed https://alfabot.cl/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=alfabot.cl | CN=YE2,O=Let's Encrypt,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 628762c78e5de8e9b718c707f6d2f0546c3 |
| SANs: alfabot.cl, www.alfabot.cl | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of alfabot.cl. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cl. | present | 21199 | 8 | Verified |
| alfabot.cl. | present | 14255 | 8 | Verified |
| alfabot.cl. | 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 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; font-src 'self' data: blob: https:; object-src 'none'; frame-ancestors 'none'; upgrade-insecure-requests; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://alfabot.cl/mcp | Verified | 200 | |
| http (plaintext) | http://alfabot.cl/mcp | HTTPS enforced | 301 | https://alfabot.cl/mcp |
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 →
book_meeting Agendar reunion ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Colegio o empresa (opcional) |
| string | yes | – | |
| endsAt | string | yes | ISO 8601, exactamente 30 minutos despues de startsAt |
| name | string | yes | Nombre completo de quien agenda |
| notes | string | – | Contexto breve de la reunion (opcional) |
| startsAt | string | yes | ISO 8601, debe ser un horario devuelto por check_availability |
No output schema declared.
No examples provided.
check_availability Consultar disponibilidad para reunion ~59
Consulta horarios disponibles para agendar una reunion de 30 minutos con Alfabot. Usar el resultado (no inventar horarios) antes de llamar a book_meeting.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Cantidad de dias hacia adelante a consultar |
No output schema declared.
No examples provided.
get_plans Consultar planes ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| product | string | – | Codigo del producto. Si se omite, devuelve el catalogo global de planes. |
No output schema declared.
No examples provided.
What is the Alfabot MCP Server server?
Alfabot MCP Server is listed in the public MCP registry as cl.alfabot/mcp-server. Consulta de planes de productos Alfabot y agendamiento de reuniones para colegios y empresas. This page covers its hosted endpoint (https://alfabot.cl/mcp).
Is the Alfabot MCP Server server safe to use?
Alfabot MCP Server scores 78 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 Alfabot MCP Server server expose?
Alfabot MCP Server exposes 3 tools: get_plans, check_availability, book_meeting. Their descriptions and schemas cost roughly 299 tokens of context every time the server is loaded.
Does the Alfabot MCP Server server require authentication?
No. We connected to Alfabot MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Alfabot MCP Server server still maintained?
Alfabot MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.