Chiark MCP Server
MCP server for AI agent discovery and quality scoring. Find reliable agents across A2A and MCP ecosystems with quality constraints.
Powered by chiark.ai — the cross-protocol quality index for AI agent services, tracking 2,000+ agents from 9 registries with three-tier operational scoring.
Quick Start
Use the hosted endpoint (recommended)
Add to your MCP client config (Claude Code, Cursor, etc.):
{
"mcpServers": {
"chiark": {
"url": "https://chiark.ai/mcp/"
}
}
}
Install locally
pip install chiark-mcp
Add to your MCP client config:
{
"mcpServers": {
"chiark": {
"command": "chiark-mcp"
}
}
}
Or run directly:
python -m chiark_mcp
Tools
find_agent
Search for AI agents by task description with quality constraints.
find_agent(
task_description="web scraping",
min_uptime=0.95,
max_latency_ms=500,
protocol="mcp",
max_results=5
)
Returns ranked agents with scores, uptime, latency, endpoint URLs.
check_agent_status
Check if an agent is alive right now.
check_agent_status(agent_id="uuid-from-find-results")
Returns: is_alive, HTTP status, response time, TLS validity, last probe timestamp.
get_agent_score
Get full quality score breakdown.
get_agent_score(agent_id="uuid")
Returns: availability (0-30), conformance (0-30), performance (0-40), uptime, latency, trend, rank.
report_outcome
Report whether a routed agent succeeded or failed. Improves future recommendations.
report_outcome(agent_id="uuid", success=true, task_category="translation")
get_ecosystem_stats
Get ecosystem overview: total agents, online count, average scores, top categories.
get_ecosystem_stats()
How It Works
Chiark crawls 9 public agent registries every 24 hours and probes every discovered agent every 30 minutes across three tiers:
- Availability — Is it alive? HTTP status, response time, TLS
- Conformance — Does it follow its declared protocol correctly?
- Performance — How fast does it respond? Task completion rate
Agents are scored 0-100 (or 0-45 for auth-gated agents that can't be fully tested).
Constraint Filters
| Parameter | Description | Example |
|---|---|---|
min_score |
Minimum operational score (0-100) | 50 |
min_uptime |
Minimum 30-day uptime (0-1) | 0.99 |
max_latency_ms |
Maximum P95 latency | 500 |
auth_required |
Filter by auth requirement | false |
payment_enabled |
Filter by x402 payment | true |
protocol |
a2a or mcp |
mcp |
category |
Skill category | Developer Tools |
Links
- Site: https://chiark.ai
- API docs: https://chiark.ai/docs
- Hosted MCP endpoint: https://chiark.ai/mcp/
- llms.txt: https://chiark.ai/llms.txt
- Agent Card: https://chiark.ai/.well-known/agent.json
License
MIT
Metadata
Release files for chiark-mcp 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| chiark_mcp-1.0.0.tar.gz | 5.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chiark_mcp-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.9 kB
Release files / chiark_mcp-1.0.0.tar.gz
| Download URL | chiark_mcp-1.0.0.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b85f054b60e03eb8038950c61565b2dc012d2180c88d209151847fc7e5022e25
|
|
BLAKE2b-256 checksum How to use checksums |
a139464a7fd50bf6b4eaf836ce4ae03cd6d0a4017448d925ffaf349093c3299b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / chiark_mcp-1.0.0-py3-none-any.whl
| Download URL | chiark_mcp-1.0.0-py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
55d4d5b073bba8be3caecdb5e3cb602a771d1cd4e580512da287af9ddd3ca474
|
|
BLAKE2b-256 checksum How to use checksums |
793b0d561c62e7be8034ba3a268356276f70d4d66ce8d9be38b74c153b455d39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for chiark-mcp 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.