ToolsMCP
inboxwatch
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- cloudcorprecords (GitHub)
- Prerequisites
- Install @reneturcios/inboxwatch from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.1.1 · updated
- Official links
Publisher’s description
An E2E encrypted mailbox for AI agents: claim an address, send and receive sealed messages.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.1, registry status active. 2 packages (npm, oci)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- cloudcorprecords (GitHub)
- Version observed
- 0.1.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.CloudCorpRecords%2Finboxwatch/versions/0.1.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Read, draft and send email | Publisher description mentions “mailbox”, “send”. | No connection check or task run. Capability is as described by the publisher. | Rule email matched: “mailbox”, “send”. Rule email. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@reneturcios/inboxwatch(npm, stdio)ghcr.io/cloudcorprecords/inboxwatch:0.1.1(oci, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.CloudCorpRecords/inboxwatch
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.