app.netlify.clify-dev/clify
REMOTE · BOLD-CLOUD-H4U6S.RUN.MCP-USE.COM
Verified websites as JSON commands for AI agents over plain curl or MCP.
Available components
Last scanned (2 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Web Scraping
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (clify_run). See how to fix → View diagnostics → Fail
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 930 tokens (~116/item across 8 items; 7 tools + 1 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 23 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.
- 21 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 65
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 24 Oct 2026 · Probed https://bold-cloud-h4u6s.run.mcp-use.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.run.mcp-use.com | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 9c485fdb774d6faa0e800b5ffe82ed8e |
| SANs: *.run.mcp-use.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of bold-cloud-h4u6s.run.mcp-use.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mcp-use.com. | present | 2371 | 13 | Verified |
| bold-cloud-h4u6s.run.mcp-use.com. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bold-cloud-h4u6s.run.mcp-use.com/mcp | Verified | 200 | |
| http (plaintext) | http://bold-cloud-h4u6s.run.mcp-use.com/mcp | HTTPS enforced | 301 | https://bold-cloud-h4u6s.run.mcp-use.com/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 →
clify_help Commands and params of a site ~85
A site's commands with params ("name*" = required, ":a|b" = allowed values, "=x" = default). Pass command for full param docs, default fields and a ready clify_run call.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | one command name for full details |
| site | string | yes | site name from clify_sites, e.g. crates, weather |
No output schema declared.
No examples provided.
clify_run Run a site command ~156
Call one command of a clify site and get JSON back. args holds the command's params (see clify_help). Lists return count, total and nextPage (args for the next page). Write commands return a dry-run preview unless confirm:true.
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | – | params, e.g. {"name":"serde"} |
| command | string | yes | command name, e.g. get-crate |
| confirm | boolean | – | true sends a write; otherwise writes return a preview |
| fields | string | – | comma-separated keys to keep (dot paths ok); "*" for all |
| limit | integer | – | first N items of a list |
| site | string | yes | site name, e.g. crates |
No output schema declared.
No examples provided.
clify_sites Find a clify site ~153
Search the catalogue of 135 real websites clify can call (package registries, government data, science, news, jobs, weather, culture…). Pass a keyword query to get the best sites with their matching commands. Without a query it pages through the catalogue, one line per site ("name (category, commands): about"); filter with category. Start here.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | max sites (default 6 with a query, 40 per page without) |
| offset | integer | – | skip this many sites when paging the catalogue (see nextPage) |
| query | string | – | what you need, e.g. "rust crate versions" or "weather forecast" |
No output schema declared.
No examples provided.
crates__get-crate crates get-crate ~111
crates.io: Get a crate's details: description, links, download totals, keywords, categories and default version Returns name, description, default_version, downloads, recent_downloads, num_versions, keywords, categories, repository, documentation, homepage, updated_at by default. (Same as clify_run site=crates command=get-crate.)
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | keys to keep; "*" for all |
| limit | integer | – | – |
| name | string | yes | Crate name |
No output schema declared.
No examples provided.
hnsearch__search hnsearch search ~107
hn.algolia.com: Search stories/comments by relevance Returns title, points, num_comments, author, created_at, url, objectID by default. (Same as clify_run site=hnsearch command=search.)
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | keys to keep; "*" for all |
| hitsPerPage | number | – | – |
| limit | integer | – | – |
| page | number | – | – |
| query | string | yes | – |
| tags | string | – | default story |
No output schema declared.
No examples provided.
pypi__get-package pypi get-package ~119
pypi.org: Get a package's PyPI page for its latest version: name and version, summary, pip install command, project links and metadata sidebar, and README text. Returns name_version, summary, pip_command, sidebar, description by default. (Same as clify_run site=pypi command=get-package.)
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | keys to keep; "*" for all |
| limit | integer | – | – |
| name | string | yes | Package name as it appears on PyPI, e.g. requests |
No output schema declared.
No examples provided.
wikipedia__summary wikipedia summary ~96
en.wikipedia.org: Short summary of an article (title, description, extract, url) Returns title, description, extract, content_urls.desktop.page by default. (Same as clify_run site=wikipedia command=summary.)
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | keys to keep; "*" for all |
| limit | integer | – | – |
| title | string | yes | article title, spaces as underscores, e.g. Y_Combinator |
No output schema declared.
No examples provided.
How do I install the app.netlify.clify-dev/clify MCP server?
app.netlify.clify-dev/clify is a hosted endpoint at https://bold-cloud-h4u6s.run.mcp-use.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 · bold-cloud-h4u6s.run.mcp-use.com
claude mcp add --transport http app-netlify-clify-dev-clify 'https://bold-cloud-h4u6s.run.mcp-use.com/mcp'
What is the app.netlify.clify-dev/clify MCP server?
app.netlify.clify-dev/clify is an MCP server listed in the public MCP registry as app.netlify.clify-dev/clify. Verified websites as JSON commands for AI agents over plain curl or MCP. This page covers its hosted endpoint (https://bold-cloud-h4u6s.run.mcp-use.com/mcp).
Is the app.netlify.clify-dev/clify MCP server safe to use?
app.netlify.clify-dev/clify scores 67 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 app.netlify.clify-dev/clify MCP server expose?
app.netlify.clify-dev/clify exposes 7 tools: clify_sites, clify_help, clify_run, crates__get-crate, pypi__get-package, and 2 more. Their descriptions and schemas cost roughly 827 tokens of context every time the server is loaded.
Does the app.netlify.clify-dev/clify MCP server require authentication?
No. We connected to app.netlify.clify-dev/clify without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the app.netlify.clify-dev/clify MCP server still maintained?
app.netlify.clify-dev/clify is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.