Skip to content

MCP servers › com.alertasubastas › alertasubastas

MCP server · registry snapshot 2026-11-12 · last tested 2026-11-12

alertasubastas MCP server

Registry name com.alertasubastas/alertasubastas

by alertasubastas.com · domain (the registry's namespace rule)repository owner on GitHub: alertasubastas (personal account)Source ↗Website ↗

Search Spain's public auctions (BOE, Social Security, tax agency, notaries) with full asset records. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-12version 1.0.0streamable HTTP27 tools

Summary

com.alertasubastas/alertasubastas is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain alertasubastas.com. Its linked repository is github.com/alertasubastas/alertasubastas-claude-plugin; GitHub reports its owner as alertasubastas, a personal account. On 2026-11-12 ProtocolProbe connected to it in read-only mode and read its inventory: 27 tools, 3 resources and 2 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
27
Last tested
2026-11-12

Tool list size

10,340 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (27 tools). Counted with Anthropic's token counter on 2026-11-12, from the tool list we read on 2026-11-12. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-12 (alertasubastas.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 4 tools whose name or declaration suggests they change data (borrar_alerta, renombrar_alerta, quitar_favorita, comentar_favorita). That is our reading of the names; we did not call them. Source: our connection, 2026-11-12.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-12
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-11-11 (registry, as of the 2026-11-12 snapshot)
First listed version
2026-11-11 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-12
Package and repository
checked 2026-11-12
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-09, listed on 2026-11-12 with version 1.0.0 (published 2026-11-11).

Source: the official MCP Registry list on 2026-11-09 and on 2026-11-12.

What it is

What does this server offer?

Observed inventory
27tools
3resources
2prompts

None of its 27 tools are described as changing anything. For 27 the reading was uncertain, so no mark is shown.

  • buscar_bienes

    “Busca bienes en subasta (BOE, notariales, Seguridad Social, AEAT, ayuntamientos…), 100 por página.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • filtrosobject“Filtros estructurados.”
    • ordenstring“fecha_celebracion_asc|desc, fecha_insercion_asc|desc, fecha_actualizacion_asc|desc, valoracion_asc|desc, puja_asc|desc, deposito_asc|desc.”
    • pageinteger
    • qstring“Texto libre (título, descripción, calle, referencias, marca/modelo…).”
  • ver_bien

    “Detalle completo de un bien: datos del bien, de su lote y de su subasta (valor, depósito, puja, cargas, situación posesoria, fechas, URL oficial…), subastas similares (ids) y, si la hay, la estimació…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • confirmadoboolean“true solo si el usuario ha confirmado que quiere abrir más fichas tras un error confirmacion_necesaria.”
    • idstringrequired“Id del bien (0x…), de buscar_bienes, ver_lote o listar_favoritas.”
  • ver_subasta

    “IDs de los lotes de una subasta, en su orden.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“subasta.ID del detalle de un bien.”
  • ver_lote

    “IDs de los bienes de un lote (se adjudican juntos) y la subasta a la que pertenece.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“lote.ID del detalle de un bien.”
  • buscar_por_codigoon 1 other server

    “Busca bienes por un identificador: referencia catastral, IDUFIR / CRU, referencia registral, id de subasta del BOE (SUB-…), id de la Seguridad Social o la AEAT, anuncio del BOE, bastidor o matrícula.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • qstringrequired“El identificador; espacios, guiones y barras dan igual.”
  • “Búsqueda de texto libre en subastas para la búsqueda profunda (deep research): devuelve hasta 10 resultados con id, título y URL.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • querystringrequired“Texto libre: tipo de bien, municipio, calle, referencia…”
  • “Ficha de un bien en Markdown (bien, lote, subasta, valor de mercado), para la búsqueda profunda.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Id del bien (0x…), de search.”
  • listar_provinciason 3 other servers

    “Provincias con su slug y nombre exacto, para los filtros.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • listar_municipioson 2 other servers

    “Municipios con subastas de una provincia (el nombre es el valor exacto del filtro municipio) y sus comarcas (slug para el filtro comarca).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • provinciastringrequired“Slug o nombre de la provincia.”
    • qstring“Lugar a buscar (por ejemplo "Valldoreix" o "Sant Cugat").”
  • opciones_filtros

    “Valores admitidos por los filtros (tipos de bien y sus grupos, clases de subasta, procedimientos, estados, pujas, vivienda habitual, bienes en el lote, tramos de superficie y de cantidad reclamada, m…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • explicar_conceptoon 1 other server

    “Los 3 artículos de la ayuda de AlertaSubastas que mejor explican una duda sobre subastas públicas o sobre el servicio (depósito, cargas, cesión de remate, posesión, tipos de subasta, pujas, alertas, …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • qstringrequired“El concepto o la pregunta.”
  • consumo

    “Plan, búsquedas, subastas consultadas y subastas finalizadas consultadas este mes con su cuota.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

Show 15 more tools
  • “Plan de la cuenta, cupos del mes usados y disponibles (búsquedas, subastas consultadas, subastas finalizadas consultadas, alertas que se pueden crear y favoritas que se pueden guardar), rate limits y…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • listar_alertas

    “Alertas de la cuenta, con el límite del plan y las altas del mes.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • ver_alerta

    “Una alerta de la cuenta.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Id de la alerta.”
  • alertas_previsualizaron 1 other server

    “Antes de crear_alerta: cuántas subastas activas coinciden ahora con esos filtros y una muestra de hasta 5 ids (las más recientes), para ajustar filtros demasiado estrechos o amplios.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • filtrosobjectrequired“Filtros de la alerta.”
  • crear_alertaon 1 other server

    “Crea una alerta: los bienes nuevos que cumplan los filtros llegan por email.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 1 required
    • enviostring“agrupado (por defecto), individual (no en alertas nacionales) o sin_email (solo avisos en la web).”
    • filtrosobjectrequired“Filtros de la alerta.”
    • titulostring“Nombre de la alerta (opcional).”
  • borrar_alertaon 1 other server

    “Borra una alerta.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Id de la alerta.”
  • pausar_alerta

    “Deja de enviar los avisos de una alerta sin borrarla.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Id de la alerta.”
  • reactivar_alerta

    “Vuelve a enviar los avisos de una alerta pausada (revalida los límites del plan).”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Id de la alerta.”
  • renombrar_alerta

    “Cambia el título de una alerta; vacío o null lo borra.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • idstringrequired“Id de la alerta.”
    • titulostring or nullrequired
  • listar_favoritas

    “Favoritas de la cuenta, paginadas: id del bien, URL, comentario, estado de seguimiento (estado), título, cómo está la subasta (subasta: grupo activas/proximas/finalizadas, estado y fecha de fin) y co…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • estadostring“Estado de seguimiento de la favorita.”
    • limitinteger
    • offsetinteger
    • subastastring“Solo las favoritas cuya subasta está en ese grupo, como las pestañas de Tus favoritas.”
  • anadir_favorita

    “Guarda un bien en favoritas.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • bienstringrequired“Id del bien (0x…) o su URL de alertasubastas.com.”
    • comentariostring
  • quitar_favorita

    “Quita un bien de favoritas.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • bienstringrequired“Id del bien (0x…) o su URL de alertasubastas.com.”
  • comentar_favorita

    “Fija el comentario de una favorita; vacío o null lo borra.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • bienstringrequired“Id del bien (0x…) o su URL de alertasubastas.com.”
    • comentariostring or nullrequired
  • estado_favorita

    “Cambia el estado de seguimiento de una favorita.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • bienstringrequired“Id del bien (0x…) o su URL de alertasubastas.com.”
    • estadostringrequired
  • enviar_sugerencia

    “Envía al equipo de AlertaSubastas una mejora que propone el usuario, un error que ha visto o un dato o una función que echa en falta; nos llega por email.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 2 required
    • contextostring“Opcional: qué estaba haciendo (búsqueda, filtros, id del bien…), para entenderla.”
    • textostringrequired“Lo que quiere decirnos el usuario, con sus palabras.”
    • tipostringrequired“mejora (propuesta), error (algo que no funciona o un dato equivocado) o falta_dato (un dato, filtro o función que no tenemos).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-12.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
82% of 38
Tools with a description
100% of 27
Typical description length
223 characters

The tool set

Counted from the listing

Tools
27
Size of the list
about 9,975 tokens for an agent to load (characters ÷ 4)
Naming
24 of 27 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 27 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-12 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://alertasubastas.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "alertasubastas": {
      "url": "https://alertasubastas.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "alertasubastas": {
      "type": "http",
      "url": "https://alertasubastas.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"alertasubastas","type":"http","url":"https://alertasubastas.com/mcp"}'
Claude Code
claude mcp add --transport http alertasubastas https://alertasubastas.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "alertasubastas": {
      "type": "streamableHttp",
      "url": "https://alertasubastas.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "alertasubastas": {
      "httpUrl": "https://alertasubastas.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.alertasubastas]
url = "https://alertasubastas.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "alertasubastas": {
      "url": "https://alertasubastas.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://alertasubastas.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-12. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-12. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint alertasubastas.com/mcpSession openedmatchesour test · 2026-11-12
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-12
Repository github.com/alertasubastas/alertasubastas-claude-pluginOpens publiclymatchesapi.github.com · 2026-11-12

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
com.alertasubastas
GitHub owner
a personal account (alertasubastas)
Repository
github.com/alertasubastas/alertasubastas-claude-plugin
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-12; security policy read from GitHub · 2026-11-12.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-12 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.alertasubastas/alertasubastas

Answered from the data above

Who publishes com.alertasubastas/alertasubastas?

The registry ties the namespace com.alertasubastas to the domain alertasubastas.com; only its owner can publish under it. Its linked repository is github.com/alertasubastas/alertasubastas-claude-plugin; GitHub reports its owner as alertasubastas, a personal account. These are facts from the registry and GitHub, not a rating.

Is com.alertasubastas/alertasubastas safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.alertasubastas/alertasubastas need an API key or sign-in?

It opened a session without any credential on 2026-11-12. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.alertasubastas/alertasubastas been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does com.alertasubastas/alertasubastas publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of com.alertasubastas/alertasubastas?

In github.com/alertasubastas/alertasubastas-claude-plugin, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-12
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 5
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-12, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,328 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 27 tools, 3 resources, 2 prompts.
  4. 5,125 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-12; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
not stated
GitHub detects no source language in this repository (docs-only or empty)
Hosting type
registry · 2026-11-12
MCP capability
prompts, resources, tools
our test · 2026-11-12
Transport
streamable HTTP
registry · 2026-11-12
Required credentials
none declared
registry · 2026-11-12 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-12
Lifecycle status
registry · 2026-11-12
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-12
Maintenance
api.github.com · 2026-11-12
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-12

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.alertasubastas/alertasubastas: MCP server record.” Data checked 2026-11-12. https://protocolprobe.com/mcp/servers/com.alertasubastas/alertasubastas

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.alertasubastas/alertasubastas)](https://protocolprobe.com/mcp/servers/com.alertasubastas/alertasubastas)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology