ooruby: verified AI agents and MCP servers

Agentmail MCP

stdio compatibility bridge for the hosted AgentMail MCP server

Not claimed by its maker. Is this yours? Prove it and answer the findings

Not yet tested

Licence and provenance: finding; no LICENCE file at the root (.)

Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.

What this does not cover

Everything. Treat it as you would software from anywhere else.

Corrected after a reading by hand on 2026-09-30

Data handling disclosed: the automated note “no statement of what it reads, writes or sends (README.md)” was withdrawn. The README says exactly what it sends and to whom; it just never uses the words the automated check looks for.

How it was read

Receipt history: every signed receipt for every version of this listing, and what changed between them.

What it does

stdio compatibility bridge for the hosted AgentMail MCP server

Compare with

Compare all 4

How far this has been checked

Static scanned

What it establishes: Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
What it does not: How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
Exactly what was read: Version 1.1.0, the file with digest sha512-D3QFNkh+iJndZ5ocboM2RHLcxLJ3ma4z/Ybgx8u/D/bDByCa9jETPxRyHW9Ey8UDH1JjLRFFGo2ZA8qjbmKm4Q==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.

How the rungs work

Adding it

Paste this into your client's MCP configuration.

{
  "mcpServers": {
    "agentmail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agentmail-mcp@1.1.0"
      ]
    }
  }
}

Or run it directly.

npx -y agentmail-mcp@1.1.0

Pinned to 1.1.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.

16,471 installs last month · build provenance signed · no published advisories · version current · checked 2026-10-05

Where this came from

Registry: npm
Package: agentmail-mcp
Version read: 1.1.0
Resolved: 2026-09-23

Open the source

Built from source, attested

npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.

Repository: github.com/agentmail-to/agentmail-mcp
Commit: e1cf3002259b
Built by: github.com/actions/runner/github-hosted

The badge, if this is your listing

It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.

[![ooruby: static scanned](https://ooruby.com/api/badge/agentmail-mcp)](https://ooruby.com/market/agentmail-mcp)

About this listing

Kind: MCP server
Category: Support
Pricing: Free
Sandbox: No
Hosted: No
Updated: 2026-09-16

Similar MCP servers

Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.