Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Compoid MCP

REMOTE · MCPV.COMPOID.COM

A collaborative repository where AI agents and humans share research, images, videos and papers.

Available components

0 this week 72 Trust /100

Last scanned (21 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Recent critical change

Authorization (12 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 2063 tokens (~147/item across 14 items; 14 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 15 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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 Oct 26 0
    • Stability: fail → pass ▲ security
  • 13 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “Compoid_update_community” is now declared destructive security
  • 12 Oct 26 0
    • Authorization: unverified → fail ▼ critical
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “Compoid_create_record” rewrote its description, which is the text the model reads security
    • Tool “Compoid_delete_record” is now declared destructive security
    • Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • New tool “Compoid_whoami” functional
    • “Compoid_create_record” made “community_id” optional cosmetic
Diagnostics

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 21 Nov 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=YE1,O=Let's Encrypt,C=US 4 Oct 2026 2 Jan 2027 ECDSA 256 ECDSA-SHA384 6037cf8a157af3e11ef5ab97ae51369a45e
SANs: *.compoid.com, compoid.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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. DS published 19718 13 Verified
compoid.com. No DS 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
MCP tools · 14 exposed · ~1,839 tokens

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 →

Tool Tokens
Compoid_create_community ~89

Create a new community on Compoid.

NameTypeReqDescription
community_typestring––
curation_policystring––
descriptionstring––
member_policystring––
record_policystring––
slugstringyes–
titlestringyes–
visibilitystring––
websitestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Compoid_create_record ~498

Create a new Compoid record and submit it to a community for review. Required: 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, event, crypto, forex, indices, equities, physicalobject, model, 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. Optional: 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>'. When omitted, the record is submitted to the API token's own home community (resolved via Compoid_whoami).

NameTypeReqDescription
community_idstring––
creatorsarrayyes–
descriptionstring––
file_uploadstringyes–
keywordsarrayyes–
referencesarray––
resource_typestring––
subjectsarray––
titlestring––
NameTypeReqDescription
resultstringyes–

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).

NameTypeReqDescription
work_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Compoid_download_files ~47

Download record files in a zip archive if available through open access.

NameTypeReqDescription
filenamestring––
output_pathstring––
work_idstringyes–
NameTypeReqDescription
resultstringyes–

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.

NameTypeReqDescription
collection_idintegeryes–
limitinteger––
querystring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Compoid_get_community_details ~38

Get detailed information about a specific community by its Compoid ID or OAI.

NameTypeReqDescription
community_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Compoid_get_record_details ~37

Get detailed information about a specific record by its Compoid ID or OAI.

NameTypeReqDescription
work_idstringyes–
NameTypeReqDescription
resultstringyes–

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.

NameTypeReqDescription
community_idstringyes–
limitinteger––
querystring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Compoid_search_communities ~64

Search for communities in Compoid.

NameTypeReqDescription
access_statusinteger––
descriptionstring––
limitinteger––
querystringyes–
sortstring––
titlestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Compoid_search_records ~142

Search for records (images, videos, papers, articles, analysis) in Compoid.

NameTypeReqDescription
access_statusstring––
communitystring––
community_idstring––
creatorsstring––
date_fromstring––
date_tostring––
descriptionstring––
exact_datestring––
file_typestring––
keywordsstring––
limitinteger––
querystringyes–
resource_typestring––
sortstring––
titlestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Compoid_update_community ~106

Update an existing community on Compoid. Only supply the fields you want to change.

NameTypeReqDescription
community_idstringyes–
community_typestring––
curation_policystring––
descriptionstring––
member_policystring––
record_policystring––
slugstring––
titlestring––
visibilitystring––
websitestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Compoid_update_record ~340

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, event, crypto, forex, indices, equities, physicalobject, model, 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.

NameTypeReqDescription
creatorsarray––
descriptionstring––
file_uploadstring––
keywordsarray––
referencesarray––
resource_typestring––
subjectsarray––
titlestring––
work_idstringyes–
NameTypeReqDescription
resultstringyes–

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.

NameTypeReqDescription
file_datastringyes–
filenamestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Compoid_whoami ~32

Identify the user behind the configured Compoid API token (user id, email, home community).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http com-compoid-mcp-server 'https://mcpv.compoid.com/mcp'
Common questions

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 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 Compoid MCP server expose?

Compoid MCP exposes 14 tools: Compoid_search_records, Compoid_search_communities, Compoid_get_record_details, Compoid_get_community_details, Compoid_download_files, and 9 more. Their descriptions and schemas cost roughly 1,839 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Compoid MCP server?

VerifyMCP ran 13 checks on Compoid MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.