_ registry / mcp streamable-http · checked 22m ago

agent-email-list

https://ai.agentemaillist.com

Registry code: 40c9a0d49d2f7332

api record

Email sending and receiving for agents. Free, and you can open an account

yourself: call create_account first, which needs no credentials, then send

endpoint
https://ai.agentemaillist.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is agent-email-list live?
Yes — it answered the hub's last check (checked 22m ago). It answered 99% of checks over the last 30 days.
Is agent-email-list free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does agent-email-list have?
8 tools: get_delivery_events, add_domain, send_email, list_messages, verify_domain, list_domains, create_account, get_sending_limits.
Is agent-email-list safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.2%

90 days 98.9%· all time 98.9%

latency
98ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 736 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • create an email sending account
  • register and verify a sending domain
  • send an email
  • check delivery events
  • list received messages
takes → gives
text → data
tools
4 reads3 changes data1 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
8 auth-required 8 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_delivery_events reads auth-required 17h ago

    What happened to messages on this domain: accepted, delivered, failed, and so on. A send returning success means queued, not delivered; this is where the delivery outcome actually appears.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "event": {
          "type": "string",
          "description": "Filter to one type, such as delivered or failed."
        },
        "limit": {
          "type": "integer"
        },
        "domain": {
          "type": "string"
        },
        "recipient": {
          "type": "string"
        }
      }
    }
    arguments 21 lines
  • add_domain changes data auth-required never probed

    Register a domain to send from, and get the DNS records that must be published before it will work. Publishing DNS usually needs a human with registrar access, so start this early. The domain cannot send until verify_domain succeeds.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "A bare domain such as mail.yourcompany.com. A subdomain is better than the root."
        }
      }
    }
    arguments 12 lines
  • send_email sends messages auth-required never probed

    Send a message. The domain must be verified and the from address must belong to it. Counts one against the daily allowance per recipient. Set test_mode true to run the whole pipeline, including content screening, without sending anything and without spending allowance — do that first when building.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain",
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "One address, or several separated by commas."
        },
        "from": {
          "type": "string",
          "description": "An address at that domain."
        },
        "html": {
          "type": "string",
          "description": "Optional HTML body."
        },
        "text": {
          "type": "string",
          "description": "Plain text body."
        },
        "domain": {
          "type": "string",
          "description": "The verified domain to send from."
        },
        "subject": {
          "type": "string"
        },
        "test_mode": {
          "type": "boolean",
          "description": "Accept and screen the message but send nothing. Defaults to false."
        }
      }
    }
    arguments 37 lines
  • list_messages reads auth-required 17h ago

    Recent messages for a domain, sent and received. Use direction to filter, and folder to separate inbox from spam on received mail.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Up to 100. Defaults to 25."
        },
        "domain": {
          "type": "string"
        },
        "folder": {
          "enum": [
            "inbox",
            "spam"
          ],
          "type": "string"
        },
        "direction": {
          "enum": [
            "outbound",
            "inbound"
          ],
          "type": "string"
        }
      }
    }
    arguments 29 lines
  • verify_domain changes data auth-required never probed

    Re-read DNS now and mark the domain active if its SPF and DKIM records are visible. DNS takes minutes to hours to propagate; poll this every few minutes, not every few seconds.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • list_domains reads auth-required 17h ago

    List the sending domains on this account, with their verification state and how much of today's sending allowance each has left.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • create_account changes data auth-required never probed

    Create an account on this email service and get an API key back. Needs no existing credentials, so an agent with nothing can call this first. The key is returned once and never again. Free, with no card and no trial clock.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email",
        "password"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Optional display name."
        },
        "email": {
          "type": "string",
          "description": "A contact address for the account."
        },
        "password": {
          "type": "string",
          "description": "At least 12 characters. Needed only to sign in to the web console."
        }
      }
    }
    arguments 21 lines
  • get_sending_limits reads auth-required never probed

    How much this domain may send today and what graduates it to the next rung, plus this account's standing: how many domains it may hold and whether sending is paused. New domains start at a low daily cap and climb as they prove themselves, so check this before planning a bulk send rather than discovering it part-way. Call it with no domain for the account-level answer alone.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "domain": {
          "type": "string",
          "description": "Optional. Omit for account limits without a domain's allowance."
        }
      }
    }
    arguments 9 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 40c9a0d49d2f7332.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/40c9a0d49d2f7332/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/40c9a0d49d2f7332/badge.svg)](https://brick.blue/agent/40c9a0d49d2f7332?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.