Content Policy & Standards

Content Creation Process

Our content creation process is designed to ensure every piece of content meets the highest standards of quality, originality, and usefulness. We follow a rigorous multi-stage workflow that combines research, hands-on testing, original writing, and thorough review.

1. Research & Discovery

Every piece of content begins with comprehensive research to understand the topic deeply:

• Primary Sources - We start with official documentation, GitHub repositories, and source code to understand the technology firsthand
• Community Insights - We review community discussions, GitHub issues, and user feedback to identify common questions and pain points
• Competitive Analysis - We study similar servers, tools, or approaches to understand the landscape and identify unique value propositions
• Technical Deep Dive - We examine implementation details, architecture patterns, and technical specifications to ensure accuracy
• Use Case Exploration - We identify real-world applications and practical scenarios where the technology provides value

2. Hands-On Testing

We don't write about anything we haven't personally tested and used:

• Installation & Setup - We follow the complete installation process to verify accuracy and identify potential issues
• Feature Exploration - We test all major features and capabilities in realistic scenarios
• Performance Testing - We measure response times, resource usage, and scalability characteristics
• Integration Testing - We test integration with MCP clients and other tools in the ecosystem
• Edge Case Testing - We explore boundary conditions, error scenarios, and unusual use cases
• Documentation Validation - We verify that official documentation is accurate and complete

3. Original Content Creation

All content is written from scratch by our team of experienced developers and technical writers:

• Original Analysis - We provide unique insights, perspectives, and analysis based on our testing and expertise
• Practical Examples - We create original code examples, configuration snippets, and use case demonstrations
• Expert Commentary - We add editorial opinions, recommendations, and best practices from our experience
• Comprehensive Coverage - We ensure content is thorough, addressing common questions and providing complete information
• Clear Explanations - We explain complex concepts in accessible language without sacrificing technical accuracy
• Structured Format - We organize content logically with clear headings, sections, and navigation

4. Technical Review

Every piece of content undergoes technical review by a senior team member:

• Verification of all technical claims and specifications
• Testing of all code examples and commands
• Validation of installation instructions and configuration examples
• Review of performance claims and benchmarks
• Assessment of security considerations and best practices
• Checking for technical accuracy and completeness

5. Editorial Review

Our editorial team reviews content for quality, clarity, and consistency:

• Grammar, spelling, and punctuation
• Clarity and readability for target audience
• Consistency with our style guide and tone
• Logical flow and structure
• Completeness and thoroughness
• Proper attribution and citations

6. Quality Assurance

Before publication, we perform final quality checks:

• Link validation and external reference checking
• Code snippet testing in clean environments
• Formatting and layout verification
• Metadata optimization (titles, descriptions, tags)
• Minimum word count verification (2,500+ words for major content)
• Final proofread for any remaining errors

Sourcing Methodology

We maintain strict standards for how we source information and create content to ensure originality and trustworthiness.

Primary Sources

We prioritize primary sources for the most accurate and authoritative information:

• Official Documentation - We reference official docs, READMEs, and specifications from project maintainers
• Source Code - We examine actual implementation code to understand behavior and capabilities
• GitHub Repositories - We review commit history, issues, and discussions for context and updates
• Official Announcements - We follow project blogs, release notes, and official communications
• Direct Testing - We rely heavily on our own hands-on testing and experimentation

Secondary Sources

We use secondary sources for context and community perspectives:

• Community Discussions - We review forums, Discord channels, and community feedback
• Technical Blogs - We read technical articles and blog posts for additional perspectives
• Stack Overflow - We examine common questions and solutions from the developer community
• Social Media - We monitor Twitter, Reddit, and other platforms for trends and issues

What We Don't Do

We maintain strict policies against content practices that compromise quality or originality:

• No Copy-Pasting - We never copy content directly from GitHub READMEs, documentation, or other sources
• No Content Spinning - We don't use automated tools to rewrite or "spin" existing content
• No Plagiarism - We create original content and properly attribute any referenced material
• No AI-Generated Content - We don't use AI tools to generate content without human expertise and review
• No Thin Content - We don't publish superficial or low-value content just to increase page count
• No Misleading Claims - We don't make exaggerated or unverified claims about servers or features

Original vs. Sourced Content

We maintain a high ratio of original to sourced content:

• Target: 90%+ Original - We aim for at least 90% original content in every article
• Substantial Transformation - When we reference external sources, we add significant original analysis and context
• Unique Insights - We provide perspectives, recommendations, and insights not available elsewhere
• Practical Examples - We create our own code examples, configurations, and demonstrations
• Testing Results - We include original testing data, benchmarks, and observations

Attribution Standards

We believe in giving credit where credit is due. Our attribution standards ensure transparency and respect for original creators while maintaining the integrity of our content.

When We Attribute

We provide clear attribution in the following situations:

• Direct Quotes - Any text quoted directly from external sources is clearly marked and attributed
• Code Examples - Code snippets adapted from official documentation or other sources are attributed
• Technical Specifications - Specific technical details from official documentation are referenced
• Community Contributions - Ideas, solutions, or insights from community members are credited
• External Research - Studies, benchmarks, or analysis from external sources are properly cited
• Images & Screenshots - Visual content from external sources is attributed (though we primarily use our own)

Attribution Format

We use consistent attribution formats throughout our content:

• Inline Citations - We link directly to sources within the text where information is referenced
• Sources Section - Major articles include a "Sources" section at the bottom listing all references
• Link Format - We provide descriptive link text and full URLs to original sources
• Access Dates - We include the date we accessed external sources for reference
• Author Credit - We credit original authors and maintainers when referencing their work

Fair Use & Transformation

We follow fair use principles and ensure substantial transformation of referenced material:

• Limited Quotation - We quote only what's necessary to support our analysis
• Substantial Commentary - We add significant original analysis, context, and insights
• Educational Purpose - Our content serves educational and informational purposes
• Transformative Use - We transform source material through testing, analysis, and expert commentary
• No Market Substitution - Our content complements rather than replaces original sources

Example Attribution

Editorial Independence

We maintain complete editorial independence to ensure our content is unbiased, trustworthy, and serves the best interests of our readers.

No Paid Placements

• No Pay-for-Play - Server maintainers cannot pay for inclusion, better reviews, or higher rankings
• No Sponsored Content - We don't publish sponsored articles or paid promotional content disguised as editorial
• No Affiliate Influence - We don't have affiliate relationships that could bias our recommendations
• Merit-Based Inclusion - Servers are included based solely on quality, functionality, and value to users

Objective Evaluation

• Standardized Criteria - We evaluate all servers using the same objective criteria
• Testing-Based - Our assessments are based on actual testing results, not marketing claims
• Honest Reviews - We provide balanced reviews that include both strengths and weaknesses
• No Favoritism - We don't favor servers based on popularity, maintainer relationships, or other non-merit factors

Conflict of Interest Policy

• Disclosure - We disclose any relationships with server maintainers or projects we cover
• Recusal - Team members recuse themselves from reviewing projects they're personally involved with
• Transparency - We're transparent about our funding, partnerships, and business relationships
• Reader First - Our primary obligation is to our readers, not to server maintainers or sponsors

Current Disclosures

Content Quality Standards

We maintain strict quality standards to ensure every piece of content provides genuine value to our readers.

Minimum Requirements

• Word Count - Major server pages: 2,500+ words; Blog articles: 1,500+ words; Guides: 1,000+ words
• Originality - Less than 10% similarity to external sources (verified through plagiarism checking)
• Accuracy - All technical claims verified through testing and research
• Completeness - Comprehensive coverage of the topic without significant gaps
• Clarity - Clear, well-organized writing accessible to the target audience
• Usefulness - Practical value for developers implementing MCP solutions

Content Types & Standards

Corrections & Updates

We're committed to accuracy, but mistakes can happen. When they do, we handle them transparently and promptly.

How to Report Issues

If you find an error, outdated information, or have suggestions for improvement:

• Email us at editorial@mcpfinder.com
• Use our contact form
• Report issues on our GitHub repository
• Reach out via our community Discord channel

Our Correction Process

1. Acknowledgment - We acknowledge receipt of error reports within 24 hours
2. Verification - We verify the issue through testing and research within 24-48 hours
3. Correction - If confirmed, we update the content immediately (within 2 hours for critical errors)
4. Notation - We add a correction note indicating what was changed and when
5. Notification - For significant errors, we notify affected users via email or site notifications
6. Process Review - We review our processes to prevent similar errors in the future

Types of Updates

• Minor Corrections - Typos, formatting issues (updated silently)
• Technical Corrections - Incorrect commands, code snippets (noted with correction date)
• Factual Corrections - Incorrect information about features or specifications (prominently noted)
• Major Corrections - Significant errors affecting recommendations or safety (correction notice at top)
• Content Updates - Updates for new versions, features, or changes (noted with update date)

Community Contributions

While we create all content in-house, we value community input and contributions to improve our content quality.

How You Can Help

• Report Errors - Let us know if you find inaccuracies or outdated information
• Suggest Servers - Recommend MCP servers we should review and include
• Share Experiences - Tell us about your experiences with servers we've covered
• Request Topics - Suggest topics, guides, or tutorials you'd like to see
• Provide Feedback - Share feedback on content quality, clarity, and usefulness

Credit for Contributions

• We credit community members who provide significant corrections or insights
• We acknowledge contributors in our changelog and update notes
• We link to contributor profiles or websites when appropriate
• We maintain a list of top contributors on our community page

Related Policies

Our content policy works in conjunction with other policies that govern our operations:

• Testing Process - How we test and evaluate MCP servers
• Editorial Policy - Our comprehensive editorial standards and guidelines
• Privacy Policy - How we handle user data and privacy
• Terms of Service - Terms governing use of our website