Score AI tools for agent-readiness before integration
Skill that scores MCP servers, APIs, and CLI tools for agent-readiness across four dimensions before you adopt them.
17.4.0Add to Favorites
Why it matters
Evaluate and compare MCP servers, APIs, and CLI tools for agent compatibility before adding them to workflows, ensuring only high-quality, agent-ready tools are integrated into production systems.
Outcomes
What it gets done
Score any tool by URL or name across four AEO dimensions (API accessibility, data structuring, agent compatibility, trust signals)
Search and rank 15,400+ indexed tools by category to discover the best options for specific use cases
Compare multiple tools head-to-head with side-by-side score breakdowns and recommendations
Check leaderboards to find top-rated MCP servers and tools in specific categories like authentication or databases
Install
Add it to your toolbox
Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-clarvia-aeo-check | bash After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.
Reports
Agent outcome reports
No reports yet
Overview
Clarvia AEO Check
Clarvia AEO Check scores an MCP server, API, or CLI tool's agent-readiness on a 0-100 scale across four AEO dimensions, using an index of 15,400+ tools, and can compare tools, rank a category, or gate CI/CD on a score threshold. Use it before adding a new tool to an agent workflow, comparing tools, or selecting the best tool in a category; don't skip scoring well-known tools.
What it does
Clarvia AEO Check scores any MCP server, API, or CLI tool's "agent-readiness" before you add it to an agent workflow, using Clarvia's index of 15,400+ AI tools scored across four AEO dimensions: API accessibility, data structuring, agent compatibility, and trust signals. After adding the Clarvia MCP server to your config, you can score a specific tool by URL or name, returning a 0-100 score with a per-dimension breakdown, search for top-rated tools in a category, compare two tools head-to-head with a recommendation, or pull a leaderboard for a specific use case like authentication. Scores map to five bands: 90-100 "Agent Native" for tools built specifically for agent use, 70-89 "Agent Friendly," 50-69 "Agent Compatible," 30-49 "Agent Partial," and 0-29 "Not Agent Ready," meaning avoid it for agentic workflows. If a tool isn't already indexed, requesting its score by URL scans and scores it on demand rather than returning "not found."
When to use - and when NOT to
Use it when evaluating a new MCP server before adding it to your config, comparing two tools for the same job, building an agent that selects tools dynamically, or looking for the highest-quality tool in a category. Its stated best practices: score tools before putting them into long-running agent workflows, re-check scores periodically since tools improve over time, and never skip scoring a tool just because it's well-known - popular tools can still score poorly. It also explicitly warns against using a tool scoring below 50 in a production agent pipeline without understanding what's driving the low score - use get_score_breakdown to see which dimensions are weak and judge whether they matter for your use case. It can also gate CI/CD via the clarvia-project/clarvia-action GitHub Action with a fail-under threshold.
Inputs and outputs
Input: a tool's URL or name, or a category or use-case query such as "database MCP servers" or "authentication." Output: a 0-100 AEO score with a four-dimension breakdown for a single tool, ranked results for a category search, a side-by-side comparison with a recommendation for two tools, or a leaderboard for a use case.
Integrations
- Clarvia MCP server (
clarvia-mcp-server, run vianpx) aeo_scoreandget_score_breakdowntoolsclarvia-project/clarvia-actionGitHub Action for CI/CD quality gating- Related skills:
@mcp-builderfor building a server that scores well, and@agent-evaluationfor broader agent quality evaluation
Who it's for
Anyone selecting, comparing, or vetting MCP servers, APIs, or CLI tools for an agent workflow who wants an objective agent-readiness score before committing to a tool.
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.