MCP servers › com.clickd › clickd
MCP server · registry snapshot 2026-11-01 · last tested 2026-11-01
com.clickd/clickd
by clickd.com · domain (the registry's namespace rule)Website ↗
Reads a site as search engines and AI assistants do, ranks its fixes, and checks them live. — the publisher's description
Summary
com.clickd/clickd is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain clickd.com. On 2026-11-01 ProtocolProbe connected to it in read-only mode and read its inventory: 17 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Operate this server? Correct a fact · README badge · Run the checks yourself
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 17
- Last tested
- 2026-11-01
Tool list size
6,919 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (17 tools). Counted with Anthropic's token counter on 2026-11-01, from the tool list we read on 2026-11-01. Median across 25,738 counted servers: 2,858 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-01 (clickd.com), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.0.0).
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-01
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.0, published 2026-11-01 (registry, as of the 2026-11-01 snapshot)
- First listed version
- 2026-11-01 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-11-01
- Package and repository
- checked 2026-11-01
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-10-31, listed on 2026-11-01 with version 1.0.0 (published 2026-11-01).
Source: the official MCP Registry list on 2026-10-31 and on 2026-11-01.
What it is
What does this server offer?
Observed inventoryNone of its 17 tools are described as changing anything. For 17 the reading was uncertain, so no mark is shown.
- clickd_site
“Gets a site's report from its latest read: score, grades, place among ranked sites, towns served, and every fix with its failing pages.”
Publisher declares: read-only yes · open-world no
2 inputs, 1 required
sitestringrequired“The site, as a domain such as example.com.”viewstring“report (the default) or agent.”
- clickd_brief
“Gets a site's fixes as a work order: what to fix, in what order, how, why and on which pages.”
Publisher declares: read-only yes · open-world no
2 inputs, 1 required
sitestringrequired“The site, as a domain such as example.com.”formatstring“markdown (the default) or steps.”
- clickd_pages
“Lists the pages of a site's latest read with status, depth, words and failing rules, or gives one page in full.”
Publisher declares: read-only yes · open-world no
10 inputs, 1 required
sitestringrequired“The site, as a domain such as example.com.”pathstring“One page, such as /pricing.”failingstring“A rule id.”qstring“Text in the path.”kindstring“A kind of page.”sectionstring“A section, such as /guides.”sortstring“What to sort by.”dirstring“Which way.”limitnumber“How many to return.”offsetnumber“How many to skip, for the next part of a long list.”
- clickd_rescan
“Puts a fresh read of a site in line and returns a job to follow.”
Publisher declares: read-only no · destructive no · open-world yes
2 inputs, 1 required
sitestringrequired“The site, as a domain such as example.com.”reasonstring“What was changed, in a few words.”
- clickd_changes
“Says what a site's latest read changed against the one before: score, rules fixed and newly failing, pages added and removed.”
Publisher declares: read-only yes · open-world no
2 inputs, 1 required
sitestringrequired“The site, as a domain such as example.com.”jobnumber“The job id that clickd_rescan returned.”
- clickd_rivals
“Sets a site against its rivals from kept reads: who they are, how close, and where it is behind.”
Publisher declares: read-only yes · open-world no
4 inputs, 1 required
sitestringrequired“The site, as a domain such as example.com.”viewstring“competitors (the default), near, market, rules or content.”withstring“The other site, already read.”limitnumber“For near only: how many sites.”
- clickd_citations
“Lists what assistants were found to cite for a site, question by question, from lookups already made, and the credits left.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
sitestringrequired“The site, as a domain such as example.com.”
- clickd_claim
“Claims a site for the person: the TXT record or file that proves it is theirs, then the check that finds it.”
Publisher declares: read-only no · destructive no · open-world yes
2 inputs, 1 required
sitestringrequired“The site, as a domain such as example.com.”stepstring“start (the default) or check.”
- clickd_propose
“Proposes a change before you deploy it, emailing the person Approve and Decline links that lapse in 72 hours.”
Publisher declares: read-only no · destructive no · open-world no
6 inputs, 3 required
sitestringrequired“The site, as a domain such as example.com.”titlestringrequired“The change in a few words, at most 120 characters.”summarystringrequired“What it does and why, at most 2000 characters.”rulestring“The rule id it answers, such as answer-first.”pagesstring“Paths separated by commas, at most 20; none for the whole site.”diffstring“A unified diff, at most 20,000 characters.”
- clickd_proposals
“Lists the person's proposals and where each stands, or one by id, and whether a site is set to approve or automatic.”
Publisher declares: read-only yes · open-world no
2 inputs
idnumber“One proposal, by the id clickd_propose returned.”sitestring“Only proposals for this site, and its mode.”
- clickd_log_work
“Records a step of work on a site: what you planned, changed or checked, or where you got stuck.”
Publisher declares: read-only no · destructive no · open-world no
8 inputs, 3 required
sitestringrequired“The site, as a domain such as example.com.”stepstringrequired“Which step this was.”didstringrequired“What was done, in a sentence or two.”foundstring“What was true of the site, such as of its code.”filesstring“The files touched, separated by commas.”rulesstring“The clickd rules worked on, by id, separated by commas.”proposalnumber“The proposal id, from clickd_propose, this step carried out.”tasknumber“The queued task id this step finished.”
- clickd_todo
“Gets the person's work across all their sites: the next fix and every other by worth, or the tasks they queued for you.”
Publisher declares: read-only yes · open-world no
1 input
showstring“board (the default) or queue.”
Show 5 more tools
- clickd_rules
“Lists the rulebook: every rule clickd checks, with its id, stage, weight and fix.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
- clickd_leaderboard
“Lists the public leaderboard: every ranked site by its latest score, the board of one crowd, or a record.”
Publisher declares: read-only yes · open-world no
7 inputs
instring“A line of work, such as trades.”statestring“A US state by two letters, such as MO.”citystring“A city in that state, such as Dallas.”sizestring“By the pages a read took.”recordstring“One record in place of the places.”limitnumber“How many to return.”offsetnumber“How many to skip, for the next part of a long list.”
- clickd_signup
“Gets a free key, shown once, with the command to connect with it: the person's by email, or a throwaway one.”
Publisher declares: read-only no · destructive no · open-world no
1 input
emailstring“The person's email address.”
- clickd_check
“Checks one live address now, as the free tools do: product data, a page as an agent reads it, an X card, a certificate, or location pages.”
Publisher declares: read-only yes · open-world yes
2 inputs, 2 required
kindstringrequired“Which check.”urlstringrequired“The address to check, such as https://example.com/products/linen-shirt.”
- clickd_schema_create
“Makes JSON-LD for one page from the fields given, ready to paste, and fetches nothing.”
Publisher declares: read-only yes · open-world no
3 inputs, 1 required
typestringrequired“The schema type to make.”asstring“A more exact type, for LocalBusiness (such as Plumber, RoofingContractor, Restaurant) or Article (BlogPosting, NewsArticle).”fieldsobject“Values by field key, as text, such as { "name": "Acme Plumbing" }.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-01.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 100% of 55
- Tools with a description
- 100% of 17
- Typical description length
- 637 characters
The tool set
Counted from the listing
- Tools
- 17
- Size of the list
- about 4,988 tokens for an agent to load (characters ÷ 4)
- Naming
- 17 of 17 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 17 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-01 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://clickd.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"clickd": {
"url": "https://clickd.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"clickd": {
"type": "http",
"url": "https://clickd.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"clickd","type":"http","url":"https://clickd.com/mcp"}'Claude Code
claude mcp add --transport http clickd https://clickd.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"clickd": {
"type": "streamableHttp",
"url": "https://clickd.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"clickd": {
"httpUrl": "https://clickd.com/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.clickd] url = "https://clickd.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"clickd": {
"url": "https://clickd.com/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://clickd.com/mcp --transport http
- Optional settings the entry also lists (left out above): Authorization.
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint clickd.com/mcp | Session opened | matches | our test · 2026-11-01 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-01 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-01. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about com.clickd/clickd
Answered from the data aboveWho publishes com.clickd/clickd?
The registry ties the namespace com.clickd to the domain clickd.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does com.clickd/clickd need an API key or sign-in?
It opened a session without any credential on 2026-11-01. The registry entry declares no required credential; no declaration is not a guarantee.
Has com.clickd/clickd been security tested?
Partly. 3 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
3 exercised12 not run (reason given)3 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-11-01, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,915 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 17 tools, 0 resources, 0 prompts.
- 4,985 msFinished: 3 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “com.clickd/clickd: MCP server record.” Data checked 2026-11-01. https://protocolprobe.com/mcp/servers/com.clickd/clickd
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/com.clickd/clickd)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology