github TypeScript re-analysis due

ni-c/imap-mcp

MCP server for IMAP mailboxes: read, search, organise and draft mail — it deliberately cannot send

Drift inferred · capture-to-capture

No drift recorded — single capability capture; advisories appear once its surface changes.

capabilities 11 tools

transport stdio · http verified reported listed in the official MCP registry counts 11 tools · 0 res · 0 prompts permission surface via code analysis

code evidence vHEAD · github-tarball

evidence-backed findings quoted directly from the published source artifact — not inferred

code files: 42

fs (weak) ni-c-imap-mcp-16c680c/docs/.vitepress/config.ts :1 import { readFileSync } from 'node:fs';
fs (weak) ni-c-imap-mcp-16c680c/scripts/gen-assets.mjs :31 import { readFileSync, writeFileSync, mkdirSync } from 'node:fs';
fs ni-c-imap-mcp-16c680c/src/download.ts :1 import { open } from 'node:fs/promises';
fs (weak) ni-c-imap-mcp-16c680c/test/download.test.ts :8 } from 'node:fs/promises';

net ni-c-imap-mcp-16c680c/src/imap.ts :43 fetch(
net ni-c-imap-mcp-16c680c/src/resources.ts :61 for await (const message of connection.fetch(
net ni-c-imap-mcp-16c680c/src/tools/read.ts :533 for await (const message of connection.fetch([uid], query, { uid: true })) {
net (weak) ni-c-imap-mcp-16c680c/test/fake-imap.ts :238 async *fetch(

prepublishOnly ni-c-imap-mcp-16c680c/package.json :41 npm run lint && npm run build && npm test

show 2 more