Skip to content

MCP servers › com.blogelia › mcp

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

mcp MCP server

Registry name com.blogelia/mcp

Blogelia — the publisher's title

by blogelia.com · domain (the registry's namespace rule)Website ↗

Blog SEO en piloto automático: genera, edita, programa y publica artículos y consulta estadísticas. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-19version 1.0.0streamable HTTP46 tools

Summary

com.blogelia/mcp is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain blogelia.com. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 46 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: 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: no public GitHub repository

From public records, not a safety rating. Each check with its reason

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
Tools
46
Last tested
2026-11-19

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-19 (api.blogelia.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 14 tools whose name or declaration suggests they change data (update_blog, update_article, unpublish_article, delete_article, create_blog and 9 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-19.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-19
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-11-18 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-18 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19
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. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. 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-18, listed on 2026-11-19 with version 1.0.0 (published 2026-11-18).

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19.

What it is

What does this server offer?

Observed inventory
46tools
0resources
0prompts

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

  • “Organización, plan, scopes de la clave, créditos disponibles (si la clave tiene account:read) y límites restantes (peticiones por minuto, coste del día, artículos de hoy).”

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

    Takes no inputs.

  • “Blogs de la cuenta con id, nombre, URL pública y estado.”

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

    Takes no inputs.

  • “Cambia el perfil editorial de un blog (nombre, categoría, tono, público, autor, contacto, búsqueda web y preguntas frecuentes).”

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

    8 inputs, 1 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
    • namestring“Nombre nuevo del blog.”
    • categoryIdstring“Id de la categoría de negocio (de list_categories).”
    • subcategoryIdsarray“Ids de subcategorías (de list_categories), hasta 5.”
    • profileobject“Perfil del negocio: descripción, servicios, público, tono, formalidad, ubicación, ventajas y palabras clave.”
    • authorobject“Autor que firma los artículos: nombre y biografía.”
    • contactobject“Teléfono y email de contacto que aparecen en el blog.”
    • contentobject“Opciones de los artículos nuevos: búsqueda web y preguntas frecuentes.”
  • list_articleson 70 other servers

    “Artículos de un blog.”

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

    7 inputs, 1 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
    • statusstring“Filtra por estado del artículo (draft, scheduled, pending_approval, published…).”
    • qstring“Texto a buscar en el título.”
    • pageinteger“Página de resultados, desde 1.”
    • limitinteger“Resultados por página (máximo 50).”
    • desdestring“Solo artículos desde esta fecha, YYYY-MM-DD.”
    • hastastring“Solo artículos hasta esta fecha, YYYY-MM-DD.”
  • “Un artículo: título, estado, fechas, SEO, revisión y contenido en Markdown (truncado a 50 KB).”

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

    1 input, 1 required
    • idstringrequired“Id del artículo (de list_articles).”
  • update_articleon 9 other servers

    “Edita título, extracto, SEO, preguntas frecuentes y contenido (en Markdown) de un artículo.”

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

    8 inputs, 2 required
    • idstringrequired“Id del artículo (de list_articles).”
    • revisionintegerrequired“Revisión actual del artículo (de get_article); si otro la cambió antes, da conflicto.”
    • titlestring“Título del artículo.”
    • excerptstring“Resumen corto que se muestra en listados y redes.”
    • keywordstring“Palabra clave principal.”
    • seoobject“Título y meta descripción para buscadores.”
    • contentMarkdownstring“Cuerpo completo del artículo en Markdown (sin HTML).”
    • faqsarray“Preguntas frecuentes del artículo (hasta 8), con pregunta y respuesta.”
  • schedule_article

    “Programa la publicación de un artículo en una fecha ISO 8601 (`at`), o quita la programación con `at: null`.”

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

    2 inputs, 2 required
    • idstringrequired“Id del artículo (de list_articles).”
    • atstring or nullrequired“Fecha y hora de publicación en ISO 8601; null quita la programación.”
  • publish_articleon 6 other servers

    “Publica un artículo ya (o aprueba uno pendiente de revisión).”

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

    1 input, 1 required
    • idstringrequired“Id del artículo (de list_articles).”
  • unpublish_article

    “Retira un artículo publicado de la web.”

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

    2 inputs, 1 required
    • idstringrequired“Id del artículo (de list_articles).”
    • confirmboolean“true para confirmar una acción irreversible o cara; sin él, la herramienta no actúa.”
  • delete_articleon 5 other servers

    “Borra un artículo que no esté publicado (borrador, descartado o despublicado).”

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

    2 inputs, 1 required
    • idstringrequired“Id del artículo (de list_articles).”
    • confirmboolean“true para confirmar una acción irreversible o cara; sin él, la herramienta no actúa.”
  • estimate_article

    “Créditos estimados y máximos de generar un artículo con una longitud y modelos concretos.”

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

    6 inputs, 1 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
    • lengthstring“Longitud: short, medium (por defecto) o long.”
    • textModelIdstring or null“Id del modelo de texto (de list_ai_models); null o sin él, el del blog.”
    • imageModelIdstring or null“Id del modelo de portada (de list_ai_models), "none" sin portada; null o sin él, el del blog.”
    • webSearchboolean“Investigar en la web antes de escribir (más créditos; no en Free).”
    • faqboolean“Añadir preguntas frecuentes al final del artículo.”
  • generate_articleon 7 other servers

    “Encola la generación con IA de un artículo nuevo (a partir de un tema propuesto, una palabra clave o un brief).”

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

    12 inputs, 2 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
    • sourcestringrequired“De dónde sale el artículo: topic (una idea del blog), keyword o brief.”
    • topicIdeaIdstring“Id de la idea de tema (de get_blog) con source=topic.”
    • keywordstring“Palabra clave del artículo (2-80 caracteres) con source=keyword.”
    • intentstring“Intención de búsqueda: informational, commercial o transactional.”
    • briefstring“Instrucciones del artículo en texto libre (30-1500 caracteres) con source=brief.”
    • lengthstring“Longitud: short, medium (por defecto) o long.”
    • textModelIdstring or null“Id del modelo de texto (de list_ai_models); null o sin él, el del blog.”
    • imageModelIdstring or null“Id del modelo de portada (de list_ai_models), "none" sin portada; null o sin él, el del blog.”
    • webSearchboolean“Investigar en la web antes de escribir (más créditos; no en Free).”
    • faqboolean“Añadir preguntas frecuentes al final del artículo.”
    • confirmboolean“true para confirmar cuando el máximo estimado pasa de 50 créditos (estimate_article).”
Show 34 more tools
  • get_generationon 15 other servers

    “Estado y pasos de una generación; cuando termina, incluye el id del artículo.”

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

    1 input, 1 required
    • idstringrequired“Id de la generación (de generate_article o list_generations).”
  • propose_topics

    “Propone 10 temas nuevos para el blog con IA.”

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

    1 input, 1 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
  • “Visitas y únicos aproximados de toda la cuenta, de un blog o de un artículo, en un rango de hasta 400 días (30 por defecto).”

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

    6 inputs, 1 required
    • scopestringrequired“Qué estadísticas: account (toda la cuenta), blog o article.”
    • blogIdstring“Id del blog (de list_blogs); obligatorio con scope=blog.”
    • articleIdstring“Id del artículo (de list_articles); obligatorio con scope=article.”
    • fromstring“Fecha inicial, YYYY-MM-DD.”
    • tostring“Fecha final, YYYY-MM-DD.”
    • intervalstring“Agrupación de la serie: day, week o month.”
  • “Un blog: nombre, dirección, estado y, con permisos de escritura o generación, su perfil editorial, la configuración de contenido y las ideas de temas (con su id, para generate_article con source=topi…”

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

    1 input, 1 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
  • list_categorieson 726 other servers

    “Categorías y subcategorías de negocio admitidas (id y nombre).”

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

    Takes no inputs.

  • analyze_siteon 8 other servers

    “Analiza la web del negocio (`url`) o una descripción (`description`, si no hay web) para proponer el perfil del blog y 10 temas.”

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

    2 inputs
    • urlstring“URL de la web de la empresa que se va a analizar.”
    • descriptionstring“Si no hay web, descripción del negocio en texto libre (20-1000 caracteres).”
  • get_site_analysis

    “Estado y resultado de un análisis de web: perfil propuesto (descripción, servicios, tono...), categoría sugerida y temas.”

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

    1 input, 1 required
    • idstringrequired“Id del análisis (de analyze_site).”
  • “Crea un blog nuevo en la cuenta (cuenta para el límite de blogs del plan).”

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

    7 inputs, 5 required
    • namestringrequired“Nombre del blog.”
    • slugstringrequired“Subdominio del blog en blogelia.com: minúsculas, números y guiones.”
    • categoryIdstringrequired“Id de la categoría de negocio (de list_categories).”
    • subcategoryIdsarray“Ids de subcategorías (de list_categories), hasta 5.”
    • analysisIdstring“Id del análisis de la web (de analyze_site).”
    • profileobjectrequired“Perfil del negocio: descripción, servicios, público, tono, formalidad, ubicación, ventajas y palabras clave.”
    • topicIdeasarrayrequired“Ideas de temas iniciales (del análisis o tuyas), con título y palabra clave opcional.”
  • list_api_keyson 34 other servers

    “Claves de API y conexiones MCP de la cuenta (nunca el valor de la clave): nombre, prefijo, permisos, entorno, blog al que está restringida y estado.”

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

    Takes no inputs.

  • create_api_keyon 44 other servers

    “Crea una clave de API (pk_live_ o pk_test_) para una integración, por ejemplo el .env de otro proyecto.”

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

    4 inputs, 2 required
    • namestringrequired“Nombre para reconocer la clave (por ejemplo, el proyecto que la usa).”
    • scopesarrayrequired“Permisos de la clave (content:read, content:write, generate, publish, stats:read…).”
    • environmentstring“live (real) o test (las escrituras se simulan y no gastan créditos).”
    • blogIdstring“Restringe la clave a un solo blog (de list_blogs); sin él, toda la cuenta.”
  • revoke_api_keyon 25 other servers

    “Revoca una clave de API o una conexión MCP por su id (de list_api_keys).”

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

    2 inputs, 1 required
    • idstringrequired“Id de la clave (de list_api_keys).”
    • confirmboolean“true para confirmar una acción irreversible o cara; sin él, la herramienta no actúa.”
  • get_autopiloton 1 other server

    “Configuración del piloto automático de un blog (activo, ritmo, días, hora, modo revisión o automático) y próximos huecos.”

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

    1 input, 1 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
  • update_autopilot

    “Activa, pausa o cambia el piloto automático de un blog: `perWeek` (0-5 artículos por semana), `days` (0 = domingo ...”

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

    9 inputs, 6 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
    • enabledbooleanrequired“true para activar el piloto automático, false para pausarlo.”
    • perWeekintegerrequired“Artículos por semana (0-5).”
    • daysarrayrequired“Días de publicación: 0 = domingo … 6 = sábado.”
    • hourintegerrequired“Hora de publicación (0-23, hora de Madrid).”
    • modestringrequired“review (quedan pendientes de tu aprobación) o auto (se publican solos).”
    • scheduleTypestring“weekly (días fijos de la semana) o interval (cada N días).”
    • intervalDaysinteger“Con scheduleType=interval, cada cuántos días (1-30).”
    • startDatestring“Con scheduleType=interval, primer día, YYYY-MM-DD.”
  • remove_topic_idea

    “Quita una idea de tema de la cola del blog (por su id, de get_blog).”

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

    2 inputs, 2 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
    • ideaIdstringrequired“Id de la idea de tema (de get_blog, en topicIdeas).”
  • list_generationson 9 other servers

    “Historial de generaciones de un blog (30 días): estado, pasos, créditos y error.”

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

    4 inputs, 1 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
    • estadostring“Filtra por estado de la generación: queued, running, done o failed.”
    • pageinteger“Página de resultados, desde 1.”
    • limitinteger“Resultados por página (máximo 50).”
  • reject_article

    “Descarta un artículo pendiente de aprobación (piloto en modo revisión).”

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

    1 input, 1 required
    • idstringrequired“Id del artículo (de list_articles).”
  • get_link_suggestions

    “Enlaces internos sugeridos para un artículo: otros artículos publicados del mismo blog con los que enlazar (título, URL y texto de anclaje propuesto).”

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

    1 input, 1 required
    • idstringrequired“Id del artículo (de list_articles).”
  • generate_article_faqs

    “Propone con IA preguntas frecuentes para un artículo (hasta 2 créditos).”

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

    1 input, 1 required
    • idstringrequired“Id del artículo (de list_articles).”
  • set_article_cover

    “Pone la imagen de portada de un artículo desde una URL pública (`imageUrl`, recomendado) o en base64 (`imageBase64`, hasta unos 280 KB).”

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

    4 inputs, 2 required
    • idstringrequired“Id del artículo (de list_articles).”
    • imageUrlstring“URL pública de la imagen (JPEG, PNG o WebP de hasta 5 MB).”
    • imageBase64string“Imagen en base64 (hasta unos 280 KB) si no tienes URL.”
    • altstringrequired“Texto alternativo que describe la imagen.”
  • remove_article_cover

    “Quita la imagen de portada de un artículo.”

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

    1 input, 1 required
    • idstringrequired“Id del artículo (de list_articles).”
  • retry_generationon 1 other server

    “Reintenta una generación fallida con las mismas opciones.”

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

    1 input, 1 required
    • idstringrequired“Id de la generación fallida (de list_generations).”
  • reorder_topic_ideas

    “Cambia el orden de la cola de temas de un blog (el piloto automático toma primero los de arriba).”

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

    2 inputs, 2 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
    • idsarrayrequired“Ids de todas las ideas de tema (de get_blog) en el orden nuevo.”
  • get_autopilot_history

    “Historial del piloto automático de un blog: cada hueco programado, si generó artículo o por qué se saltó (por ejemplo, sin créditos).”

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

    2 inputs, 1 required
    • blogIdstringrequired“Id del blog (de list_blogs).”
    • limitinteger“Cuántos huecos devolver (máximo 50).”
  • get_credit_ledgeron 1 other server

    “Movimientos de créditos de la cuenta (recargas del plan, reservas, cobros por artículo, devoluciones y caducidades), del más reciente al más antiguo.”

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

    4 inputs
    • pageinteger“Página de resultados, desde 1.”
    • limitinteger“Resultados por página (máximo 50).”
    • fromstring“Fecha inicial, YYYY-MM-DD.”
    • tostring“Fecha final, YYYY-MM-DD.”
  • list_ai_modelson 2 other servers

    “Modelos de IA que se pueden elegir para el texto y la portada, con su coste en créditos y si tu plan los permite.”

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

    Takes no inputs.

  • get_publishing_statuson 1 other server

    “Estado de la copia de un artículo en la web externa conectada (por ejemplo WordPress): si está al día, pendiente o con error.”

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

    1 input, 1 required
    • idstringrequired“Id del artículo (de list_articles).”
  • retry_article_publishing

    “Reintenta enviar un artículo a la web externa conectada (por ejemplo WordPress) tras un error.”

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

    1 input, 1 required
    • idstringrequired“Id del artículo (de list_articles).”
  • list_webhookson 73 other servers

    “Webhooks de la cuenta: URL, eventos, si están activos y su último estado.”

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

    Takes no inputs.

  • create_webhookon 39 other servers

    “Crea un webhook HTTPS que recibe un POST firmado en cada evento (hoy `article.published`).”

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

    4 inputs, 2 required
    • urlstringrequired“URL HTTPS que recibirá los eventos.”
    • eventsarrayrequired“Eventos que se envían al webhook (hoy article.published).”
    • descriptionstring“Descripción para reconocer el webhook.”
    • blogIdstring“Id del blog (de list_blogs) cuyos artículos recibe; sin él, los de todos los blogs.”
  • update_webhookon 26 other servers

    “Cambia la URL, los eventos, la descripción o el blog de un webhook (`blogId`; `null` = todos los blogs de la cuenta), o lo pausa (`active: false`).”

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

    6 inputs, 1 required
    • idstringrequired“Id del webhook (de list_webhooks).”
    • urlstring“URL HTTPS nueva del webhook.”
    • eventsarray“Eventos que se envían al webhook (hoy article.published).”
    • descriptionstring“Descripción para reconocer el webhook.”
    • activeboolean“false para pausar el webhook, true para reanudarlo.”
    • blogIdstring or null“Id del blog (de list_blogs) cuyos artículos recibe; null = todos los blogs.”
  • delete_webhookon 56 other servers

    “Borra un webhook y deja de enviarle eventos.”

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

    2 inputs, 1 required
    • idstringrequired“Id del webhook (de list_webhooks).”
    • confirmboolean“true para confirmar una acción irreversible o cara; sin él, la herramienta no actúa.”
  • “Envía un evento de prueba a un webhook; mira el resultado con list_webhook_deliveries.”

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

    1 input, 1 required
    • idstringrequired“Id del webhook (de list_webhooks).”
  • list_webhook_deliverieson 12 other servers

    “Últimos envíos de un webhook: evento, estado, código HTTP, intentos y próximo reintento.”

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

    2 inputs, 1 required
    • idstringrequired“Id del webhook (de list_webhooks).”
    • limitinteger“Cuántas entregas devolver (máximo 50).”
  • retry_webhook_deliveryon 2 other servers

    “Vuelve a enviar una entrega fallida de un webhook.”

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

    2 inputs, 2 required
    • idstringrequired“Id del webhook (de list_webhooks).”
    • deliveryIdstringrequired“Id de la entrega (de list_webhook_deliveries).”

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-19.

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
100% of 126
Tools with a description
100% of 46
Typical description length
154 characters

The tool set

Counted from the listing

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

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 46 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, comparing tools within groups of 40. 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-19 (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://api.blogelia.com/v1/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.blogelia.com/v1/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.blogelia.com/v1/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"mcp","type":"http","url":"https://api.blogelia.com/v1/mcp"}'
Claude Code
claude mcp add --transport http mcp https://api.blogelia.com/v1/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "mcp": {
      "type": "streamableHttp",
      "url": "https://api.blogelia.com/v1/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "mcp": {
      "httpUrl": "https://api.blogelia.com/v1/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.mcp]
url = "https://api.blogelia.com/v1/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "mcp": {
      "url": "https://api.blogelia.com/v1/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://api.blogelia.com/v1/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-19. 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-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Own host

  • security.txt. No security.txt at https://api.blogelia.com/.well-known/ (HTTP 404, 2026-11-19). No security.txt at https://blogelia.com/.well-known/ (HTTP 404, 2026-11-19). Source: api.blogelia.com/.well-known/security.txt · read 2026-11-19.
  • A2A agent card. No A2A agent card at https://api.blogelia.com/.well-known/ (HTTP 404, 2026-11-19). No A2A agent card at https://blogelia.com/.well-known/ (HTTP 404, 2026-11-19). Source: api.blogelia.com/.well-known/agent-card.json · read 2026-11-19.

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 api.blogelia.com/v1/mcpSession openedmatchesour test · 2026-11-19
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-19

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • 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-19. 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.blogelia/mcp

Answered from the data above

Who publishes com.blogelia/mcp?

The registry ties the namespace com.blogelia to the domain blogelia.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

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

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

Has com.blogelia/mcp been security tested?

Partly. 3 of the 15 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.

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-19
  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: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  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

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 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 · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 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
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or 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 · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 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-19, 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,818 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 46 tools, 0 resources, 0 prompts.
  4. 4,301 msFinished: 3 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-19; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-19
MCP capability
tools
our test · 2026-11-19
Transport
streamable HTTP
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · 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-19
Lifecycle status
registry · 2026-11-19
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
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-19

“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.blogelia/mcp: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/com.blogelia/mcp

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: 1 of 2 record checks met

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

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