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.

clickd

REMOTE · CLICKD.COM

Reads a site as search engines and AI assistants do, ranks its fixes, and checks them live.

Available components

67 Trust /100

Last scanned (10 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

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 Security74
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4297 tokens (~252/item across 17 items; 17 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 Management0
  • Stability check failed: schema churn in the 4 days we've observed: 62 tool removals, 0 breaking changes, 0 auth/transport breaks, 17 additions. See how to fix → Fail
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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 2 Nov 26 +6
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • Tool “mttr_agent_view” was removed ▼ security
    • Tool “mttr_approvals_set” was removed ▼ security
    • Tool “mttr_backlinks” was removed ▼ security
    • Tool “mttr_brief” was removed ▼ security
    • Tool “mttr_changes” was removed ▼ security
    • Tool “mttr_citations” was removed ▼ security
    • Tool “mttr_cite” was removed ▼ security
    • Tool “mttr_claim” was removed ▼ security
    • Tool “mttr_claim_check” was removed ▼ security
    • Tool “mttr_compare” was removed ▼ security
    • Tool “mttr_competitors” was removed ▼ security
    • Tool “mttr_content_brain” was removed ▼ security
    • Tool “mttr_content_done” was removed ▼ security
    • Tool “mttr_content_drop” was removed ▼ security
    • Tool “mttr_content_next” was removed ▼ security
    • Tool “mttr_content_posts” was removed ▼ security
    • Tool “mttr_crawls” was removed ▼ security
    • Tool “mttr_events” was removed ▼ security
    • Tool “mttr_examples” was removed ▼ security
    • Tool “mttr_explore” was removed ▼ security
    • Tool “mttr_gaps” was removed ▼ security
    • Tool “mttr_job” was removed ▼ security
    • Tool “mttr_leaderboard” was removed ▼ security
    • Tool “mttr_links” was removed ▼ security
    • Tool “mttr_list” was removed ▼ security
    • Tool “mttr_locations” was removed ▼ security
    • Tool “mttr_log_work” was removed ▼ security
    • Tool “mttr_map” was removed ▼ security
    • Tool “mttr_market” was removed ▼ security
    • Tool “mttr_markets” was removed ▼ security
    • Tool “mttr_near” was removed ▼ security
    • Tool “mttr_page” was removed ▼ security
    • Tool “mttr_pages” was removed ▼ security
    • Tool “mttr_plan” was removed ▼ security
    • Tool “mttr_portfolio” was removed ▼ security
    • Tool “mttr_portfolio_set” was removed ▼ security
    • Tool “mttr_portfolio_veto” was removed ▼ security
    • Tool “mttr_product_check” was removed ▼ security
    • Tool “mttr_progress_link” was removed ▼ security
    • Tool “mttr_proposal” was removed ▼ security
    • Tool “mttr_proposals” was removed ▼ security
    • Tool “mttr_propose” was removed ▼ security
    • Tool “mttr_queries” was removed ▼ security
    • Tool “mttr_queue” was removed ▼ security
    • Tool “mttr_queue_done” was removed ▼ security
    • Tool “mttr_rescan” was removed ▼ security
    • Tool “mttr_reviews” was removed ▼ security
    • Tool “mttr_rules” was removed ▼ security
    • Tool “mttr_schema_create” was removed ▼ security
    • Tool “mttr_search” was removed ▼ security
    • Tool “mttr_signup” was removed ▼ security
    • Tool “mttr_similar” was removed ▼ security
    • Tool “mttr_site” was removed ▼ security
    • Tool “mttr_sites” was removed ▼ security
    • Tool “mttr_ssl_check” was removed ▼ security
    • Tool “mttr_structure” was removed ▼ security
    • Tool “mttr_tells” was removed ▼ security
    • Tool “mttr_todo” was removed ▼ security
    • Tool “mttr_topics” was removed ▼ security
    • Tool “mttr_traffic” was removed ▼ security
    • Tool “mttr_visits” was removed ▼ security
    • Tool “mttr_x_card” was removed ▼ security
    • Authorization: fail → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 133 → 252 ▼ functional
    • Schema quality: good → excellent functional
    • Destructive annotations: 100 → pass functional
    • New tool “clickd_brief” functional
    • New tool “clickd_changes” functional
    • New tool “clickd_check” functional
    • New tool “clickd_citations” functional
    • New tool “clickd_claim” functional
    • New tool “clickd_leaderboard” functional
    • New tool “clickd_log_work” functional
    • New tool “clickd_pages” functional
    • New tool “clickd_proposals” functional
    • New tool “clickd_propose” functional
    • New tool “clickd_rescan” functional
    • New tool “clickd_rivals” functional
    • New tool “clickd_rules” functional
    • New tool “clickd_schema_create” functional
    • New tool “clickd_signup” functional
    • New tool “clickd_site” functional
    • New tool “clickd_todo” functional
  • 1 Nov 26 61

    First indexed and scored.

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://clickd.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=clickd.com CN=WE1,O=Google Trust Services,C=US 29 Sept 2026 28 Dec 2026 ECDSA 256 ECDSA-SHA256 53f25985feebb9240e7f726bb5ba202f
SANs: clickd.com, *.clickd.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 insecure

Validation of clickd.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
clickd.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
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://clickd.com/mcp Verified 200
http (plaintext) http://clickd.com/mcp HTTPS enforced 301 https://clickd.com/mcp
MCP tools · 17 exposed · ~3,740 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
clickd_brief ~215

Gets a site's fixes as a work order: what to fix, in what order, how, why and on which pages. When: at the start of work on a site, and after clickd_changes says a read is done. Instead: clickd_site for the score to tell a person; clickd_todo for the next fix across all the person's sites. Inputs: `site` is a domain, like example.com. `format` is markdown (the default), the whole list, or steps: the four fixes worth the most as steps with pages and points, and words to hand another agent. Returns: with markdown, the Markdown text alone; with steps, JSON with steps, prompt, report and caveat. Fails: a site never read, or a draft, answers not found; clickd_rescan reads it. Works with no key.

NameTypeReqDescription
formatstring–markdown (the default) or steps.
sitestringyesThe site, as a domain such as example.com.

No output schema declared.

No examples provided.

clickd_changes ~216

Says what a site's latest read changed against the one before: score, rules fixed and newly failing, pages added and removed. When: after clickd_rescan, every minute or two with its job until the read is done. Instead: clickd_rescan to ask for the read; clickd_site for the report as it now stands. Inputs: `site` is a domain, like example.com. `job` is the id clickd_rescan returned: the reply then says where that read stands, with changes only once it is done. Returns: host, run, changes (null for a first read) and visits; with job, job ({ id, state, ahead }), changes null until done. Fails: a site never read, or a job for another site, answers not found; a failed read says so in job. Needs a key.

NameTypeReqDescription
jobnumber–The job id that clickd_rescan returned.
sitestringyesThe site, as a domain such as example.com.

No output schema declared.

No examples provided.

clickd_check ~209

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. When: before and after a fix to one page, link or host. Instead: clickd_rescan and clickd_changes for every page of a site; clickd_pages for a page as last read. Inputs: `kind` is product, agent, x_card, ssl or locations. `url` is the page's full address; for ssl, only its host is used; for locations, the brand's site. Returns: the findings, each with its state in a word and what to do when it is wrong. Fails: a private address is refused, and robots.txt is obeyed; the free tools' hourly allowance applies. Works with no key.

NameTypeReqDescription
kindstringyesWhich check.
urlstringyesThe address to check, such as https://example.com/products/linen-shirt.

No output schema declared.

No examples provided.

clickd_citations ~136

Lists what assistants were found to cite for a site, question by question, from lookups already made, and the credits left. When: to tell a person whether assistants cite their site, at no cost. Instead: clickd_site for how well formed the pages are, which is not whether they are cited. Inputs: `site` is a domain, like example.com. Returns: host, rows, credits, price, perDay and note. Fails: rows is empty until a lookup is made. Needs a key and a claim.

NameTypeReqDescription
sitestringyesThe site, as a domain such as example.com.

No output schema declared.

No examples provided.

clickd_claim ~197

Claims a site for the person: the TXT record or file that proves it is theirs, then the check that finds it. When: to open a site's private parts, such as rivals, citations and proposals. Instead: clickd_signup first for a key; clickd_site for a public report, which needs no claim. Inputs: `site` is a domain, like example.com. `step` is start (the default), for the record and file, or check, to look for either and add the site. Returns: with start, site, record, dns, file and note; with check, site, claimed and how. Fails: check before the proof is up answers claimed false; a new DNS record can take minutes to be seen. Needs a person's key.

NameTypeReqDescription
sitestringyesThe site, as a domain such as example.com.
stepstring–start (the default) or check.

No output schema declared.

No examples provided.

clickd_leaderboard ~292

Lists the public leaderboard: every ranked site by its latest score, the board of one crowd, or a record. When: to show a person where a site places among every site, or sites like it. Instead: clickd_site for one site's own place; clickd_rivals for the sites closest to one site. Inputs: `in` (a line of work such as trades), `state` (two letters), `city` (needs state) and `size` narrow the board, together or alone. `record` gives one record in place of the places. `limit` and `offset` page it. Returns: total, offset, limit, sites, tiers and note; with record, its sites and what it counted. Fails: a crowd too small answers an empty board; drafts and closed sites are not ranked. Works with no key.

NameTypeReqDescription
citystring–A city in that state, such as Dallas.
instring–A line of work, such as trades.
limitnumber–How many to return.
offsetnumber–How many to skip, for the next part of a long list.
recordstring–One record in place of the places.
sizestring–By the pages a read took.
statestring–A US state by two letters, such as MO.

No output schema declared.

No examples provided.

clickd_log_work ~315

Records a step of work on a site: what you planned, changed or checked, or where you got stuck. When: after each step, including one that carries out a proposal or a queued task. Instead: clickd_propose before deploying to a site set to approve; clickd_todo for tasks waiting. Inputs: `site` is a domain, like example.com. `step` is planned, changed, checked or stuck; `did` says what. `found`, `files` and `rules` (comma separated) add detail. `proposal` names the proposal carried out, `task` the queued task finished. Never send private data. Returns: kept, site, step and note, with proposal or task and left when given. Fails: a proposal or task not the person's keeps nothing and says so. Needs a person's key.

NameTypeReqDescription
didstringyesWhat was done, in a sentence or two.
filesstring–The files touched, separated by commas.
foundstring–What was true of the site, such as of its code.
proposalnumber–The proposal id, from clickd_propose, this step carried out.
rulesstring–The clickd rules worked on, by id, separated by commas.
sitestringyesThe site, as a domain such as example.com.
stepstringyesWhich step this was.
tasknumber–The queued task id this step finished.

No output schema declared.

No examples provided.

clickd_pages ~335

Lists the pages of a site's latest read with status, depth, words and failing rules, or gives one page in full. When: to find the pages behind a fix, or everything wrong with one page. Instead: clickd_brief for the fixes in order; clickd_check for a page as it is live now. Inputs: `site` is a domain, like example.com. `path`, such as /pricing, gives that page in full, and the rest is then ignored. `failing` (a rule id), `q`, `kind` and `section` narrow the list, `sort` and `dir` order it, `limit` and `offset` page it. Returns: host, run, total and pages; one page as path, status, failing, needsAPerson, linkedFrom, linksTo and quoted. Fails: a site or page not read answers not found. Needs a key; any key reads a public site.

NameTypeReqDescription
dirstring–Which way.
failingstring–A rule id.
kindstring–A kind of page.
limitnumber–How many to return.
offsetnumber–How many to skip, for the next part of a long list.
pathstring–One page, such as /pricing.
qstring–Text in the path.
sectionstring–A section, such as /guides.
sitestringyesThe site, as a domain such as example.com.
sortstring–What to sort by.

No output schema declared.

No examples provided.

clickd_proposals ~195

Lists the person's proposals and where each stands, or one by id, and whether a site is set to approve or automatic. When: before work on a claimed site, and every few minutes after clickd_propose until it is answered. Instead: clickd_propose to make one; clickd_todo for the work itself. Inputs: `id` is one proposal from clickd_propose; deploy only once it says approved. `site` gives that site's proposals and its mode. Neither, every proposal; never both. Returns: with id, proposal and promise; otherwise proposals and promise, and with site, site and mode. Fails: id and site together are refused; one not the person's answers not found. Needs a person's key.

NameTypeReqDescription
idnumber–One proposal, by the id clickd_propose returned.
sitestring–Only proposals for this site, and its mode.

No output schema declared.

No examples provided.

clickd_propose ~301

Proposes a change before you deploy it, emailing the person Approve and Decline links that lapse in 72 hours. When: before each deploy to a site clickd_proposals says is set to approve. Instead: clickd_proposals with the id to wait for the answer; clickd_log_work, naming it, once carried out. Inputs: `site` is a domain, like example.com. `title` is the change in a few words; `summary` what it does and why; `rule` the rule id it answers; `pages` the paths it changes, comma separated; `diff` a unified diff, shown and never applied. Returns: proposal ({ id, state, deploy, ... }), note and promise. Fails: a site not claimed with this key answers not found; 20 proposals a site an hour at most. Needs a person's key.

NameTypeReqDescription
diffstring–A unified diff, at most 20,000 characters.
pagesstring–Paths separated by commas, at most 20; none for the whole site.
rulestring–The rule id it answers, such as answer-first.
sitestringyesThe site, as a domain such as example.com.
summarystringyesWhat it does and why, at most 2000 characters.
titlestringyesThe change in a few words, at most 120 characters.

No output schema declared.

No examples provided.

clickd_rescan ~178

Puts a fresh read of a site in line and returns a job to follow. When: once a fix is deployed, or for a site clickd has never read. Instead: clickd_changes with the job to see what the read changed; clickd_check for one live page with no read. Inputs: `site` is a domain, like example.com. `reason` says what was changed, in a few words. Returns: job, added (false when a read was already in line), allowedAt and ahead. Fails: a site read in the last ten minutes answers allowedAt, when to ask again; a private address is refused. Needs a key.

NameTypeReqDescription
reasonstring–What was changed, in a few words.
sitestringyesThe site, as a domain such as example.com.

No output schema declared.

No examples provided.

clickd_rivals ~278

Sets a site against its rivals from kept reads: who they are, how close, and where it is behind. When: to pick the fixes that matter against the sites a buyer compares it with. Instead: clickd_leaderboard for places among every site; clickd_site for its own score. Inputs: `site` is a domain, like example.com. `view` is competitors (default: rivals doing similar work), near (closest in meaning), market (rule by rule), or rules or content (two sites side by side). `with` is the other site, for rules or content; alone, it means rules. `limit` is for near, 10 if left out. Returns: host, then by view: local, nearby and elsewhere; sites; rules; ahead and behind; or pages. Fails: a site with no meaning yet answers found or embedded false; rules or content with no with says to give it. Needs a key and a claim.

NameTypeReqDescription
limitnumber–For near only: how many sites. 10 if left out.
sitestringyesThe site, as a domain such as example.com.
viewstring–competitors (the default), near, market, rules or content.
withstring–The other site, already read.

No output schema declared.

No examples provided.

clickd_rules ~103

Lists the rulebook: every rule clickd checks, with its id, stage, weight and fix. When: to explain a fix to a person, or to find a rule's id. Instead: clickd_brief for the rules one site fails; clickd_pages with failing for the pages failing one. Inputs: none. Returns: rules, each with id, title, stage, weight and fix. Fails: nothing to refuse. Works with no key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

clickd_schema_create ~227

Makes JSON-LD for one page from the fields given, ready to paste, and fetches nothing. When: to write the structured data a fix asks for; call it with only type to see the fields. Instead: clickd_check with kind product to check a live product page. Inputs: `type` is one of the types offered; `as` a more exact one, such as Plumber; `fields` the values by field key, as text. Give only what the page shows. Returns: jsonld, script (ready to paste), missing, problems, recommended and fields. Fails: a type not offered says which are. Works with no key.

NameTypeReqDescription
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" }. A list is one value a line.
typestringyesThe schema type to make.

No output schema declared.

No examples provided.

clickd_signup ~157

Gets a free key, shown once, with the command to connect with it: the person's by email, or a throwaway one. When: when a call needs a key and there is none. Instead: clickd_claim, with a person's key, to make a site theirs. Inputs: `email` is the person's own address; leave it out for a throwaway key, which reads and asks for a few reads an hour. Returns: key, connect and next, with email or anonymous. Fails: an email already signed up, or not an email, says so; three an hour from one address. Needs no key.

NameTypeReqDescription
emailstring–The person's email address. Leave it out for a throwaway key.

No output schema declared.

No examples provided.

clickd_site ~213

Gets a site's report from its latest read: score, grades, place among ranked sites, towns served, and every fix with its failing pages. When: to tell a person how a site stands. Instead: clickd_brief for the fixes as a work order; clickd_rivals for its rivals; clickd_check for one live page. Inputs: `site` is a domain, like example.com. `view` is report (the default) or agent: the whole-site Agent View from the same read, with each AI crawler as robots.txt treats it. Returns: host, score, grade, stages, grades, rank, served, fixes and card, a picture to send the person; with agent, the Agent View's figures. Fails: a site never read, a draft or one kept unnamed answers not found. Works with no key.

NameTypeReqDescription
sitestringyesThe site, as a domain such as example.com.
viewstring–report (the default) or agent.

No output schema declared.

No examples provided.

clickd_todo ~173

Gets the person's work across all their sites: the next fix and every other by worth, or the tasks they queued for you. When: when you start work for the person, and when a reply says tasks are waiting. Instead: clickd_brief for every fix on one site; clickd_log_work with task to finish a queued task. Inputs: `show` is board (the default): next, every fix by worth, what slipped and what is fixed; or queue: the person's tasks for you, oldest first. Returns: with board, next, todo, slipped, fixed, waiting and note; with queue, tasks and note. Fails: an account with no claimed site has an empty board. Needs a person's key.

NameTypeReqDescription
showstring–board (the default) or queue.

No output schema declared.

No examples provided.

Install

How do I install the clickd MCP server?

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

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

What is the clickd MCP server?

clickd is an MCP server listed in the public MCP registry as com.clickd/clickd. Reads a site as search engines and AI assistants do, ranks its fixes, and checks them live. This page covers its hosted endpoint (https://clickd.com/mcp).

Is the clickd MCP server safe to use?

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

clickd exposes 17 tools: clickd_site, clickd_brief, clickd_pages, clickd_rescan, clickd_changes, and 12 more. Their descriptions and schemas cost roughly 3,740 tokens of context every time the server is loaded.

Does the clickd MCP server require authentication?

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

Is the clickd MCP server still maintained?

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