Clawpost is an open-source Cloudflare Worker you deploy yourself to give an AI agent its own email address, with an MCP server, a REST API and a CLI for sending, receiving, searching, drafts and sender approval.
Best for A developer who wants an agent inbox on their own domain and Cloudflare account with a default approval gate.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Inboxes. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
Assessment. A small self-hosted agent inbox whose sender-approval gate keeps unknown senders' mail away from the agent by default, with drafts for human review. It is one developer's project, unchanged since 1 April 2026, with one all-powerful key, no releases, tests or CI.
Facts
Access how an agent reaches and pays for it
- Transport
- Streamable HTTP, HTTP
- Auth
- API key
- Pricing
- Free · Free · OSS
- x402
- No
- Licence
- MIT
- Tools exposed
- 21
- Capabilities
- email.inbox email.send email.inbound email.threads email.domains
Where it lives packages, source, docs and releases
- llms.txt
- not found
- Last release
From our research 5 facts checked against the vendor's pages
- Surface listed
- The Worker's MCP endpoint at /mcp, its REST API under /api and the CLI, read from a clone of github.com/hirefrank/clawpost (README, SKILL.md, src/mcp.ts, src/index.ts and the commit history) on 6 November 2026. Nothing was deployed or run
- MCP tools
- 21 tools: send, reply, list, read, attachments, search, threads, labels, drafts, archive, and sender approval (list_pending, approve_sender, remove_sender, list_approved_senders)
- Previous name
- clawmail, renamed to clawpost on 12 February 2026 per the commit history
- Built for
- openclaw.ai agents, per the README
- Known gaps
- The README's roadmap lists per-key rate limiting, bounce handling and Resend webhook signature checks as not yet built
Facts verified 6 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
- Mail from unapproved senders is stored but hidden from every query tool until a sender is approved
- Drafts let a person review mail before an agent's message goes out
- Self-hosted on the deployer's own Cloudflare account, so mail stays in their D1 and R2
- 21 MCP tools with typed zod inputs, plus a REST API and a CLI with
--jsonoutput - Free software; running costs are the Cloudflare Workers Paid plan at $5 a month
Weaknesses
- One shared API key grants every REST and MCP operation; no scopes or read-only key
- No commits since 1 April 2026, no tags or releases, no CI and no tests
- No idempotency on sends and no MCP tool annotations
- Tool descriptions are one line, such as
Send an email, with no when-not-to-use guidance - README says MIT but no LICENSE file is in the repository
Before you call it notes for agents
- Expect unknown senders' mail to be invisible until
approve_senderruns; checklist_pendingfor metadata first - Use
create_draftinstead ofsend_emailwhen a person should review the message - Send to one address per call or comma-separate recipients in
to; a retried send isn't deduplicated - Treat the deployer's Worker URL and
CLAWPOST_API_KEYas full access to the mailbox
Who's behind it provenance 13/100
- Legal entity namednot found0/20
- Domain agegithub.com, no registry record we could read0/15
- Endpoint on the vendor's domain is not on github.com0/15
- Terms of servicenot found0/10
- Privacy policynot found0/10
- Status pagenot found0/10
- Changelognot found0/10
- security.txtnot found0/10
- People named1 named with their role, 1 with a public profile10/10
- Support routehelp pages5/5
Terms and privacy, as read
Terms of service none to read
TL;DR We found no terms of service published for this product, so there is nothing to read and the check scores 0.
Privacy policy none to read
TL;DR We found no privacy policy published for this product, so there is nothing to read and the check scores 0.
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
A personal repository under the GitHub account hirefrank; every commit but one merged pull request is by Frank Harris. No company, terms or privacy policy, as expected for self-hosted software.
The README's licence section says MIT and SKILL.md declares MIT, but no LICENSE file is committed.
The endpoint is whatever Worker URL the deployer chooses, usually on workers.dev.
GitHub's API refused our requests for its rate limit on 6 November 2026, so stars and open issues weren't read; the code and history come from a shallow clone.
Checked 2026-11-06 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
- Frank HarrisAuthor and maintainer
The company on GitHub
Researched 6 November 2026 from public pages. Clawpost is a personal repository under the GitHub account hirefrank; every commit in the history is by Frank Harris, apart from one merged pull request authored with Claude, and SKILL.md names hirefrank as author. There is no company, website, funding or investors. His GitHub profile names him Frank Harris and links the X account hirefrank, which is listed. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Live watched around the clock · updated 2026-11-07 16:01 UTC
- GitHub stars 6
- security.txt valid, expires 2026-12-07T16:01:24z · 1 hour ago
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/clawpost.json
Notable
- Inbound mail is unapproved by default and hidden from every query tool until
approve_senderallowlists the sender;list_pendingshows metadata only, as a prompt-injection guard source - Drafts let an agent prepare mail for a person to review and send source
- Runs on the deployer's own Cloudflare account with D1, R2, Durable Objects, Email Routing and Email Service or Resend source
- 25 commits between 7 February and 1 April 2026, no tags or releases, no CI and no tests in the repository source
- The README says MIT, but the repository has no LICENSE file source
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using Clawpost, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used Clawpost, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 6 November 2026 from public evidence, against the published checklist. Confidence low. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 6 November 2026 | 16%20 | 1.6 | |
| Graded with the lines for self-hosted software, since each deployer runs their own Worker. No published package; it deploys from the repository with a Deploy to Cloudflare button, Bun and Wrangler, and states the Cloudflare products it needs (8 of 20). No CI workflow or test suite in the repository (0). Open issues couldn't be read, because GitHub's API refused our requests for its rate limit, so the line scores absent (0, unchecked). No tags, releases or changelog; package.json says 0.1.0 (0). Pre-1.0 (0). Total 8. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 6 November 2026 | 13%16.2 | 8.8 | |
All 21 MCP tools take typed zod inputs, which the MCP SDK publishes as JSON Schema (25). SKILL.md and AGENTS.md give agent-readable setup in Markdown; no llms.txt (5 of 10). Descriptions are one line each, such as Send an email, with parameter descriptions but no when-not-to-use (8 of 20). Inputs are typed with defaults for limit and offset, but recipients are a comma-separated string and direction isn't an enum in the schema read (9 of 15). The README has request examples and a REST route table; error responses aren't documented (7 of 15). No versioning or changelog (0). Total 54. | |||
| Agent ergonomicschecked 6 November 2026 | 13%16.2 | 8.6 | |
21 tools, the 11 to 30 band (15 of 25). List and search tools take limit, offset and filters by direction, sender, label and archive state (20). Error shapes aren't documented; the code returns JSON errors (8 of 20). No idempotency key for sends and no readOnlyHint or destructiveHint annotations; drafts give a review step (3 of 20). Archived mail is excluded by default and the CLI has a --json mode, but there's no SDK beyond the CLI (7 of 15). Total 53. | |||
| Security & authchecked 6 November 2026 | 14%17.5 | 7.3 | |
One shared secret for REST and MCP, compared in constant time, with no scopes, expiry or per-client keys (10 of 30). Sender approval, drafts, and an optional allowlist of domains for routing changes limit what an agent can see and change; the key can still send to anyone (14 of 20). Mail from unapproved senders is hidden from all query tools by default, and list_pending returns metadata without bodies, documented as a prompt-injection guard (15). No log of API or tool calls beyond the stored messages (3 of 15). No security policy, advisories or disclosure route for this personal project (0). Total 42. | |||
| Payments & pricingchecked 6 November 2026 | 10%12.5 | 7.5 | |
| Free self-hosted software with nothing to buy from the author, which the rubric scores 20 + 20 + 20. Running it needs the deployer's own Cloudflare Workers Paid plan at $5 a month, which isn't Clawpost's charge. No payment protocol (0 of 40). Total 60. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 6 November 2026 | 7%8.8 | 0.2 | |
The last commit was on 1 April 2026, 219 days before this check (0). No releases or commits in the 90 days from 8 August (0). Issue and pull request activity couldn't be read through GitHub's API that day (0, unchecked). Not in the official MCP registry and no published package (0). Dependencies such as agents ^0.0.74 and the MCP SDK ^1.12.1 date from early 2026, and there's no CI (2 of 10). Total 2. | |||
| Transparency & trusteditorial 50, provenance 13checked 6 November 2026 | 7%8.8 | 2.8 | |
| The README and SKILL.md say MIT, but no LICENSE file is committed (20 of 30). Self-hosted; the README says mail is stored in the deployer's D1 database with attachments in R2 and sent through Cloudflare Email Service or Resend. No retention or deletion guidance (15 of 30). No deprecation policy (0). No telemetry in the source read; the only outbound calls are to the configured mail provider, Cloudflare's API and the deployer's own webhooks (15 of 20). Total 50. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 36.8 · F | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 36.8 F methodology v0.7
Fix list 17 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Clawpost. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- unchecked: GitHub stars, open issues and pull requests, because GitHub's API refused our requests for its rate limit on 6 November 2026
- The licence is stated as MIT in the README and SKILL.md but no LICENSE file is committed
Sources 5
- repository and README github.com · seen 2026-11-06
- MCP tool definitions github.com · seen 2026-11-06
- authentication code github.com · seen 2026-11-06
- agent skill github.com · seen 2026-11-06
- commit history github.com · seen 2026-11-06
Probe metrics
Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Free Free · OSS Free, MIT-licensed software. Running it needs the Cloudflare Workers Paid plan ($5 a month) for Durable Objects and outbound Email Service; the README puts a typical agent at about $5 a month. Resend can be used for outbound instead.
Recent changes
- security.txt on github.com is valid, the listing says none source
- Latest release
Follow them as a feed at /feeds/tools/clawpost.xml, or this listing's score history at history.json.
Connect
Install
git clone https://github.com/hirefrank/clawpost && cd clawpost && bun install && bun run db:migrate && bun run deployMCP client configuration
{
"mcpServers": {
"clawpost": {
"headers": {
"Authorization": "Bearer YOUR_CLAWPOST_API_KEY"
},
"type": "streamable-http",
"url": "https://\u003cyour-worker\u003e.workers.dev/mcp"
}
}
}Through letme picks today, calling later
GET https://letme.dev/clawpostletme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.
Alternatives to Clawpost
#12 of 12 in Best email inbox APIs for AI agents · All 66 inboxes comparisons
AgentMail API + MCP BBMailSlurp BRobotomail Bmails.ai Agent Email BLumbox CInbound C
Head to head AgentMail API + MCP vs Clawpost · Cherami vs Clawpost · Clawpost vs Hostinger Agentic Mail · Clawpost vs Inbound · Clawpost vs InboxAPI · Clawpost vs Lumbox · Clawpost vs Mailows · Clawpost vs mails.ai Agent Email · Clawpost vs MailSlurp · Clawpost vs Postfleet · Clawpost vs Robotomail
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| AgentMail API + MCP AgentMail | BB | 72.8 | email.inbox email.send email.inbound email.threads email.domains | yes |
| Mailtrap Email API + MCP Mailtrap (Railsware) | B | 66.8 | email.send email.inbound email.domains email.inbox email.threads | no |
| MailSlurp Pettman OÜ | B | 66.7 | email.inbox email.inbound email.send email.threads email.domains | no |
| Robotomail Tiny Bot Labs Limited | B | 66 | email.inbox email.send email.inbound email.threads email.domains | no |
| mails.ai Agent Email Mails.ai | B | 65.2 | email.inbox email.send email.inbound email.threads email.domains | no |
| Lumbox Cyphen Innovations Private Limited | C | 60.7 | email.inbox email.send email.inbound email.threads email.domains | no |
Machine-readable
- JSON
/api/v1/tools/clawpost.json· historyhistory.json· badge/badges/clawpost.svg· changes feed/feeds/tools/clawpost.xml - Markdown
/tools/clawpost.md· slim/tools/clawpost.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/clawpost.md·/fixes/clawpost.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool clawpost --md(the CLI) · over MCPget_tool {"slug": "clawpost"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT clawpost.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/clawpost"><img src="https://www.anchorterminal.com/badges/clawpost.svg" alt="Clawpost on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/clawpost)<a href="https://www.anchorterminal.com/tools/clawpost">Clawpost on Anchor Terminal</a>It counts on the front page of github.com/hirefrank or of one of its repositories, or the README at the root of github.com/hirefrank/clawpost.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "clawpost", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say Clawpost is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/clawpost. The logo is the one on this listing. If it's wrong or out of date, send us the right one.