AgentCV
REMOTE · AGENTCV.AI
Search AgentCV's registry of AI agent teams and check a team profile before registering it.
Available components
Last scanned (6 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1183 tokens (~197/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Nov 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://agentcv.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentcv.ai | CN=YR2,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | RSA 2048 | SHA256-RSA | 5c138d924d690c2042eabd6c279cb5aab80 |
| SANs: agentcv.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentcv.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| agentcv.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; img-src 'self' data: https:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; connect-src 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentcv.ai/mcp | Verified | 200 | |
| http (plaintext) | http://agentcv.ai/mcp | HTTPS enforced | 308 | https://agentcv.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_registration_schema Get the AgentCV team-profile format ~89
The agentcv.team.v1 format for registering a team: the JSON Schema (as an object, and as the exact text agentcv.ai/agentcv-team.schema.json serves) and the self-contained prompt from agentcv.ai/register/with-agent that tells an agent how to write the profile. Registration itself is done by a person on agentcv.ai; this server cannot submit anything. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| finishRegistrationUrl | string | yes | – |
| format | string | yes | – |
| howToRegister | string | yes | – |
| prompt | string | yes | – |
| promptPageUrl | string | yes | – |
| schema | object | yes | – |
| schemaJson | string | yes | – |
| schemaUrl | string | yes | – |
No examples provided.
get_team Get an AgentCV team profile ~148
The public profile of one AgentCV team, as its page shows it: layer and its notice (curated teams are documented by AgentCV from public sources and are not endorsed by the team), the reference-design label, owner, trust tier, topology, size, roster (name, role and the model where stated), how it is built and overseen, evidence entries with their links and titles, cited sources, and — for an unclaimed curated team — the links where its operator can claim it or ask for its removal. Only public fields. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The team’s slug, as search_teams returns it (e.g. "ari-collective"). |
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint | object | yes | – |
| claimUrl | string|null | yes | – |
| class | string | yes | – |
| evidence | array | yes | – |
| evidenceTotal | integer | – | – |
| industries | array | – | – |
| layer | string | yes | – |
| name | string | yes | – |
| notice | string|null | yes | – |
| operatingSince | string|null | – | – |
| operatingSinceLabel | string | – | – |
| owner | object | yes | – |
| platform | string|null | – | – |
| referenceDesign | object|null | yes | Set when the profile is a reference design: a design documented from a paper, framework docs or vendor material that no one is known to operate. null for every other team. |
| removalUrl | string|null | yes | – |
| requestUrl | string | – | – |
| roster | array | yes | – |
| size | object|null | – | Team size as the site words it: kind "total" is the stated size ("5 agents"); kind "listed" is a curated team whose sources state no total ("3 listed members"). null when no size is stated. |
| slug | string | yes | – |
| sources | array | yes | – |
| status | string | yes | – |
| tagline | string | yes | – |
| taskKinds | array | – | – |
| topology | object|null | – | – |
| trust | object | yes | – |
| url | string | yes | – |
No examples provided.
list_platforms List AgentCV platform hubs ~72
The platform hubs of agentcv.ai/platforms (Claude, OpenAI Codex, OpenClaw, CrewAI, LangGraph, …) with the platform names each covers and how many public teams each holds, by layer and by class. AgentCV is independent and not affiliated with any platform. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| platforms | array | yes | – |
No examples provided.
list_use_cases List AgentCV use-case hubs ~66
The use-case hubs of agentcv.ai/use-cases (code review, testing and QA, research and analysis, …) with how many public teams each holds, by layer (real, curated, illustrative) and by class (operated, reference design, illustrative). Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| useCases | array | yes | – |
No examples provided.
search_teams Search AgentCV teams ~301
Search the public AgentCV registry of AI agent teams. Returns public teams only, in the site’s default order: operated teams first, then reference designs (designs documented from papers, framework docs or vendor material that no one is known to run), then clearly labelled illustrative demos. Each team has its layer (real = registered by its owner, curated = documented by AgentCV from cited public sources, illustrative = demo), size wording, platform, topology, trust tier and page URL. All filters are optional and combine with AND. Pages of up to 20; pass nextCursor back as cursor for the next page. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | nextCursor from the previous page; omit for the first page. |
| layer | string | – | real = registered by its owner; curated = documented by AgentCV from cited public sources; illustrative = clearly labelled demo. |
| limit | integer | – | Teams per page, 1–20 (default 10). |
| platform | string | – | A platform hub slug (see list_platforms): teams whose own platform or any listed member’s platform belongs to that hub. |
| query | string | – | Text to find in a team’s name, tagline or description (case-insensitive substring), as the search box on agentcv.ai/teams. |
| topology | string | – | The team’s declared topology type. |
| use_case | string | – | A use-case hub slug (see list_use_cases). |
| Name | Type | Req | Description |
|---|---|---|---|
| nextCursor | string|null | yes | – |
| order | string | yes | – |
| returned | integer | yes | – |
| teams | array | yes | – |
| total | integer | yes | Teams matching the filters, across all pages. |
No examples provided.
validate_team_profile Check an AgentCV team profile ~298
Check an agentcv.team.v1 team profile with the same validator the registration page’s import panel uses (the same field rules the server enforces), and with AgentCV’s secret and personal-data detectors. Returns the errors, the warnings (example values left in, values over the form’s limit, ignored keys) and the fields that look like an API key, token, password or personal data (named by path, never repeated), plus the URL where a person signs in, imports the file, reviews it and submits. When the profile is ready, it also returns finishUrl: the registration form’s link with the profile in its # fragment, at most 16 KB, for the person to open, review and submit. Browsers do not send the fragment in HTTP requests, but it is not encrypted: anyone with the link can read it. No link is returned while a value, as written or once percent-, base64- or hex-decoded, looks like a secret, personal data, a local path or a private or credential-bearing link; detection is best effort, and the person’s review before Submit is the final check. This server receives the profile to check it; it neither stores nor logs it, and submits nothing. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | – | yes | The profile: the agentcv.team.v1 JSON object, or its JSON text exactly as it would be pasted into the import panel (at most 64 KB). |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| finishLink | object | yes | – |
| finishRegistrationUrl | string | yes | – |
| finishUrl | – | yes | – |
| nextSteps | string | yes | – |
| readyToImport | boolean | yes | – |
| redacted | integer | yes | – |
| stored | boolean | yes | – |
| truncated | object | yes | – |
| valid | boolean | yes | – |
| warnings | array | yes | – |
| withheld | array | yes | – |
No examples provided.
How do I install the AgentCV MCP server?
AgentCV is a hosted endpoint at https://agentcv.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentcv.ai
claude mcp add --transport http ai-agentcv-registry 'https://agentcv.ai/mcp'
What is the AgentCV MCP server?
AgentCV is an MCP server listed in the public MCP registry as ai.agentcv/registry. Search AgentCV's registry of AI agent teams and check a team profile before registering it. This page covers its hosted endpoint (https://agentcv.ai/mcp).
Is the AgentCV MCP server safe to use?
AgentCV scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AgentCV MCP server expose?
AgentCV exposes 6 tools: search_teams, get_team, list_use_cases, list_platforms, get_registration_schema, validate_team_profile. Their descriptions and schemas cost roughly 974 tokens of context every time the server is loaded.
Does the AgentCV MCP server require authentication?
No. We connected to AgentCV without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentCV MCP server still maintained?
AgentCV is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.