LeashIndex Get the report

Index / messaging

io.github.nikolausm/imap-mcp-server

io-github-nikolausm-imap-mcp-server declares 40 capabilities across 40 tools, with 2 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

99/100 exposureHigh exposure

Manifest recorded 2026-11-02 from tools/list answered by the npm package imap-mcp-server@2.2.0 (published to npm as imap-mcp-server, listed in the official MCP registry as io.github.nikolausm/imap-mcp-server 2.2.0), run in an isolated container with no network access and no credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 40 tools

40 of 40 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 22 of 40 tools

22 tools are classified as irreversible and declare no limit.

high · no-expiry · All 40 tools

40 of 40 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 40 tools

40 of 40 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 10 of 40 tools

10 tools can modify data and declare no limit.

low · uncapped-read · 8 of 40 tools

8 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
imap_add_accountwrite inferred
imap_update_accountwrite inferred
imap_list_accountsread inferred
imap_remove_accountdelete inferred
imap_connectwrite assumed
imap_disconnectwrite assumed
imap_test_accountwrite assumed
imap_search_emailssend inferred
imap_get_emailsend inferred
imap_upload_filewrite inferred
imap_download_attachmentsend inferred
imap_mark_as_readread inferred
imap_mark_as_unreadsend inferred
imap_flag_emailsend inferred
imap_unflag_emailsend inferred
imap_add_keywordwrite inferred
imap_remove_keyworddelete inferred
imap_delete_emailsend inferred
imap_move_emailsend inferred
imap_bulk_deletedelete inferred
imap_bulk_delete_by_searchdelete inferred
imap_get_latest_emailssend inferred
imap_send_emailsend inferred
imap_save_draftsend inferred
imap_reply_to_emailsend inferred
imap_forward_emailsend inferred
imap_find_thread_messagessend inferred
imap_find_email_by_message_idsend inferred
imap_list_foldersread inferred
imap_folder_statusread inferred
imap_create_folderwrite inferred
imap_get_unread_countread inferred
imap_check_spamread inferred
imap_delete_spamdelete inferred
imap_domain_statsread inferred
imap_add_spam_domainwrite inferred
imap_remove_spam_domaindelete inferred
imap_add_whitelist_domainwrite inferred
imap_list_spam_domainsread inferred
imap_delete_by_domaindelete inferred
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.