@mailbuttons/mcp-server

MCP@rhalldearnlive
v0.1.0UnknownMITUpdated 2mo agonpmGitHub

Mailbuttons MCP stdio server + Claude Code skill for the governed Agent Mail API (sandbox-by-default, human-in-the-loop escalation). The remote MCP endpoint is served natively by the Mailbuttons backend.

Endpoint healthlive
checked 5 days ago · 396ms · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

@rhalldearn
Identity-verified publisher GitHub@rhalldearn
Verified Aug 11, 2026
39Downloads/wk
2mo agoLast update
Package
AuthorUnknown
LicenseMIT
Version0.1.0
Sourcenpm+mcp-registry
Trust Status
A
80/100Trusted
✓Listed in Forge index+10/10
✓Publisher identity verified+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
Publisher@rhalldearn
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface15 tools · none privileged
Security scan✓ Cleanv0.1.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 2, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · none privileged
Statically extracted from the published packagev0.1.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

mailbuttons_audit_tailRead the most recent governed tool calls for this customer (every call,

Read the most recent governed tool calls for this customer (every call,

No input schema was published for this tool.

mailbuttons_export_auditExport the customer's tamper-evident audit log for a SIEM, including the

Export the customer's tamper-evident audit log for a SIEM, including the

No input schema was published for this tool.

mailbuttons_extract_codeExtract a one-time / verification code (a 4–8 digit number) from recent

Extract a one-time / verification code (a 4–8 digit number) from recent

No input schema was published for this tool.

mailbuttons_generate_policyBuild-time, sandbox-only. Turns an allow/block description into a valid

Build-time, sandbox-only. Turns an allow/block description into a valid

No input schema was published for this tool.

mailbuttons_get_attachment_textExtract inline text from a message attachment (text/* and text/csv). PDF and

Extract inline text from a message attachment (text/* and text/csv). PDF and

No input schema was published for this tool.

mailbuttons_get_draftFetch one held draft in full (recipients, subject, body, the reason it

Fetch one held draft in full (recipients, subject, body, the reason it

No input schema was published for this tool.

mailbuttons_get_messageFetch one message's full text body, recipients, and attachment metadata.

Fetch one message's full text body, recipients, and attachment metadata.

No input schema was published for this tool.

mailbuttons_get_threadFetch every message in a thread (full bodies + attachment metadata), oldest

Fetch every message in a thread (full bodies + attachment metadata), oldest

No input schema was published for this tool.

mailbuttons_list_draftsList sends held for human approval (an external recipient on a sandbox

List sends held for human approval (an external recipient on a sandbox

No input schema was published for this tool.

mailbuttons_list_messagesList delivered messages in a scoped inbox (id, thread, sender, subject,

List delivered messages in a scoped inbox (id, thread, sender, subject,

No input schema was published for this tool.

mailbuttons_propose_senderPropose adding an address to an inbox's send allowlist. This NEVER grants

Propose adding an address to an inbox's send allowlist. This NEVER grants

No input schema was published for this tool.

mailbuttons_request_promotionFile a human-approval request to grant additional capabilities (e.g.

File a human-approval request to grant additional capabilities (e.g.

No input schema was published for this tool.

mailbuttons_run_selftestBuild-time, sandbox-only. Sends an INTERNAL test message, polls for it to

Build-time, sandbox-only. Sends an INTERNAL test message, polls for it to

No input schema was published for this tool.

mailbuttons_scaffold_integrationBuild-time, sandbox-only. Writes a governed send wrapper and an inbound

Build-time, sandbox-only. Writes a governed send wrapper and an inbound

No input schema was published for this tool.

mailbuttons_send_emailSend or reply from a scoped inbox, subject to send policy. Sandbox tokens can

Send or reply from a scoped inbox, subject to send policy. Sandbox tokens can

No input schema was published for this tool.

15 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Mailbuttons MCP stdio server + Claude Code skill for the governed Agent Mail API (sandbox-by-default, human-in-the-loop escalation). The remote MCP endpoint is served natively by the Mailbuttons backend.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-28 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.