Changelog
Every free tool reachable by AI, and listed where agents look
Every one of the 55 free tools can now be reached from an AI assistant: 54 run on the free MCP server, and the Spamhaus checker, which needs a paid key, says so and links Spamhaus’s own lookup. The server reads our research in full rather than only finding it, ends a sized fleet on how to get it, and is listed in the official MCP Registry and on Glama, with the Claude directory submission in review. The comparison pages now carry each provider’s own published figures, dated.
Tools
- Twelve tools that ran only in the browser now run over the MCP server and the free API with their page’s own code: the Spam Checker, Pre-Send Checker, Bounce Analyzer, SCL Analyzer, Inbox Previewer, Record Generator, Inbox Rotation Planner, Waterfall Calculator, CSV List Cleaner, Sequencer CSV Converter, CSV Combiner and Suppression Checker. The CSV tools return the file up to 500 rows and hand anything larger back to the page, which runs the same code in the browser. /for-ai
- The tools page has a search box above the tools, which also takes ?q= in the address, and its first cards sit under a Go To Market Tools heading. the tools page
For AI agents
- The free MCP server has 50 tools and runs 54 of the 55 free tools. Three tools hand off rather than run, and say so before they are called: the Spamhaus DBL (a paid key, not queried here), the Burned Inbox Checker (its own site) and Cold Email AI (a custom GPT). /for-ai
- The server reads what we publish, not only its titles. find_resources searches the full text of 159 pages, the guides, playbooks, studies and their data, recipes, comparisons, changelog and the offer and about pages, and quotes the passage that answers the question; the new read_resource returns any of them whole, with a study’s dataset as JSON. A page added to the site is readable over MCP the day it ships. /research
- plan_infrastructure, plan_from_list and get_pricing now end on how to get the fleet: exactly what to order, the app for a first order, and for existing customers the purchasing server to connect so later orders, the build and the export into a sequencer happen in the same conversation. /developers
- Listed in the official MCP Registry as com.warminboxes/deliverability-tools, with ownership proved from warminboxes.com, and on Glama as a verified, healthy connector. Submitted to the Claude Connectors Directory, in review. /for-ai
- Each ChatGPT user now has their own daily allowance, keyed on the anonymous id ChatGPT sends for that purpose and honoured only from OpenAI’s published addresses. Calls from Claude’s and ChatGPT’s shared servers that carry no per-user id draw on a 1,000-domain daily pool per platform rather than the ten an IP gets. /privacy
- The free API and the purchasing API are stated once, on /developers, /for-ai and llms.txt: the free one is public with no key; the purchasing one comes with a free account, and a first purchase is a checkout in the app. /developers
Pages
- The comparison pages now fill each competitor’s cells from that provider’s own published pages, checked on 22 October, with a section on where each may be the better choice. Primeforge, Mailforge and Infraforge, one company, share one page, and the three old addresses redirect to it. the Primeforge, Mailforge and Infraforge comparison
- A recommended tools page: the cold email tools our agency runs on, starting with Instantly and PlusVibe, with what each is for and how we use it. /recommended-tools
- A guide to connecting inboxes to a sequencer by OAuth or by app password: what each one costs you, why Google and Microsoft are moving everyone to OAuth, and what a password change does to each. The guide count is 102. the OAuth vs app password guide
Corrections
- The Apollo, Instantly, PlusVibe and Smartlead inbox pages said an OAuth connection survives a password change. It does not: changing a Google Workspace password revokes the tokens with Gmail scopes, so the sequencer has to reconnect. The pages now say so and link the new guide. /instantly-inboxes
- The privacy policy said the CSV tools never leave your browser. On the website that is true; through the free API or an AI assistant the file reaches our server, where it is processed in memory and not stored. The policy now says so, and names the daily usage counter and that it is deleted within two days. /privacy
- The purchasing API was described as one that buys inboxes. It orders more on plans an account already has; a first purchase is a checkout in the app. llms.txt and the developer pages now say so, and plan_from_list no longer tells an assistant to place a first order it cannot place. /developers
Technical
- The build now fails on a stated guide count that disagrees with the blog, and on promising inboxes running, live or delivered tomorrow, since every order takes 48 to 72 hours.
- Every MCP tool says accurately whether it reaches the outside world: the 25 that query DNS, blocklists, registration data or a certificate say yes, and the 24 that only read what they are given, the site’s own catalogue, or return a link say no.