inboxwatch
io.github.CloudCorpRecords/inboxwatch
About inboxwatch
inboxwatch is an MCP server published by the GitHub account CloudCorpRecords. An E2E encrypted mailbox for AI agents: claim an address, send and receive sealed messages.
It runs on your own machine: your AI client starts it from the npm package @reneturcios/inboxwatch at version 0.1.1.
It asks for no keys or passwords.
Version 0.1.1 was published on 26 October 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
This server declares no environment variables, so it asks for no keys or settings.
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/CloudCorpRecords/inboxwatch |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for no secrets |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account CloudCorpRecords |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | @reneturcios/inboxwatch@0.1.1 runs nothing at install |
| Code red flags | Pass | Read 8 files in @reneturcios/inboxwatch@0.1.1: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 8 files, including comments and the README |
Popularity & health: 52 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
0 forks, 0 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.CloudCorpRecords/inboxwatch |
|---|---|
| Publisher | GitHub account CloudCorpRecords |
| How the name is verified | Name verified via GitHub account CloudCorpRecords. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | npm @reneturcios/inboxwatch 0.1.1 (stdio)oci ghcr.io/cloudcorprecords/inboxwatch:0.1.1 no version given (stdio) |
| Version | 0.1.1 |
| Published | |
| Last updated | |
| Source repository | https://github.com/CloudCorpRecords/inboxwatch |
| Website | None linked |
| Category | Email & messaging (assigned by keyword rule, not by hand) |
Related servers in Email & messaging
- threadline-mcp7/7Agent-to-agent messaging relay. Discover agents, send messages, and…
- clawaimail7/7Email infrastructure for AI agents. Create inboxes, send/receive…
Bird3/3Send and receive across email, SMS, WhatsApp, and voice. One API,…
Cooper Email4/4Email inboxes for AI agents: send, receive, search, drafts with…- npubmail4/4Email inbox for AI agents, owned by a Nostr key. No signup or API…
- Dead Simple Email8/8Give an agent its own inbox: send, receive, and pull signup codes…