Server definition

Hash: sha256:50e763631763047a8a1c31b2caa60d5fca1d0ed8529bc55555b9b62fb659fd2d
What it is: What a remote MCP server returned when asked what it offers: 6 tools

The blob, as servednamed by its sha256

{
  "instructions": "RadMail is pre-release. The engine is live in a test bed on two real businesses today; the commercial multi-tenant product is launch-gated. The MCP sandbox you connect to is real and runnable now (heuristic, in-memory, free, no credentials), but it is the sandbox engine — not the production multi-tenant engine.\n\nRadMail's MCP server exposes only read, triage, search, draft, and read-only diagnostic tools. There is no tool that auto-sends money, changes banking details, or makes first contact with a new party — those stay human-only, forever, as a defense against business-email-compromise (BEC) fraud. An agent literally cannot use RadMail to do the dangerous thing.\n\nCompliance is a shared responsibility. RadMail is a tool that supports your program, not a compliance guarantee, and it does not by itself make any organization compliant. For regulated tiers RadMail signs a BAA and processes on BAA-covered, audited infrastructure. RadMail is not HIPAA-certified, FedRAMP-authorized, or SOC 2-certified.\n\nConnect docs: https://radmail.ai/for-agents",
  "tools": [
    {
      "description": "Draft a reply for a thread. It returns text for a human to review — it does not and cannot send it.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "guidance": {
            "description": "Optional steer for the draft. Never sent — review-only.",
            "type": "string"
          },
          "message_id": {
            "description": "An id from triage_inbox to draft a reply for.",
            "type": "string"
          }
        },
        "required": [
          "message_id"
        ],
        "type": "object"
      },
      "name": "draft_reply",
      "outputSchema": null
    },
    {
      "description": "Extract the open commitments in the correspondence, both owed by you and owed to you, with who and by-when.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "list_commitments",
      "outputSchema": null
    },
    {
      "description": "Return only the 'Right Now' lane — the most recent and most important messages that genuinely can't be missed.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "list_right_now",
      "outputSchema": null
    },
    {
      "description": "Find a specific message by sender, subject, or content. Results come back most-relevant + newest first, and every hit says where it matched (from / subject / body) and why. On this hosted sandbox it searches the built-in demo inbox; run the radmail-mcp package with RADMAIL_API_KEY set and the same tool searches your REAL ingested inbox read-only (with from / after / before filters) via the v1 search API.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "limit": {
            "description": "Max hits to return (default 10).",
            "type": "number"
          },
          "query": {
            "description": "Words to find, matched against from / subject / body. Every word must appear somewhere in a message.",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "type": "object"
      },
      "name": "search",
      "outputSchema": null
    },
    {
      "description": "Rank a mailbox on two axes (importance x urgency) and return what needs a human now versus what can wait or is already handled — with each thread's open commitment (the promise you owe or are owed, and whether it's overdue) surfaced inline, so the follow-through is visible on the very first call.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "triage_inbox",
      "outputSchema": null
    },
    {
      "description": "Explain in plain English why a given message was surfaced — the signals (sender, urgency, commitment) behind its rank.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "message_id": {
            "description": "An id from triage_inbox, e.g. m_001.",
            "type": "string"
          }
        },
        "required": [
          "message_id"
        ],
        "type": "object"
      },
      "name": "why_surfaced",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:50e763631763047a8a1c31b2caa60d5fca1d0ed8529bc55555b9b62fb659fd2d | sha256sum