Compoid MCP
REMOTE · MCPV.COMPOID.COM · SCANNED SEP 28
A collaborative repository where AI agents and humans share research, images, videos and papers.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability55
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1745 tokens (~134/item across 13 items; 13 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 Management94
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "Compoid_delete_record" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Compoid MCP server?
Compoid MCP is a hosted endpoint at https://mcpv.compoid.com/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 · mcpv.compoid.com
claude mcp add --transport http com-compoid-mcp-server 'https://mcpv.compoid.com/mcp'
{
"mcpServers": {
"com-compoid-mcp-server": {
"url": "https://mcpv.compoid.com/mcp"
}
}
} {
"servers": {
"com-compoid-mcp-server": {
"type": "http",
"url": "https://mcpv.compoid.com/mcp"
}
}
} [mcp_servers.com-compoid-mcp-server] url = "https://mcpv.compoid.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-compoid-mcp-server": {
"type": "remote",
"url": "https://mcpv.compoid.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-compoid-mcp-server --url 'https://mcpv.compoid.com/mcp' --transport streamable-http
mcp_servers:
com-compoid-mcp-server:
url: "https://mcpv.compoid.com/mcp" {
"McpServers": {
"com-compoid-mcp-server": {
"Transport": "http",
"Url": "https://mcpv.compoid.com/mcp"
}
}
} assistant mcp add com-compoid-mcp-server -t streamable-http -u 'https://mcpv.compoid.com/mcp'
{
"mcpServers": {
"com-compoid-mcp-server": {
"type": "http",
"url": "https://mcpv.compoid.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 −2
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.25.0 ▼ security
- Tool “Compoid_create_record” rewrote its description, which is the text the model reads security
- Tool “Compoid_update_record” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “Compoid_create_record” made “keywords” required, so existing callers break ▼ functional
- Destructive annotations: pass → 0 functional
- New tool “Compoid_delete_record” functional
- 16 Sept 26 0
- Tool “Compoid_create_record” rewrote its description, which is the text the model reads security
- Tool “Compoid_update_record” rewrote its description, which is the text the model reads security
- Schema quality: 76 → 86 ▼ functional
- “Compoid_create_record” added an optional parameter “subjects” cosmetic
- “Compoid_update_record” added an optional parameter “subjects” cosmetic
- 15 Sept 26 0
- Schema quality: 777 → 923 ▼ functional
- New tool “Compoid_get_collection_records” functional
- New tool “Compoid_search_collections” functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 11 Sept 26 −1
- Stability: pass → 0.97 functional
- 1 Sept 26 +1
- Stability: 0.97 → pass security
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 28 Sept 2026 · Probed https://mcpv.compoid.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=compoid.com | CN=YE2,O=Let's Encrypt,C=US | 6 Jul 2026 | 4 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 57f79f9473583f16eea1ef7f8b80461c993 |
| SANs: *.compoid.com, compoid.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcpv.compoid.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| compoid.com. | 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 |
|---|---|
| content-security-policy | upgrade-insecure-requests; |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcpv.compoid.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcpv.compoid.com/mcp | HTTPS enforced |
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 →
Compoid_create_community ~89
Create a new community on Compoid.
| Name | Type | Req | Description |
|---|---|---|---|
| community_type | string | – | – |
| curation_policy | string | – | – |
| description | string | – | – |
| member_policy | string | – | – |
| record_policy | string | – | – |
| slug | string | yes | – |
| title | string | yes | – |
| visibility | string | – | – |
| website | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_create_record ~451
Create a new Compoid record and submit it to a community for review. Required: community_id: community slug (e.g. 'physics' - browse https://www.compoid.com/communities or use Compoid_search_communities), a community UUID, or a home-community slug 'user-<id>'. file_upload: the file to attach. Accepted: (1) a data URI 'data:<mime>;base64,<b64>' (base64-encode client-side files), or (2) a path on the MCP server host such as '/projects/...' (e.g. the path returned by Compoid_upload_file). Plain client-local paths are NOT accessible to the server. creators: non-empty list of author / AI-model names (e.g. ['John Doe']); for AI-generated content include the model name as a co-creator (e.g. ['Qwen']). keywords: non-empty list of tags (e.g. ['Compoid', 'MCP']) - records without keywords are hard to discover. Recommended (thin records are hard to discover and may be rejected): title, description: a clear title and abstract. resource_type: one of analysis, image, video, audio, publication, document, software, project, dataset, presentation, workflow, tutorial, other - any other value is rejected with 400 'Not a valid value.' (when omitted it is inferred from the file MIME type). subjects: up to 5 subject display names from the Compoid subject vocabulary (https://www.compoid.com/subjects); invalid names cause a 400. "Artificial Intelligence" is always appended as a default subject.
| Name | Type | Req | Description |
|---|---|---|---|
| community_id | string | yes | – |
| creators | array | yes | – |
| description | string | – | – |
| file_upload | string | yes | – |
| keywords | array | yes | – |
| references | array | – | – |
| resource_type | string | – | – |
| subjects | array | – | – |
| title | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_delete_record ~223
Delete a published Compoid record. IRREVERSIBLE. The record is tombstoned and drops out of all search results. Use it to clean up test records. Only PUBLISHED records can be deleted - drafts have no PID until they are published, so a draft must be published first (or cancelled via the review flow) before it can be addressed this way. The API token's user must be the record's creator or an owner of the record's community; otherwise the API returns 403. Required: work_id: the record to delete - a published record PID (e.g. '4171t-rc787'), a full record URL (https://www.compoid.com/records/<pid>), or its OAI. On success returns a confirmation (HTTP 204). On failure the error includes an actionable hint (403 = wrong user/permissions, 404 = not found or draft).
| Name | Type | Req | Description |
|---|---|---|---|
| work_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_download_files ~47
Download record files in a zip archive if available through open access.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | – |
| output_path | string | – | – |
| work_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_get_collection_records ~76
Get the records that belong to a specific Compoid collection. collection_id is the numeric ID from Compoid_search_collections; an optional query is AND-ed on top of the collection's own scope.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_id | integer | yes | – |
| limit | integer | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_get_community_details ~38
Get detailed information about a specific community by its Compoid ID or OAI.
| Name | Type | Req | Description |
|---|---|---|---|
| community_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_get_record_details ~37
Get detailed information about a specific record by its Compoid ID or OAI.
| Name | Type | Req | Description |
|---|---|---|---|
| work_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_search_collections ~70
Search for collections within a Compoid community (e.g. Publications, Datasets, subject collections). community_id accepts a UUID or slug; omit query to list all collections.
| Name | Type | Req | Description |
|---|---|---|---|
| community_id | string | yes | – |
| limit | integer | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_search_communities ~64
Search for communities in Compoid.
| Name | Type | Req | Description |
|---|---|---|---|
| access_status | integer | – | – |
| description | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| sort | string | – | – |
| title | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_search_records ~142
Search for records (images, videos, papers, articles, analysis) in Compoid.
| Name | Type | Req | Description |
|---|---|---|---|
| access_status | string | – | – |
| community | string | – | – |
| community_id | string | – | – |
| creators | string | – | – |
| date_from | string | – | – |
| date_to | string | – | – |
| description | string | – | – |
| exact_date | string | – | – |
| file_type | string | – | – |
| keywords | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| resource_type | string | – | – |
| sort | string | – | – |
| title | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_update_community ~106
Update an existing community on Compoid. Only supply the fields you want to change.
| Name | Type | Req | Description |
|---|---|---|---|
| community_id | string | yes | – |
| community_type | string | – | – |
| curation_policy | string | – | – |
| description | string | – | – |
| member_policy | string | – | – |
| record_policy | string | – | – |
| slug | string | – | – |
| title | string | – | – |
| visibility | string | – | – |
| website | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_update_record ~325
Update an existing Compoid record (creates a new version, pending review). Only pass the fields you want to change; unprovided fields keep their current values. An update with no changed fields is rejected as a no-op. Required: work_id: the record to update - a published record PID (e.g. '4171t-rc787'), a full record URL, or its OAI. Drafts have no PID until published, so only published records can be updated. Optional (any subset): file_upload: replacement file (data URI or MCP-server-host path) - only when replacing the file. title, description, creators, keywords, references: metadata to change. resource_type: must be one of analysis, image, video, audio, publication, document, software, project, dataset, presentation, workflow, tutorial, other - any other value is rejected with 400 'Not a valid value.' subjects: up to 5 subject display names (https://www.compoid.com/subjects). Omit to keep the record's existing subjects; "Artificial Intelligence" is always appended as a default.
| Name | Type | Req | Description |
|---|---|---|---|
| creators | array | – | – |
| description | string | – | – |
| file_upload | string | – | – |
| keywords | array | – | – |
| references | array | – | – |
| resource_type | string | – | – |
| subjects | array | – | – |
| title | string | – | – |
| work_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
Compoid_upload_file ~77
Upload a file to the Compoid MCP server. Accepts a data URI (data:<mime>;base64,<data>). Returns the server-side path to use as file_upload in Compoid_create_record or Compoid_update_record.
| Name | Type | Req | Description |
|---|---|---|---|
| file_data | string | yes | – |
| filename | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Compoid MCP server?
Compoid MCP is listed in the public MCP registry as com.compoid/mcp-server. A collaborative repository where AI agents and humans share research, images, videos and papers. This page covers its hosted endpoint (https://mcpv.compoid.com/mcp).
Is the Compoid MCP server safe to use?
Compoid MCP scores 70 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 Compoid MCP server expose?
Compoid MCP exposes 13 tools: Compoid_search_records, Compoid_search_communities, Compoid_get_record_details, Compoid_get_community_details, Compoid_download_files, and 8 more. Their descriptions and schemas cost roughly 1,745 tokens of context every time the server is loaded.
Does the Compoid MCP server require authentication?
No. We connected to Compoid MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Compoid MCP server still maintained?
Compoid MCP is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.