Editorial Policy

Our Editorial Standards

Every piece of content on MCP Find — whether a tool listing, a blog article, or a learn guide — goes through a review process before publication. This page explains what that process looks like, what standards we hold ourselves to, and where we fall short.

MCP Find is not a promotional platform. We do not accept payment for listings, reviews, or editorial coverage. Our primary obligation is to our readers.

How We Select Tools

We maintain a directory of 292+ MCP servers, skills, and workflows. Not every tool that exists makes it into our directory, and not every tool currently listed will remain there forever.

We evaluate tools against the following criteria:

• Functional: The tool must actually work. We test installation commands on a clean environment before adding a listing.
• Accessible: The project must have enough documentation or code for a reasonably experienced developer to evaluate it without contacting the author directly.
• Relevant: The tool must serve a purpose related to the MCP ecosystem — connecting AI models to external tools, data, or workflows.
• Alive: We flag tools with no commits in over 12 months. We remove tools with no commits in over 24 months, unless there is a documented reason for dormancy.

We do not list tools that require payment or sign-up as a condition of basic evaluation. Tools with optional paid tiers are listed if the free tier provides meaningful functionality.

How We Write Articles

Our blog articles and learn guides are written by the MCP Find editorial team, which currently consists of one author. All articles reflect direct, hands-on experience with the subject matter.

When we publish an article, we have usually spent days or weeks actually using the tools, running the benchmarks, or deploying the architectures we describe. We do not publish articles based on reading documentation alone.

Every article includes:

• An explicit description of the author's direct experience with the topic
• Honest acknowledgment of what the tool or approach cannot do
• Specific test environments, version numbers, and dates so readers can verify our claims
• Real code examples, benchmark data, or configuration samples that we have actually run
• Updates when ecosystem changes invalidate previous claims

AI Use in Our Content

We use AI tools in our workflow, but not in the way that generates low-value content.

AI assists us with:

• Grammar and readability checks during drafting
• Generating code boilerplate that we then customize and test
• Summarizing documentation for our initial research phase

AI does not:

• Write our articles from outline to final draft
• Generate benchmark numbers or test results
• Produce tool descriptions without human verification
• Replace our direct experience with summaries of others' experiences

How We Handle Corrections

When a reader or tool maintainer points out a factual error in our content, we correct it promptly. We do not hide corrections behind revision logs — we update the content and note the correction inline if it changes the meaning.

If a tool we recommended changes significantly (or stops working), we update our recommendation accordingly. A tool that was good in 2024 may not be the best choice in 2026, and we try to reflect that honestly.

What We Do Not Cover

• Tools we have not personally installed and tested
• Tools with no public documentation or code
• Tools that exist only behind a paid wall without any free evaluation option
• Services that claim MCP compatibility but have no verifiable MCP implementation

Conflicts of Interest

MCP Find does not accept sponsored content, affiliate payments, or compensation of any kind in exchange for editorial coverage. If an article mentions a tool we helped build or a project with financial ties to us, we disclose that relationship explicitly.

We have not received payment from any tool developer, AI company, or MCP-related service in exchange for listing, reviewing, or recommending their product.

Contact

If you believe our content is inaccurate, outdated, or violates these standards, contact us at info@mcp-find.org.

For tool submission inquiries, use our submission form.