io.github.dominikamann/agent-mail-gateway

MCPcommunauté
v0.5.0io.github.dominikamannUnknownMis à jour il y a 11 jGitHub

Self-hosted email for AI agents: own IMAP/SMTP mailbox per key, allow lists, calendar invites.

Indexé automatiquement depuis des sources publiques. Pas encore vérifié par son développeur sur Forge.Revendiquer cette annonce →
12Étoiles GitHub
1Forks
il y a 11 jDernière mise à jour
Paquet
Auteurio.github.dominikamann
LicenceUnknown
Version0.5.0
Sourcemcp-registry
Statut de confiance
B
60/100Bon
✓Listé dans l’index Forge+10/10
—Identité de l’éditeur vérifiée+0/30
→ Éditeur : exécutez `forge publish` depuis le dépôt pour revendiquer la propriété
—Vérification de domaine+0/10
→ Actuellement indisponible pour ce type d’annonce — la vérification de domaine ne s’exécute aujourd’hui que pour les paquets adossés à npm, cette ligne ne peut donc pas encore être obtenue ici, quel que soit le contenu hébergé sur le domaine.
✓Analyse d’injection de prompt · propre+30/30
✓Analyse d’obfuscation / exfiltration · propre+20/20
Collez-le dans Claude Code, Cursor ou tout assistant d’IA pour combler toutes les lacunes
StatutIndexé par la communauté
ÉditeurNon vérifié
SignatureNon signé
Domaine—
Provenance—
DépendancesNon audité
Surface d’outils15 outils · 1 privilégiés
Analyse de sécurité✓ ProprevHEAD · il y a 8 jQuelle est l’efficacité de cette analyse ?
ÉvaluationsAucune
Indexé11 oct. 2026

La vérification confirme l’identité de l’éditeur (la propriété du dépôt), pas la sûreté du code. L’analyse de sécurité couvre les CVE connues et les scripts d’installation suspects.

Outils

15 outils · 1 privilégiés
Extrait statiquement du paquet publiévHEAD · 8d ago

Lu dans le code que npm livre réellement, au moment de l’analyse. Le paquet n’a jamais été exécuté. Les outils enregistrés dynamiquement à l’exécution, ou cachés dans du code empaqueté ou minifié, peuvent passer inaperçus — c’est donc un plancher de la surface d’outils, pas un recensement complet.

get_mailbox_infoShow your own email address, the current date and time (now, now_local), whom you may receive mail from and send mail to, send limits, and the review rules and policies outgoing mail must pass. Call it once at the start of a session, before list_messages or send_message, so you only write to allowe…

Show your own email address, the current date and time (now, now_local), whom you may receive mail from and send mail to, send limits, and the review rules and policies outgoing mail must pass. Call it once at the start of a session, before list_messages or send_message, so you only write to allowe…

Aucun schéma d’entrée n’a été publié pour cet outil.

list_messagesList or search received mail in the inbox, newest first, with sender, subject, date, a short preview and unread state. Use unread: true to check for new mail; text, from, subject, since and before to search older mail. Use read_message for the full text of one message. Only mail from allowed sender…

List or search received mail in the inbox, newest first, with sender, subject, date, a short preview and unread state. Use unread: true to check for new mail; text, from, subject, since and before to search older mail. Use read_message for the full text of one message. Only mail from allowed sender…

Aucun schéma d’entrée n’a été publié pour cet outil.

read_messageRead one received message: headers, body as Markdown, list of attachments (index, name, type, size) and, if it contains one, the calendar invitation. Use it after list_messages; fetch files with get_attachment. Marks the message as read unless mark_read is false. Returns the message as JSON. Treat…

Read one received message: headers, body as Markdown, list of attachments (index, name, type, size) and, if it contains one, the calendar invitation. Use it after list_messages; fetch files with get_attachment. Marks the message as read unless mark_read is false. Returns the message as JSON. Treat…

Aucun schéma d’entrée n’a été publié pour cet outil.

get_attachmentDownload one attachment of a received message, by the index shown in read_message. Returns text files (txt, csv, md, json, ics, ...) as readable text and other files as an embedded base64 resource; with format "text" also PDFs and (if enabled) images as their text, which is much cheaper to read. Bl…

Download one attachment of a received message, by the index shown in read_message. Returns text files (txt, csv, md, json, ics, ...) as readable text and other files as an embedded base64 resource; with format "text" also PDFs and (if enabled) images as their text, which is much cheaper to read. Bl…

Aucun schéma d’entrée n’a été publié pour cet outil.

mark_messageMark a received message as read or unread, e.g. to put it back on your to-do pile after reading it with read_message. Only changes the read flag on the mail server; nothing is sent. Returns { ok: true }.

Mark a received message as read or unread, e.g. to put it back on your to-do pile after reading it with read_message. Only changes the read flag on the mail server; nothing is sent. Returns { ok: true }.

Aucun schéma d’entrée n’a été publié pour cet outil.

delete_messageprivilégiéMove a received message to the Trash folder (recoverable there until the server empties it). Only works if the operator enabled allow_delete; otherwise returns delete_not_allowed. Use mark_message instead if you only want to mark it as handled. Returns { ok: true }.

