tapacapi.com / hub / footprints
Distribution for an MCP server is not one landing page — it is a set of places an agent, a crawler or a developer can independently check. This is the list for TAPAC, with the link to each one. If a link here is dead, the footprint is gone; that is the point of keeping it in the open.
Installable with npx -y @tapacapi/mcp.
Python SDK for the REST API.
JavaScript SDK (dual ESM+CJS, types, retry).
stdio + hosted HTTP server, two tools, SKILL.md / AGENTS.md / plugin.json manifests.
Tagged release of the MCP server.
Row in "Sales and Outreach Agents".
Row in the MCP server list, search section.
Remote server entry (servers/tapac/server.yaml, streamable-HTTP, Bearer auth).
One-line entry in the largest awesome list for MCP servers.
Listing PR.
Listing PR.
Row in the remote-server table.
Bullet in docs/marketing-sales--crm.md.
Article #7 (dev.to id 4684475), canonical on /email-verification-api/.
dev.to article, canonical to https://tapacapi.com/email-verification-webhook/.
Article #8 (dev.to id 4684598), canonical on /smtp-email-verification/.
Article #9 (dev.to id 4684764), canonical on /b2b-lead-list/.
Article #10 (dev.to id 4684886), canonical on /catch-all-email-verification/.
Canonical: tapacapi.com/mcp.html
Canonical: tapacapi.com
Canonical: this hub's readiness checklist.
Canonical: tapacapi.com/blog/email-bounce-rate-cost.html
Canonical: tapacapi.com/lead-generation-mcp-server/
dev.to article, canonical to https://tapacapi.com/email-verification-cost/.
dev.to article, canonical to https://tapacapi.com/email-list-cleaning/.
dev.to article, canonical to https://tapacapi.com/outbound-lead-generation/.
dev.to article, canonical to https://tapacapi.com/compare/.
dev.to article, canonical to https://tapacapi.com/modern-contact-finding-stack.html.
dev.to article, canonical to https://tapacapi.com/bulk-email-verification/.
dev.to article, canonical to https://tapacapi.com/email-finder-vs-email-verifier/.
dev.to article, canonical to https://tapacapi.com/cold-email-domain-warmup/.
dev.to article, canonical to https://tapacapi.com/role-based-email-addresses/.
dev.to article, canonical to https://tapacapi.com/cost-per-replied-lead/.
dev.to article, canonical to https://tapacapi.com/verify-on-entry-vs-at-send/.
dev.to article, canonical to https://tapacapi.com/email-verification-benchmarks/.
dev.to article, canonical to https://tapacapi.com/email-verification-accuracy/.
dev.to article, canonical to https://tapacapi.com/lead-pipeline-attrition/.
dev.to article, canonical to https://tapacapi.com/delivered-is-not-a-delivery/.
dev.to article, canonical to https://tapacapi.com/hard-vs-soft-bounces/.
dev.to article, canonical to https://tapacapi.com/disposable-email-domains/.
dev.to article, canonical to https://tapacapi.com/bounce-rate-vs-complaint-rate/.
dev.to article, canonical to https://tapacapi.com/verified-contact-timestamp/.
dev.to article, canonical to https://tapacapi.com/smtp-timeout-is-not-a-no/.
Footer link from the gym analytics product to the contact tool.
Footer link from the release-notes product to the contact tool.
Footer link from the marketing content tool to the contact tool.
Public post (no login required) carrying TAPAC's sourcing and verification model.
Cursor config block, hosted endpoint, the two tools.
The four server replies (250 / 550 / 450-451 / catch-all) and why a verdict is a timestamp.
Find + verify in one call, three-call outbound pipeline.
Endpoint table, response shape, OpenAPI 3.1, JS SDK.
Three kinds of rows in a list (live / dead / catch-all-unknown) and the decay numbers.
Plain scraping vs search + SMTP verification; sources website / telegram / discord.
Hard, soft, blocked and catch-all bounces, with the decay figures and sources.
Accept-all domains return unknown, not verified — and what to do with unknowns.
Install for Claude / Cursor / Codex / Windsurf, tools, behaviour without a key.
Ten parameters, published list prices only.
Apollo / ZoomInfo / Hunter alternatives, Discord lead mining, Telegram B2B contacts, email verification.
Installation walkthrough and bounce arithmetic, both with sources.
Verification inside the search call, endpoint table, SDK snippet.
Sourced-per-request vs stored database, decay figures with sources.
Published Lusha list prices against pay-per-use.
Install for Claude, hosted endpoint, two tools.
Two questions behind one request — does the person work there, does the mailbox exist — and how each find method answers them.
What a cleaning pass fixes, what it cannot (catch-all stays unknown), and why a cleaned file keeps decaying.
Price per check versus price per usable contact: the three billing models and the four cost lines that never reach the invoice.
What enrichment adds to a row and what it cannot prove; the three fields every enriched row should carry.
A profile proves the person exists, not that the mailbox does: pattern guessing versus a probe, and why catch-all domains come back unknown.
Valid, invalid, unknown at list scale: the catch-all share no re-check lowers, the decay clock, and the arithmetic on 10,000 rows.
A finder proposes a string, a verifier asks the mail server: two failure modes, the leak in the handoff, and why catch-all comes back unknown.
Published versus inferred addresses, where business addresses actually sit, and the three states a collection pass produces.
A check is a snapshot, not a subscription: what a verification webhook would have to watch, the decay numbers, and a re-check cadence that costs almost nothing.
Enrichment as a lookup at request time versus a bulk backfill that becomes a second, older database - and the three fields worth writing back.
Keep the state, the timestamp and the source - not a second copy of the mailbox. What to store, how long, and why the un-made copy is the erasure request you never have to audit.
Verification is accuracy, warmup is reputation: two failure modes that look identical, a four-week order of operations, and why a verified list still gets throttled.
info@ is not a person: deliverability is fine, ownership is not. When a role mailbox is the right target, when only a named person counts, and why usable contacts are never counted as valid ones.
Agencies buy lists by client while per-seat tools charge by head: published entry prices of Apollo, Hunter, Lusha and ZoomInfo read as a yearly bar, against pay-per-contact.
Cost per contact hides the contacts that never reply: the arithmetic of cost per replied lead, the same money read as a seat, and the three leaks that inflate it.
What an email audit trail has to record to be worth keeping - which mailbox, checked when, found where - and why a catch-all must never be promoted into the usable count.
Two verification policies, neither a superset of the other: what a check on entry proves, what a send-time check proves, and why the log is the only thing that reconciles them.
An email verification SLA is three promises - a check at call time, honest labelling of catch-alls, a reproducible record - and not a guaranteed bounce rate.
The published numbers behind email verification - 2-5% versus 10-35%, 23% job churn, 40% dead in two years - what each one measures, and how to read your own log against them.
An SMTP check asks a mailbox whether an address exists. What the handshake proves, what it can never prove, and why catch-all domains have to be returned as unknown.
A single accuracy percentage has no denominator. The states a mailbox check can return, the one state that is not a verdict, and the four numbers worth measuring instead.
A stored list decays on two clocks - 23% job churn a year and 40% dead mailboxes in two years. The arithmetic behind a re-check cadence and what a pass costs.
Three failures hide behind one aggregate sent count - hard bounce, soft failure, silent drop. The evidence that still exists and the triage ladder.
Seven stages from discovery to reply, the failure mode of each, and which of them actually have a published rate.
Deliverable, undeliverable, catch-all - and the fourth state nobody names: no answer at all. What causes a timeout and what to do with the contacts it touches.
The word describes a handoff between two servers, not a person reading. Four layers sit between a delivered count and an inbox, and only one is visible in a report.
A hard bounce retires an address; a soft bounce only says the mailbox was not reachable right now. What each SMTP code licenses and how to keep a full mailbox from deleting a live contact.
A live MX record proves a domain can receive mail, not that a person exists behind an address - five setups where the domain checks out and the mailbox does not.
A throwaway mailbox passes every existence check: why SMTP verification answers a different question than list quality, and how to handle disposable domains with a policy instead of a guess.
The same person arrives from several sources and every count you quote is wrong by the amount you did not notice - why dedupe by address misses the expensive case.
A 4xx answer during a mailbox check is a request to come back later, not a verdict on the contact: why greylisting exists, and what an honest verifier does with a temporary answer.
A hard bounce is a failure of your list data; a complaint is a person telling the mailbox provider your message was unwanted - Gmail asks bulk senders to keep that rate below 0.10%, never reaching 0.30%.
A verdict is about a moment, not a property: why a probe date on the row decides what you can do with a list, and what decays underneath it.
Valid MX records say the domain can receive mail, not that the address exists: four levels of evidence, and where a domain-level pass gives false comfort.
A server that goes silent has not refused: timeouts, greylisting and rate limits look alike, and folding silence into "undeliverable" silently deletes good contacts.
False positives bounce, false negatives vanish: how to size the error you can see against the one no report ever shows you.
What it is, install, three scenarios, sourced fact table.
MCP server readiness checklist and lead cost & bounce-risk calculator — both run in the browser, no signup.
Paid MCP directories, submission forms behind a captcha, and catalogs that require a third-party OAuth account. Those cost money or a login we do not control, and none of them guarantee a durable public URL. The list above is what is reachable without paying or registering anywhere new.
npx -y @tapacapi/mcp # hosted, no install: https://tapacapi.com/mcp