Skip to content

feat: add clarvia-mcp-server - AEO scoring for AI agent tools - #316

Closed
digitamaz wants to merge 1 commit into
pathintegral-institute:mainfrom
digitamaz:add-clarvia
Closed

feat: add clarvia-mcp-server - AEO scoring for AI agent tools#316
digitamaz wants to merge 1 commit into
pathintegral-institute:mainfrom
digitamaz:add-clarvia

Conversation

@digitamaz

@digitamaz digitamaz commented Mar 26, 2026

Copy link
Copy Markdown

Description

Add Clarvia MCP Server to the MCPM registry.

Clarvia provides AEO (Agent Experience Optimization) scoring for 15,400+ MCP servers and AI tools. It's the quality gate for the agent tool ecosystem — helping AI agents and developers make informed decisions about which tools to use.

Server Details

  • npm package: clarvia-mcp-server
  • install: npx -y clarvia-mcp-server
  • License: MIT
  • Weekly downloads: 232+
  • Tools indexed: 15,400+

What it does

Clarvia scores services on 4 AEO dimensions (0-100 each):

  1. API Accessibility — Can AI agents find and connect to this service?
  2. Data Structuring — Is the data formatted for machine consumption?
  3. Agent Compatibility — Does this service support agentic workflows?
  4. Trust Signals — Does the service provide verifiable trust indicators?

Key MCP tools:

  • clarvia_gate_check — Binary pass/fail check before trusting a tool
  • clarvia_scan — Full AEO scan with dimension breakdown
  • clarvia_search — Find the best tools by AEO score
  • clarvia_find_alternatives — Get better alternatives for underperforming tools

Links

Summary by CodeRabbit

  • New Features
    • Added Clarvia MCP server to the registry, including metadata, installation instructions, and example prompts for various use cases.

@qodo-code-review

Copy link
Copy Markdown
Contributor

Review Summary by Qodo

Add Clarvia MCP Server to registry

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Add Clarvia MCP Server to registry for AEO scoring
• Provides quality assessment for 15,400+ MCP tools
• Enables agent compatibility and tool discovery features
• Includes gate-check, scanning, and search capabilities
Diagram
flowchart LR
  Registry["MCP Registry"]
  ClarviaMCP["Clarvia MCP Server<br/>clarvia-mcp-server.json"]
  AEOScoring["AEO Scoring<br/>4 Dimensions"]
  Tools["15,400+ Tools<br/>Indexed"]
  Registry -- "registers" --> ClarviaMCP
  ClarviaMCP -- "provides" --> AEOScoring
  AEOScoring -- "scores" --> Tools
Loading

Grey Divider

File Changes

1. mcp-registry/servers/clarvia-mcp-server.json ✨ Enhancement +57/-0

Add Clarvia MCP Server registry configuration

• New registry entry for Clarvia MCP Server with complete metadata
• Defines npm installation method using npx -y clarvia-mcp-server
• Includes 8 semantic tags for discoverability and categorization
• Provides 3 practical usage examples for gate-checking, searching, and auditing tools
• Specifies MIT license and links to GitHub repository and homepage

mcp-registry/servers/clarvia-mcp-server.json


Grey Divider

Qodo Logo

@qodo-code-review

qodo-code-review Bot commented Mar 26, 2026

Copy link
Copy Markdown
Contributor

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 📐 Spec deviations (0)

Grey Divider


Action required

1. Invalid category values 🐞 Bug ✓ Correctness
Description
The new server manifest uses category strings ("AI Agents", "Development Tools") that are not in the
registry schema’s allowed category enum, so manifest validation will fail. This will break the CI
"Validate Server JSON Files" job for the PR.
Code

mcp-registry/servers/clarvia-mcp-server.json[R52-55]

