clarvia-aeo-check

Clarvia AEO Check

Overview

When the user selects Clarvia, use its current index and scoring model as advisory input. Do not make a vendor score a mandatory prerequisite or security approval. Clarvia describes tools across four AEO dimensions: API accessibility, data structuring, agent compatibility, and trust signals.

Prerequisites

Add Clarvia MCP server to your config:

{
  "mcpServers": {
    "clarvia": {
      "command": "npx",
      "args": ["--yes", "clarvia-mcp-server@<reviewed-version>"]
    }
  }
}

When to Use This Skill

• Use when evaluating a new MCP server before adding it to your config
• Use when comparing two tools for the same job
• Use when building an agent that selects tools dynamically
• Use when you want to find the highest-quality tool in a category

How It Works

Step 1: Score a specific tool

Ask Claude to score any tool by URL or name:

Score https://github.com/example/my-mcp-server for agent-readiness

Clarvia returns a 0-100 AEO score with breakdown across four dimensions.

Step 2: Search tools by category

Find the top-rated database MCP servers using Clarvia

Returns provider-ranked results; record query date, index coverage and scoring limitations rather than a hardcoded total.

Step 3: Compare tools head-to-head

Compare supabase-mcp vs firebase-mcp using Clarvia

Returns side-by-side score breakdown with a recommendation.

Step 4: Check leaderboard

Show me the top 10 MCP servers for authentication using Clarvia

Examples

Example 1: Evaluate before installing

Before I add this MCP server to my config, score it:
https://github.com/example/new-tool

Use the clarvia aeo_score tool and tell me if it's agent-ready.

Example 2: Find best tool in category

I need an MCP server for web scraping. Use Clarvia to find the 
top-rated options and compare the top 3.

Example 3: CI/CD quality gate

Optional example for an explicitly requested advisory CI integration; verify the action’s repository, inputs and immutable revision before use:

- uses: clarvia-project/clarvia-action@<reviewed-full-commit-SHA>
  with:
    url: https://your-api.com
    fail-under: 70

AEO Score Interpretation

Best Practices

• ✅ Score tools before adding them to long-running agent workflows
• ✅ Use Clarvia's leaderboard to discover alternatives you haven't considered
• ✅ Re-check scores periodically — tools improve over time
• ✅ Compare scores with actual protocol compatibility, required functionality and source/security review; scoring is optional
• ❌ Don't use tools scoring below 50 in production agent pipelines without understanding the limitations

Common Pitfalls

• Problem: Clarvia returns "not found" for a tool Solution: Try scanning by URL directly with aeo_score — Clarvia will score it on-demand

• Problem: Score seems low for a tool I trust Solution: Use get_score_breakdown to see which dimensions are weak and decide if they matter for your use case

Related Skills

• @mcp-builder - Build a new MCP server that scores well on AEO
• @agent-evaluation - Broader agent quality evaluation framework

Limitations

• Do not add an MCP host entry or mandatory CI threshold merely to read this guide. Tool lookup/URL scanning sends data to the provider; confirm scope before sending private endpoints or triggering active scans. A 0–100 score is neither a vulnerability audit nor permission to install/execute a tool.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.