Send Decision

com.inboxpolicyPublished by inboxpolicy.comOfficial publisherv1.0.0Updated Oct 26, 2026

Send-decision email verification: agents get send/review/avoid with evidence, pay-per-call via x402.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote InboxPolicy server that gives an assistant a send/review/avoid decision, with evidence, before it sends an email.

What you can do
  • Get a send-decision verdict (send, review or avoid) for an email before it goes out
  • Receive supporting evidence behind each verdict
  • Authenticate with an InboxPolicy API key, or pay per call with x402 instead
When to use it
Useful when an assistant drafts or sends outbound email and you want a pre-send check on whether a message should go out, be reviewed, or be avoided.
Requirements
Remote streamable HTTP endpoint at mcp.inboxpolicy.com; no local package. An InboxPolicy API key (ip_live_...) sent in the x-api-key header, unless the agent pays per call with x402. Network access required.
Before you install
Requires a secret API key in the x-api-key header; the alternative x402 path spends money per call. Email content submitted for a decision is sent to a third-party service. The tool list is not published, so verify behavior before relying on it.

Installation

In SourceWeft

  1. Open Send Decision in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.inboxpolicy%2Fsend-decision/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "send-decision": {
      "type": "http",
      "url": "https://mcp.inboxpolicy.com/",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.