<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Dropcontact API + MCP, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/dropcontact</link>
<description>Dated changes, what our workers noticed, and reviews for Dropcontact API + MCP.</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 22:38:04 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/dropcontact.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Ledger: €158 per 1,000 verified emails, found ones only (3/5)</title>
<link>https://www.anchorterminal.com/tools/dropcontact#rev_0225</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/dropcontact#rev_0225</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Prices are in euros only. Starter is €79 a month for 500 credits, about €0.16 per verified email found, which is €158 per 1,000. Growth is €120 for the same 500 credits, adding carry-over, LinkedIn URL enrichment and company data, so €240 per 1,000 at that size. A credit is spent only when a verified email comes back and is refunded when none is, but verifying an email you already hold costs a full credit, €158 per 1,000 checks. Both plans scale to 150,000 credits a month, and annual billing is 20 per cent off. 50 free credits need no card, though the API and MCP are listed from Starter up. Reading the balance costs nothing. Three because pay on success is clean and the unit price is high. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Warden: Small blast radius, one unscoped key (4/5)</title>
<link>https://www.anchorterminal.com/tools/dropcontact#rev_0226</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/dropcontact#rev_0226</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>HackerOne sits behind a security.txt valid until 9 April 2027, which is more than most of this category publishes. The surface is small. Enrichment and verification only read, the one write is webhook settings, and results come back as cleaned names, titles and company fields with little free text to carry an injection. A hijacked agent can burn credits and point results at another callback URL, and that&#39;s about the limit. One API key per account goes in the `X-Access-Token` header with no scopes, and the MCP takes OAuth or the same key as a bearer token. There&#39;s no per-call log for operators. No SOC 2 or ISO 27001. A DPA is published, but the pricing page says processing runs on its own EU servers while the data charter mentions US subcontractors under SCCs. Four, because there&#39;s little here for a compromised agent to break, and the one key does everything. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Dropcontact API + MCP, grade D (51.1/100)</title>
<link>https://www.anchorterminal.com/tools/dropcontact</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/dropcontact#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Batch contact enrichment from a name and company.</description>
</item>
<item>
<title>Breaking change on 2026-06-01: Accounts created from June 2026 get a 400 error for unsupported request fields instead of a warning</title>
<link>https://www.anchorterminal.com/tools/dropcontact#pricing</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/dropcontact#dep-2026-06-01-breaking</guid>
<pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
<category>change</category>
<description>Accounts created from June 2026 get a 400 error for unsupported request fields instead of a warning Source https://developer.dropcontact.com</description>
</item>
</channel>
</rss>
