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.

Anclum

REMOTE · ANCLUM.COM

Search MCP servers, agent skills and open-source AI projects, plus AI tools. Read-only.

Available components

+3 this week 74 Trust /100

Last scanned (11 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 282 tokens (~94/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1
    • Server version: 0.2.0 → 0.2.1 functional
  • 23 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_tools” rewrote its description, which is the text the model reads security
  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

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 5 Nov 2026 · Probed https://anclum.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=anclum.com CN=YE1,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA384 60ae62fcd88cfd9b7fe8d04c1ec505ac5e4
SANs: anclum.com, www.anclum.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 anclum.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
anclum.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
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://anclum.com/mcp Verified 200
http (plaintext) http://anclum.com/mcp HTTPS enforced 301 https://anclum.com/mcp
MCP tools · 3 exposed · ~238 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
get_tool ~61

Get one catalogue entry by its key (the slug used in its Anclum URL). Returns the full record: name, url, description, tags, source, first/last seen. Read-only.

NameTypeReqDescription
keystringyesThe entry key/slug

No output schema declared.

No examples provided.

list_categories ~52

List the catalogue's taxonomies: AI-tool categories (with counts) and field tags (e.g. "MCP 服务", "Agent 技能"). Useful for then calling search_tools with a category. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_tools ~125

Search Anclum's catalogue of MCP servers, agent skills and open-source AI projects, plus AI tools for people who are not developers. Returns name, url, one-line summary and tags. Read-only.

NameTypeReqDescription
category––Optional: limit to one AI-tool category slug (e.g. ai-writing) or a field tag (e.g. MCP 服务)
limitinteger–Max results (default 10, max 50)
querystringyesWhat you are looking for, e.g. "kubernetes", "video editing", "写小说"

No output schema declared.

No examples provided.

Install

How do I install the Anclum MCP server?

Anclum is a hosted endpoint at https://anclum.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 · anclum.com

# add to Claude Code
claude mcp add --transport http wdfdaivd-anclum 'https://anclum.com/mcp'
Common questions

What is the Anclum MCP server?

Anclum is an MCP server listed in the public MCP registry as io.github.wdfdaivd/anclum. Search MCP servers, agent skills and open-source AI projects, plus AI tools. Read-only. This page covers its hosted endpoint (https://anclum.com/mcp).

Is the Anclum MCP server safe to use?

Anclum scores 74 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 Anclum MCP server expose?

Anclum exposes 3 tools: search_tools, get_tool, list_categories. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.

Does the Anclum MCP server require authentication?

No. We connected to Anclum without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Anclum MCP server still maintained?

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