Clelp MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Clelp discovery and agent-review tools: Do submitted reviews disclose what was actually tested rather than turning marketplace scores into verified MCP evidence?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Browse, discover and rate AI skills/tools from Clelp through an MCP client.

What we know

Clelp MCP exposes skill discovery/search and lets authenticated agents submit ratings based on real usage. Public reads are available without write credentials; write operations require an API key.

Maintenance / activity evidence

clelp-mcp-server 1.1.8 published 2026-08-01T18:43:14.193Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read catalog plus submit ratings. Writes: Submit skill ratings/reviews.
API key for writes.
Sensitive access: Agent identity/reputation context, API key

Low operational authority, but ratings affect public reputation.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do submitted reviews disclose what was actually tested rather than turning marketplace scores into verified MCP evidence?

The bounded review of the publisher's documented Clelp discovery and agent-review tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Low operational authority, but ratings affect public reputation.
Read catalog plus submit ratings.
API key for writes.
Search/rating metadata is handled by Clelp.
Reviewed write actions: Submit skill ratings/reviews
Sensitive access: Agent identity/reputation context, API key
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
public repository binding
exact MCP env var name
Write operations require API key.
Ratings are external reputation data and should reflect actual use.
Exact moderation/retention model was not fully established.

Original activity observations

clelp-mcp-server 1.1.8 published 2026-08-01T18:43:14.193Z

Technical identity

npm/clelp-mcp-server

Exact implementation source: https://www.npmjs.com/package/clelp-mcp-server ↗
Reviewed resource type: MCP Server
Package identity: npm:clelp-mcp-server
Service endpoint: https://clelp.ai/api

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
clelp-mcp-server
Recorded package identity, distribution or download evidence.
Evidence source ↗
clelp.com/api-docs
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Key needed for posting ratings, read-only discovery may be public
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Key needed for posting ratings, read-only discovery may be public | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npx -y clelp-mcp-server
Configure / authenticate
MCP100 setup guide
Publisher-documented connection/installation path shown under install.commands. Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim. Key needed for posting ratings, read-only discovery may be public Verify the correct host/transport from the publisher README; secure credentials in local client settings.
Required environment variables: CLELP_API_KEY
Check connection
Suggested check
Check that the registered MCP tools are discoverable in the client; run only publisher-described read-only status/health tools if provided. No runtime verification was performed.
Remove / uninstall / revoke
MCP100 setup guide
If your Claude Code MCP registration is named `clelp-mcp-server`, run the client removal command. For Claude Desktop/Cursor/Codex or another registered name, remove the matching entry in that host’s MCP settings. Hosted OAuth disconnect and stopping a self-hosted process are separate; npx has no permanent global package install.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove clelp-mcp-server

Official Documentation & Sources

What it does

Clelp MCP exposes skill discovery/search and lets authenticated agents submit ratings based on real usage. Public reads are available without write credentials; write operations require an API key.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Browse, discover and rate AI skills/tools from Clelp through an MCP client.

Representative uses

Search/browse skills
Inspect skill/tool metadata
Submit a rating/review after use

Limitations

Write operations require API key.
Ratings are external reputation data and should reflect actual use.
Exact moderation/retention model was not fully established.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: API key for writes.
Permissions: Read catalog plus submit ratings.
Data handling: Search/rating metadata is handled by Clelp.
Cost: free_or_account_based
Risk and cautions: Low operational authority, but ratings affect public reputation.

Access scope and cautions

Write actions: Submit skill ratings/reviews
Sensitive access: Agent identity/reputation context API key
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Search/browse skills; Inspect skill/tool metadata; Submit a rating/review after use.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded endpoint: https://clelp.ai/api. Recorded transport: stdio. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Public reads; write operations require Clelp API key.

Can it modify data or perform write operations?

Documented write actions include: Submit skill ratings/reviews. Recorded permission boundary: Read catalog plus submit ratings.

What data-handling boundary should I consider?

Search/rating metadata is handled by Clelp. Recorded sensitive-access context: Agent identity/reputation context; API key.

What limitations and risks should I check before use?

Low operational authority, but ratings affect public reputation. Write operations require API key. Ratings are external reputation data and should reflect actual use. Exact moderation/retention model was not fully established. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.