+  "categories": [
+    "AI Agents",
+    "Development Tools"
+  ],
Evidence
The registry schema restricts categories[] to a fixed enum (e.g., "Dev Tools", "AI Systems", "MCP
Tools", etc.), and the CI workflow validates all mcp-registry/servers/*.json against that schema;
therefore non-enum values will deterministically fail validation.

mcp-registry/schema/server-schema.json[70-90]
.github/workflows/test.yml[11-25]
mcp-registry/servers/clarvia-mcp-server.json[52-55]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`mcp-registry/servers/clarvia-mcp-server.json` sets `categories` to values that are not permitted by `mcp-registry/schema/server-schema.json`, causing CI schema validation to fail.

### Issue Context
The schema restricts categories to a fixed enum (e.g., `Dev Tools`, `AI Systems`, `MCP Tools`, etc.). CI validates every `mcp-registry/servers/*.json` file against this schema.

### Fix Focus Areas
- mcp-registry/servers/clarvia-mcp-server.json[52-55]

### What to change
Replace the current category strings with one or more values from the schema enum (for example, map `Development Tools` → `Dev Tools` and `AI Agents` → `AI Systems`, or choose the single best-fitting schema category).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

@coderabbitai

coderabbitai Bot commented Mar 26, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

A new JSON registry entry for clarvia-mcp-server has been added, containing metadata including display name, repository information, installation instructions, and example prompts for MCP server selection and configuration tasks.

Changes

Cohort / File(s) Summary
New MCP Registry Entry
mcp-registry/servers/clarvia-mcp-server.json
New registry metadata file with server details, installation command via npx, example prompts for tool checking and server selection, and configuration documentation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

Review effort 2/5

Suggested reviewers

  • calmini

Poem

🐰 A registry grows with each new entry,
Clarvia joins the quest—quite the adventure!
With prompts and metadata, polished and clean,
A new MCP server arrives on the scene.
Hop-skip through configs, let tools dance free! 🎪

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and accurately describes the main change: adding the clarvia-mcp-server to the registry with a focus on its AEO scoring functionality for AI agent tools.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
mcp-registry/servers/clarvia-mcp-server.json (1)

25-29: Pin the npm package version in npx invocation.

Using npx -y clarvia-mcp-server without a version specifier always executes the latest published version, introducing supply-chain drift and non-reproducible installs. Pin to an exact version such as clarvia-mcp-server@1.1.0 (the current latest):

Proposed change
      "command": "npx",
      "args": [
        "-y",
-       "clarvia-mcp-server"
+       "clarvia-mcp-server@1.1.0"
      ],
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@mcp-registry/servers/clarvia-mcp-server.json` around lines 25 - 29, The npx
invocation currently uses an unpinned package name ("clarvia-mcp-server") which
can pull changing releases; update the args array for the "npx" command so the
package is pinned to a specific semver (e.g., replace "clarvia-mcp-server" with
"clarvia-mcp-server@1.1.0") to ensure reproducible installs and prevent
supply-chain drift.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@mcp-registry/servers/clarvia-mcp-server.json`:
- Line 51: The description field contains a volatile numeric claim ("15,400+")
that will age; update the "description" value in clarvia-mcp-server.json to use
evergreen wording (e.g., "thousands of MCP servers and AI agent tools", "a large
catalog of MCP servers and agent tools", or move the exact count to external
docs/website) so the registry metadata remains accurate over time.

---

Nitpick comments:
In `@mcp-registry/servers/clarvia-mcp-server.json`:
- Around line 25-29: The npx invocation currently uses an unpinned package name
("clarvia-mcp-server") which can pull changing releases; update the args array
for the "npx" command so the package is pinned to a specific semver (e.g.,
replace "clarvia-mcp-server" with "clarvia-mcp-server@1.1.0") to ensure
reproducible installs and prevent supply-chain drift.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 02050d82-a378-4146-bac3-0123e9a4f3ab

📥 Commits

Reviewing files that changed from the base of the PR and between 3a21496 and 4f30eac.

📒 Files selected for processing (1)
  • mcp-registry/servers/clarvia-mcp-server.json

}
],
"name": "clarvia-mcp-server",
"description": "AEO (Agent Experience Optimization) scoring for 15,400+ MCP servers and AI agent tools. Gate-check APIs before using them, score your own MCP server, find agent-friendly alternatives, and search the indexed tool catalog.",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Avoid volatile quantitative claims in static description text.

"15,400+" will age quickly and make registry metadata stale. Consider evergreen wording (or move counts to docs/website).

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@mcp-registry/servers/clarvia-mcp-server.json` at line 51, The description
field contains a volatile numeric claim ("15,400+") that will age; update the
"description" value in clarvia-mcp-server.json to use evergreen wording (e.g.,
"thousands of MCP servers and AI agent tools", "a large catalog of MCP servers
and agent tools", or move the exact count to external docs/website) so the
registry metadata remains accurate over time.

Comment on lines +52 to +55
"categories": [
"AI Agents",
"Development Tools"
],

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Invalid category values 🐞 Bug ✓ Correctness

The new server manifest uses category strings ("AI Agents", "Development Tools") that are not in the
registry schema’s allowed category enum, so manifest validation will fail. This will break the CI
"Validate Server JSON Files" job for the PR.
Agent Prompt
### Issue description
`mcp-registry/servers/clarvia-mcp-server.json` sets `categories` to values that are not permitted by `mcp-registry/schema/server-schema.json`, causing CI schema validation to fail.

### Issue Context
The schema restricts categories to a fixed enum (e.g., `Dev Tools`, `AI Systems`, `MCP Tools`, etc.). CI validates every `mcp-registry/servers/*.json` file against this schema.

### Fix Focus Areas
- mcp-registry/servers/clarvia-mcp-server.json[52-55]

### What to change
Replace the current category strings with one or more values from the schema enum (for example, map `Development Tools` → `Dev Tools` and `AI Agents` → `AI Systems`, or choose the single best-fitting schema category).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

@digitamaz digitamaz closed this by deleting the head repository Apr 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant