# replylayer-mcp

MCP server for ReplyLayer — safe email for AI agents

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.15.1
- **Author:** Unknown
- **License:** MIT
- **npm:** replylayer-mcp
- **Endpoints:** streamable-http https://api.replylayer.ai/v1/mcp
- **Source:** https://github.com/replylayer/rly
- **Endpoint health:** reachable (last checked 2026-10-06T20:15:15.235Z, 1 sample) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-06T20:14:50.064Z
- **Version scanned:** 0.15.1
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `add_inbound_allowlist_bulk` — Bulk-add up to 1000 sender email addresses or @domain patterns to the inbound allowlist for a mailbox in a single call. Useful for onboarding/migration when imp
- `add_inbound_allowlist_entry` — Add a sender (email or @domain) to the inbound allowlist for a mailbox. When the mailbox is in `allowlist` mode, only senders matching an entry on this list wil
- `add_inbound_blocklist_bulk` — Bulk-add up to 1000 sender email addresses or @domain patterns to the account-wide inbound blocklist in a single call. Useful for onboarding/migration when impo
- `add_inbound_blocklist` — Add an email or domain pattern to the inbound (incoming) blocklist. Mirrors `add_suppression` for the inbound side: customer-protective do-not-receive list. Acc
- `add_recipient` — Add a person to the account's recipient list so you can email them. Only for accounts on the free Sandbox; other accounts don't use this list and get an error h
- `add_suppression`
- `add_suppressions_bulk` — Bulk-add up to 1000 email addresses or @domain patterns to the do-not-contact list in a single call. Useful for onboarding/migration when importing an existing 
- `approve_review` — Approve a state="pending_review" message and dispatch it. Wire status reports the dispatch outcome ("sent" or "blocked" — release-style); audit_log + message.re
- `block_quarantined_message` — Block a state="quarantined" INBOUND message (→ terminal blocked, no delivery). INBOUND-ONLY: the tool pre-fetches the message and refuses an outbound row (manag
- `create_draft`
- `delete_draft` — Soft-delete a draft (sets state="deleted"; hides it from list_drafts). The row remains in the database and the raw MIME body persists in storage for operator re
- `delete_message` — Permanently delete a message: soft-deletes the row and purges its raw MIME and attachment derivatives from object storage. Works on any direction (inbound or ou
- `deny_review` — Deny a state="pending_review" message; terminal block (no dispatch). Audit_log + message.review.denied webhook fire on commit. Auth: admin API keys + session on
- `get_account_usage` — Get account usage, limits, storage quota state, and storage byte breakdown.
- `get_agent_quota` — Get the current send-budget quota (sends today, effective daily limit, remaining, reset time, bound mailbox IDs). Works with agent-scoped keys. Includes a warmu
- `get_attachment_preview` — Get a derived text preview of an inbound message attachment. Returns extracted text for plain-text, CSV, PDF, and Office (DOCX/PPTX/XLSX) attachments on mailbox
- `get_draft` — Read a specific draft by ID. Returns the full draft including body, scan results, scheduled-send fields, and sub-address fields if set.
- `get_link_scanning_status` — Get malicious link scanning (URL reputation) activation status
- `get_thread` — Read a full email thread as one ordered conversation (every message in the thread, oldest → newest, safe-view only). Pass the thread_id from list_threads or a m
- `list_allowlist_blocked_attempts`
- `list_allowlist`
- `list_drafts` — List drafts in a ReplyLayer mailbox. Drafts are scan-then-review-then-send entries; use create_draft to make one and send_draft to dispatch it.
- `list_inbound_allowlist` — List per-mailbox inbound allowlist entries (senders permitted in `allowlist` mode). Mirrors `list_allowlist` for the inbound side. Read-only. Returns up to `lim
- `list_inbound_blocklist` — List account-wide inbound sender blocklist entries (the do-not-receive list). Mirrors `list_suppressions` for the inbound side. Returns up to `limit` rows (defa
- `list_inbound_firewall_blocked_attempts` — List incoming senders rejected by the inbound firewall for a mailbox. Default aggregated view groups by (sender, matched_field, mode, reason_code) ordered by mo
- `list_mailboxes` — List all mailboxes on the account. Returns name, full address, status, and the recipient-visible From identity (effective_from_display) for each mailbox.
- `list_messages` — List / search messages in a ReplyLayer mailbox. Filter by keyword search, sender, date range, direction, and status — including the held-mail states for triage:
- `list_recipients` — List recipients with confirmation status. Sandbox-tier accounts can only send to confirmed recipients.
- `list_suppressions` — List addresses on the do-not-contact list (suppressions). Includes both system-added entries (hard bounces, spam complaints, RFC 8058 unsubscribes) and customer
- `list_threads`
- `mark_message_read`
- `mark_thread_read`
- `read_message`
- `release_firewall_blocked_message`
- `release_quarantined_message`
- `remove_suppression`
- `reply_to_message`
- `report_and_block`
- `send_draft`
- `send_email`

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"replylayer\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"replylayer-mcp\"\n      ],\n      \"env\": {\n        \"REPLYLAYER_API_KEY\": \"<YOUR_REPLYLAYER_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `REPLYLAYER_API_KEY` — Replylayer API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; runs locally and hosted.
- Floor 57, ceiling 57 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/replylayer-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/replylayer-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/replylayer-mcp
- HTML page: https://forgeregistry.com/registry/replylayer-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.