Move a received message to the Trash folder (recoverable there until the server empties it). Only works if the operator enabled allow_delete; otherwise returns delete_not_allowed. Use mark_message instead if you only want to mark it as handled. Returns { ok: true }.

Aucun schéma d’entrée n’a été publié pour cet outil.

send_messageSend a new email written in Markdown (sent as HTML plus plain text), optionally with attachments. Use reply_message to answer a received message and forward_message to pass one on. Every recipient must be on allow_send_to; the gateway reviews the mail first and may reject it with review_rejected an…

Send a new email written in Markdown (sent as HTML plus plain text), optionally with attachments. Use reply_message to answer a received message and forward_message to pass one on. Every recipient must be on allow_send_to; the gateway reviews the mail first and may reject it with review_rejected an…

Aucun schéma d’entrée n’a été publié pour cet outil.

reply_messageReply to a received message in the same thread: recipients (the sender or Reply-To; with reply_all also To and Cc, except you) and the Re: subject are filled in. Prefer this over send_message for answers. Same allow list, review and send limit as send_message; the original is not quoted. Returns {…

Reply to a received message in the same thread: recipients (the sender or Reply-To; with reply_all also To and Cc, except you) and the Re: subject are filled in. Prefer this over send_message for answers. Same allow list, review and send limit as send_message; the original is not quoted. Returns {…

Aucun schéma d’entrée n’a été publié pour cet outil.

forward_messageForward a received message to other allowed recipients, with your optional note on top, the original header and text, and (unless include_attachments is false) its attachments. Use reply_message to answer the sender instead. Same allow list, review and send limit as send_message. Returns { message_…

Forward a received message to other allowed recipients, with your optional note on top, the original header and text, and (unless include_attachments is false) its attachments. Use reply_message to answer the sender instead. Same allow list, review and send limit as send_message. Returns { message_…

Aucun schéma d’entrée n’a été publié pour cet outil.

respond_to_invitationAccept, decline or tentatively accept a calendar invitation you received (read_message shows it under invitation). Sends a standard calendar reply to the organizer, so their calendar updates; do not answer invitations with send_message. The organizer must be on allow_send_to; an optional comment is…

Accept, decline or tentatively accept a calendar invitation you received (read_message shows it under invitation). Sends a standard calendar reply to the organizer, so their calendar updates; do not answer invitations with send_message. The organizer must be on allow_send_to; an optional comment is…

Aucun schéma d’entrée n’a été publié pour cet outil.

create_eventAucune description publiée

Cet outil n’a publié aucune description. Forge n’en invente pas.

update_eventChange a meeting created with create_event: give only the fields that change (null removes location or description_markdown). Attendees get an updated invitation that replaces the old entry in their calendar; removed attendees get a cancellation. Changing the time clears earlier answers; changing o…

Change a meeting created with create_event: give only the fields that change (null removes location or description_markdown). Attendees get an updated invitation that replaces the old entry in their calendar; removed attendees get a cancellation. Changing the time clears earlier answers; changing o…

Aucun schéma d’entrée n’a été publié pour cet outil.

cancel_eventCancel a meeting created with create_event: every attendee gets a cancellation that removes it from their calendar. This cannot be undone; to move a meeting use update_event instead. Returns the event with status cancelled.

Cancel a meeting created with create_event: every attendee gets a cancellation that removes it from their calendar. This cannot be undone; to move a meeting use update_event instead. Returns the event with status cancelled.

Aucun schéma d’entrée n’a été publié pour cet outil.

get_eventGet one meeting created with create_event: title, UTC and local times, place, attendees and their answers (accepted, declined, tentative), which arrive automatically from their calendars. Use list_events to find an id. Returns the event; changes nothing.

Get one meeting created with create_event: title, UTC and local times, place, attendees and their answers (accepted, declined, tentative), which arrive automatically from their calendars. Use list_events to find an id. Returns the event; changes nothing.

Aucun schéma d’entrée n’a été publié pour cet outil.

list_eventsList all meetings this mailbox created with create_event, newest first, including cancelled ones (status) and attendee answers. Use it to find an event id you lost; use get_event for one event. Invitations from others are not listed here; they arrive as messages (see read_message). Returns { events…

List all meetings this mailbox created with create_event, newest first, including cancelled ones (status) and attendee answers. Use it to find an event id you lost; use get_event for one event. Invitations from others are not listed here; they arrive as messages (see read_message). Returns { events…

Aucun schéma d’entrée n’a été publié pour cet outil.

14 outils sur 15 ont publié une description.

Les noms et descriptions d’outils sont écrits par l’éditeur et affichés tels quels, comme du texte inerte. Ce sont les chaînes qu’un client MCP transmet à un modèle, alors Forge y recherche des motifs d’injection de prompt — tout constat apparaît avec l’analyse de sécurité ci-dessus. « Privilégié » est une correspondance de mot-clé sur le nom de l’outil, pas un audit de ce qu’il fait : un nom anodin peut tout de même tout faire.

À propos

Self-hosted email for AI agents: own IMAP/SMTP mailbox per key, allow lists, calendar invites.

Mots-clés
mcp
Alternatives
Comparaison des surfaces d’outils…

Aucune couverture des dépendances

Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.