Useful before exhaustive
Botfinder is not trying to mirror every repository that mentions MCP. We begin with tools that map to recognizable work in sales, marketing, research, commerce, support, and operations.
About the index
Useful tools, plainly explained.
Botfinder is an independent field guide to the connection layer around AI agents. The job is not to make every tool sound transformative. It is to help a team decide what belongs in a real workflow.
01 / Selection policy
What earns a place in the directory.
The initial catalog is deliberately curated. Breadth can follow once the filing system remains useful at larger scale.
Provenance over popularity
First-party documentation, official registries, maintained source repositories, and explicit publisher identity count for more than stars, launch votes, or the number of advertised tools.
Scope before promises
A connector can be useful and still be narrow. Listings separate read access from write access, local from remote operation, and protocol compatibility from complete workflow readiness.
Failure belongs in the profile
Authentication limits, destructive capabilities, self-hosting burden, preview status, missing audit controls, and uncertain maintenance are buyer information rather than footnotes.
Current sources are dated
The ecosystem changes quickly. Every initial listing carries a verification date and links to a public source so readers can confirm availability and instructions before installing.
A listing is not certification
Inclusion does not mean Botfinder has audited source code, penetration-tested a remote service, or approved a tool for regulated data. Those claims require separate evidence.
02 / Editorial disclosure
What “verified” means here
A verified listing means its primary public source was checked on the stated date and the core description is consistent with that source. It does not mean Botfinder operated the tool against a live customer account. Hands-on tests, source-code reviews, security audits, and sponsored relationships will be labelled separately if they are introduced.
Marketplace facts drift. Providers rename products, retire local packages, add remote endpoints, change authentication, and expand write access. The linked publisher documentation remains authoritative. Re-check it before connecting customer, employee, financial, or proprietary data.
How profiles are written
Profiles start with the job a team is trying to perform. We record the publisher, deployment pattern, authentication surface, client compatibility, useful capabilities, setup burden, and cautions. Category placement is editorial, not a claim by the publisher.
Descriptions are original summaries. We avoid copying vendor language, fake scores, invented benchmarks, and rankings built from opaque weights. A long capability list is not treated as evidence of quality.