@pidgeon-ai/mcp

MCPcon attestationen línea
v0.5.1UnknownMITActualizado hace 1 dnpmGitHub

Model Context Protocol server for Pidgeon. A protocol adapter over the API, and nothing more.

Estado del endpointen línea
comprobado hace 17 h · 378 ms · requiere autenticación
100 % de las últimas 1 comprobación llegó a este endpoint
Funciona en
ClaudeCursorCopilotChatGPTGemini

Inferido de los transportes que declara este listado (stdio, streamable-http). Que un cliente no aparezca aquí no significa que se haya descartado: simplemente Forge no puede confirmarlo.

Build con attestation
Una attestation de procedencia verificada vincula este artefacto al repositorio listado. Nadie ha reclamado todavía el listado: esto demuestra dónde se construyó el código, no quién lo respalda.
15Descargas/sem.
hace 1 dÚltima actualización
Necesita 1 credencial antes de poder ejecutarse
  • PIDGEON_API_KEYClave de APIobligatoria

    Your Pidgeon API key (pgn_live_…). Make one under Developers → API keys, or let an agent sign itself up: https://pidgeon.ai/skill.md

Declarado por el autor en el registro oficial de MCP. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Paquete
AutorUnknown
LicenciaMIT
Versión0.5.1
Fuentenpm+mcp-registry
Estado de confianza
B
65/100Bueno
✓Listado en el índice de Forge+10/10
✓Identidad verificada · build con attestation+20/20
—Firma de publicación Ed25519+0/5
→ Se incluye automáticamente cuando el publicador ejecuta `forge publish`
—Verificación de dominio+0/5
→ Publicador: aloja /.well-known/forge.json en la página del paquete con { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—Coincidencia de maintainer en npm+0/5
→ Publicador: añade el login de GitHub verificado a los maintainers del paquete de npm (npm owner add <login>)
✓Análisis CVE · limpio+30/30
—Análisis estático · limpio+0/20
→ Se han detectado scripts de instalación sospechosos o código ofuscado
Pégalo en Claude Code, Cursor o cualquier asistente de IA para corregir todas las carencias
EstadoIdentidad verificada
PublicadorSin verificar
FirmaSin firmar
Dominio—
Procedencia✓ Verificado con Sigstore · 8aafd88
Dependencias✓ 60 resueltas+ · ninguna vulnerable
Superficie de herramientas26 herramientas · 1 privilegiadas
Análisis de seguridad⚠ Avisos (1)v0.8.0 · hoy¿Qué tan bien funciona este análisis?
PROMPTtool:send_messageExfiltration-shaped instruction
EvaluacionesNinguna
Indexado17 oct 2026

La verificación confirma la identidad del publicador (la propiedad del repo), no la seguridad del código. El análisis de seguridad cubre los CVE conocidos y los scripts de instalación sospechosos.

Herramientas

26 herramientas · 1 privilegiadas · 1 marcadas por inyección
Extraído estáticamente del paquete publicadov0.8.0 · 10h ago

Leído del código que npm publica realmente, en el momento del análisis. El paquete nunca se ejecutó. Las herramientas registradas dinámicamente en tiempo de ejecución, o escondidas en código empaquetado o minificado, pueden pasarse por alto — así que esto es un mínimo de la superficie de herramientas, no un censo completo.

list_addressesThe addresses this credential can reach. Use `pod_id` to list one pod’s — one of your own customers — or `tenant_id` for your own opaque grouping.

The addresses this credential can reach. Use `pod_id` to list one pod’s — one of your own customers — or `tenant_id` for your own opaque grouping.

No se publicó ningún esquema de entrada para esta herramienta.

create_addressSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

get_addressOne address, by id. Answers its type, its capabilities, its send policy and its end date, which is how to check what an address is allowed to do before using it.

One address, by id. Answers its type, its capabilities, its send policy and its end date, which is how to check what an address is allowed to do before using it.

No se publicó ningún esquema de entrada para esta herramienta.

list_threadsConversations in one address, newest first. Filter by `status` for the queue an agent should be working, by `owner_type` for what kind of thing is answering, or by `assignee_id` for what one person has taken — `unassigned` is the queue nobody has.

Conversations in one address, newest first. Filter by `status` for the queue an agent should be working, by `owner_type` for what kind of thing is answering, or by `assignee_id` for what one person has taken — `unassigned` is the queue nobody has.

No se publicó ningún esquema de entrada para esta herramienta.

get_threadOne conversation, by id. Every webhook payload carries a `thread_id`, so this is how a handler turns an event into the conversation it is about.

One conversation, by id. Every webhook payload carries a `thread_id`, so this is how a handler turns an event into the conversation it is about.

No se publicó ningún esquema de entrada para esta herramienta.

list_messagesThe messages of one conversation, oldest first — the text to read before replying. Bodies are here; attachments are metadata only.

The messages of one conversation, oldest first — the text to read before replying. Bodies are here; attachments are metadata only.

No se publicó ningún esquema de entrada para esta herramienta.

search_messagesFull-text search across every address this credential can reach, ranked by relevance. Name an `identity_id` to search exactly one. Every result carries the `identity_id` it was found in, because a hit you cannot attribute to an address is a hit you cannot open.

Full-text search across every address this credential can reach, ranked by relevance. Name an `identity_id` to search exactly one. Every result carries the `identity_id` it was found in, because a hit you cannot attribute to an address is a hit you cannot open.

No se publicó ningún esquema de entrada para esta herramienta.

send_messageriesgo de inyecciónSend from an address this credential may send as. Refused if the address’s send policy does not permit the recipient, or if the recipient previously bounced or reported mail as spam.

Send from an address this credential may send as. Refused if the address’s send policy does not permit the recipient, or if the recipient previously bounced or reported mail as spam.

INYECCIÓNExfiltration-shaped instructionSend from an address this credential may send as. Refused if the address’s send policy does not …

No se publicó ningún esquema de entrada para esta herramienta.

get_messageSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

await_messageSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

reply_to_messageThe recipients, the subject and the thread are read off the message being answered, so you bring the words and nothing else. Use `to` only to change who it goes to.

The recipients, the subject and the thread are read off the message being answered, so you bring the words and nothing else. Use `to` only to change who it goes to.

No se publicó ningún esquema de entrada para esta herramienta.

update_threadWho owns a conversation and where it has got to. `owner_type: "human"` hands it to a person — it appears in the web inbox and `thread.updated` tells whatever was driving it that it no longer is; `"agent"` takes it back. `status` is the queue it sits in, and `assignee_id` names which person has it.

Who owns a conversation and where it has got to. `owner_type: "human"` hands it to a person — it appears in the web inbox and `thread.updated` tells whatever was driving it that it no longer is; `"agent"` takes it back. `status` is the queue it sits in, and `assignee_id` names which person has it.

No se publicó ningún esquema de entrada para esta herramienta.

update_messageSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

list_send_rulesThe allow and block list of one address, and the send policy it hangs off. Read this when a send was refused.

The allow and block list of one address, and the send policy it hangs off. Read this when a send was refused.

No se publicó ningún esquema de entrada para esta herramienta.

list_receive_rulesThe rules that decide what reaches one address — reject, spam, trash, archive or inbox, per sender or per domain. Read this when mail you expected did not arrive.

The rules that decide what reaches one address — reject, spam, trash, archive or inbox, per sender or per domain. Read this when mail you expected did not arrive.

No se publicó ningún esquema de entrada para esta herramienta.

list_foldersEvery folder of one address with its counts. `total` and `unread` are null where we do not count that folder — null is "we do not say", not zero.

Every folder of one address with its counts. `total` and `unread` are null where we do not count that folder — null is "we do not say", not zero.

No se publicó ningún esquema de entrada para esta herramienta.

list_folderOne folder of one address, newest first, a conversation per row — where `list_threads` says which conversations exist, this says where they are filed and what they look like in a list. The response carries a `sync_cursor`: hand it to `list_changes` to be told what moved instead of reading the folde…

One folder of one address, newest first, a conversation per row — where `list_threads` says which conversations exist, this says where they are filed and what they look like in a list. The response carries a `sync_cursor`: hand it to `list_changes` to be told what moved instead of reading the folde…

No se publicó ningún esquema de entrada para esta herramienta.

list_changesEverything that moved in one mailbox since a `sync_cursor`, arrivals included, so a long-running agent does not re-read a folder to find one new message. `since` is the `sync_cursor` from `list_folder`, never a page cursor. A cursor older than thirty days is refused with `resync`: list the folders…

Everything that moved in one mailbox since a `sync_cursor`, arrivals included, so a long-running agent does not re-read a folder to find one new message. `since` is the `sync_cursor` from `list_folder`, never a page cursor. A cursor older than thirty days is refused with `resync`: list the folders…

No se publicó ningún esquema de entrada para esta herramienta.

list_eventsEvery event across every mailbox this credential reaches — mail received, sent, delivered, bounced, filed. Workspace-wide unless you name an `identity_id`. Pass `after` with a timestamp to read forward from a moment; with neither `after` nor `cursor` it returns the newest first.

Every event across every mailbox this credential reaches — mail received, sent, delivered, bounced, filed. Workspace-wide unless you name an `identity_id`. Pass `after` with a timestamp to read forward from a moment; with neither `after` nor `cursor` it returns the newest first.

No se publicó ningún esquema de entrada para esta herramienta.

list_labelsLabels belong to an address, not to the workspace, so the same name on three addresses is three labels with three ids. Read this before applying one.

Labels belong to an address, not to the workspace, so the same name on three addresses is three labels with three ids. Read this before applying one.

No se publicó ningún esquema de entrada para esta herramienta.

create_labelA label on one address. `colour` is one of eight names — slate, red, amber, green, teal, blue, violet, pink — and defaults to slate; it is not a hex value.

A label on one address. `colour` is one of eight names — slate, red, amber, green, teal, blue, violet, pink — and defaults to slate; it is not a hex value.

No se publicó ningún esquema de entrada para esta herramienta.

apply_labelThe label has to belong to the same address the conversation is in — `list_labels` for that address gives you the right id. Applying is how an automation records what it decided, since it cannot mark anything read.

The label has to belong to the same address the conversation is in — `list_labels` for that address gives you the right id. Applying is how an automation records what it decided, since it cannot mark anything read.

No se publicó ningún esquema de entrada para esta herramienta.

remove_labelprivilegiadaRemoves one label from one conversation. The label itself is untouched.

Removes one label from one conversation. The label itself is untouched.

No se publicó ningún esquema de entrada para esta herramienta.

list_podsA pod is a container for one of your own customers: it holds addresses and domains, and **mail sent from it lands on its own sending reputation**, so one customer cannot damage another’s delivery. Every account has one to start with, marked `is_default` — that is where an address goes when you name…

A pod is a container for one of your own customers: it holds addresses and domains, and **mail sent from it lands on its own sending reputation**, so one customer cannot damage another’s delivery. Every account has one to start with, marked `is_default` — that is where an address goes when you name…

No se publicó ningún esquema de entrada para esta herramienta.

create_podA container for one of your customers, with its own sending reputation. Give it a `name` a person would recognise and, if your own system has an id for this customer, `client_id` — carried and returned, never parsed. Then pass the new pod’s id as `pod_id` to `create_address`. There is no delete: a…

A container for one of your customers, with its own sending reputation. Give it a `name` a person would recognise and, if your own system has an id for this customer, `client_id` — carried and returned, never parsed. Then pass the new pod’s id as `pod_id` to `create_address`. There is no delete: a…

No se publicó ningún esquema de entrada para esta herramienta.

get_metricsSin descripción publicada

Esta herramienta no publicó ninguna descripción. Forge no se la inventa.

21 de 26 herramientas publicaron una descripción.

Los nombres y descripciones de las herramientas los escribe el publicador y se muestran literalmente como texto inerte. Son las cadenas que un cliente MCP pasa al modelo, así que Forge las analiza en busca de patrones de inyección de prompts — cualquier hallazgo aparece junto al análisis de seguridad de arriba. «Privilegiada» es una coincidencia de palabra clave en el nombre de la herramienta, no una auditoría de lo que hace: un nombre inofensivo puede hacer cualquier cosa.

Acerca de

Model Context Protocol server for Pidgeon. A protocol adapter over the API, and nothing more.

Palabras clave
pidgeonemailmcpmodel-context-protocol
Alternativas
Comparando superficies de herramientas…

Árbol de dependencias

Lo que un análisis de Forge resolvió a partir de los metadatos de npm el 2026-10-17: resolución observada, no una declaración del publicador.

60 paquetes resueltos · 3 directos · ninguno con avisos de seguridad La resolución se detiene en la profundidad 4 y en 60 paquetes.

El rastreo se detuvo en el límite de profundidad 4. Nada por debajo de ese nivel llegó a resolverse.

El rastreo se detuvo en el límite de 60 paquetes. El resto del árbol nunca se resolvió.

Hay 36 paquetes resueltos más que no se dibujan aquí (límite de visualización: 24). Toda dependencia con avisos de seguridad se dibuja aunque se supere el límite. Inventario completo (SBOM CycloneDX)

Declaradas pero no resueltas

55 dependencias declaradas nunca llegaron al árbol. Faltan en la resolución de Forge, no en el paquete.

+43 más sin listar. Los recuentos por motivo de arriba las incluyen todas.

No se siguen: peerDependencies. Este árbol cubre solo dependencias en tiempo de ejecución, así que lo que estas arrastren nunca se resolvió.

Temas

Relacionados en email