mttr
REMOTE · MTTR.SI
Reads a site as search engines and AI assistants do, ranks its fixes, and checks them live.
Available components
Last scanned (23 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Marketing and SEO
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 11 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
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 +2
- Stability: 0.27 → 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 +1
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: mttr → clickd security
- Tool “mttr_agent_view” rewrote its description, which is the text the model reads security
- Tool “mttr_backlinks” rewrote its description, which is the text the model reads security
- Tool “mttr_cite” rewrote its description, which is the text the model reads security
- Tool “mttr_content_next” rewrote its description, which is the text the model reads security
- Tool “mttr_content_posts” rewrote its description, which is the text the model reads security
- Tool “mttr_explore” rewrote its description, which is the text the model reads security
- Tool “mttr_locations” rewrote its description, which is the text the model reads security
- Tool “mttr_log_work” rewrote its description, which is the text the model reads security
- Tool “mttr_propose” rewrote its description, which is the text the model reads security
- Tool “mttr_queries” rewrote its description, which is the text the model reads security
- Tool “mttr_queue” rewrote its description, which is the text the model reads security
- Tool “mttr_rescan” rewrote its description, which is the text the model reads security
- Tool “mttr_rules” rewrote its description, which is the text the model reads security
- Tool “mttr_signup” rewrote its description, which is the text the model reads security
- Tool “mttr_sites” rewrote its description, which is the text the model reads security
- Tool “mttr_traffic” rewrote its description, which is the text the model reads security
- Tool “mttr_visits” rewrote its description, which is the text the model reads security
- Tool “mttr_x_card” rewrote its description, which is the text the model reads security
- “mttr_log_work” reworded the description of “rules” cosmetic
- “mttr_propose” reworded the description of “diff” cosmetic
- “mttr_propose” reworded the description of “rule” cosmetic
- 31 Oct 26 0
- Tool “mttr_markets” rewrote its description, which is the text the model reads security
- “mttr_search” reworded the description of “market” cosmetic
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 61
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 4 Nov 2026 · Probed https://mttr.si/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mttr.si | CN=YE2,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6c74b21194b7856b2f6476749a1a3d6d3e2 |
| SANs: *.mttr.si, mttr.si | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 mttr.si. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| si. | present | 42378 | 13 | Verified |
| mttr.si. | 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://mttr.si/mcp | Verified | 200 | |
| http (plaintext) | http://mttr.si/mcp | HTTPS enforced | 301 | https://clickd.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 →
clickd_brief Get the fix list ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | markdown (the default) or steps. |
| site | string | yes | The site, as a domain such as example.com. |
No output schema declared.
No examples provided.
clickd_changes What changed between reads ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| job | number | – | The job id that clickd_rescan returned. |
| site | string | yes | The site, as a domain such as example.com. |
No output schema declared.
No examples provided.
clickd_check Check a live address ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which check. |
| url | string | yes | The address to check, such as https://example.com/products/linen-shirt. |
No output schema declared.
No examples provided.
clickd_citations List 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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | The site, as a domain such as example.com. |
No output schema declared.
No examples provided.
clickd_claim Claim a site ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | The site, as a domain such as example.com. |
| step | string | – | start (the default) or check. |
No output schema declared.
No examples provided.
clickd_leaderboard Get the 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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | A city in that state, such as Dallas. |
| in | string | – | A line of work, such as trades. |
| limit | number | – | How many to return. |
| offset | number | – | How many to skip, for the next part of a long list. |
| record | string | – | One record in place of the places. |
| size | string | – | By the pages a read took. |
| state | string | – | A US state by two letters, such as MO. |
No output schema declared.
No examples provided.
clickd_log_work Log work on a site ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| did | string | yes | What was done, in a sentence or two. |
| files | string | – | The files touched, separated by commas. |
| found | string | – | What was true of the site, such as of its code. |
| proposal | number | – | The proposal id, from clickd_propose, this step carried out. |
| rules | string | – | The clickd rules worked on, by id, separated by commas. |
| site | string | yes | The site, as a domain such as example.com. |
| step | string | yes | Which step this was. |
| task | number | – | The queued task id this step finished. |
No output schema declared.
No examples provided.
clickd_pages List a site's 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.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Which way. |
| failing | string | – | A rule id. |
| kind | string | – | A kind of page. |
| limit | number | – | How many to return. |
| offset | number | – | How many to skip, for the next part of a long list. |
| path | string | – | One page, such as /pricing. |
| q | string | – | Text in the path. |
| section | string | – | A section, such as /guides. |
| site | string | yes | The site, as a domain such as example.com. |
| sort | string | – | What to sort by. |
No output schema declared.
No examples provided.
clickd_proposals List 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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | – | One proposal, by the id clickd_propose returned. |
| site | string | – | Only proposals for this site, and its mode. |
No output schema declared.
No examples provided.
clickd_propose Propose a change ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| diff | string | – | A unified diff, at most 20,000 characters. |
| pages | string | – | Paths separated by commas, at most 20; none for the whole site. |
| rule | string | – | The rule id it answers, such as answer-first. |
| site | string | yes | The site, as a domain such as example.com. |
| summary | string | yes | What it does and why, at most 2000 characters. |
| title | string | yes | The change in a few words, at most 120 characters. |
No output schema declared.
No examples provided.
clickd_rescan Read a site again ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | What was changed, in a few words. |
| site | string | yes | The site, as a domain such as example.com. |
No output schema declared.
No examples provided.
clickd_rivals Compare a site with 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | For near only: how many sites. 10 if left out. |
| site | string | yes | The site, as a domain such as example.com. |
| view | string | – | competitors (the default), near, market, rules or content. |
| with | string | – | The other site, already read. |
No output schema declared.
No examples provided.
clickd_rules List the 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 Write structured data ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| as | string | – | A more exact type, for LocalBusiness (such as Plumber, RoofingContractor, Restaurant) or Article (BlogPosting, NewsArticle). |
| fields | object | – | Values by field key, as text, such as { "name": "Acme Plumbing" }. A list is one value a line. |
| type | string | yes | The schema type to make. |
No output schema declared.
No examples provided.
clickd_signup Get a free key ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The person's email address. Leave it out for a throwaway key. |
No output schema declared.
No examples provided.
clickd_site Get a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | The site, as a domain such as example.com. |
| view | string | – | report (the default) or agent. |
No output schema declared.
No examples provided.
clickd_todo Get the work board ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| show | string | – | board (the default) or queue. |
No output schema declared.
No examples provided.
How do I install the mttr MCP server?
mttr is a hosted endpoint at https://mttr.si/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 · mttr.si
claude mcp add --transport http si-mttr-mttr 'https://mttr.si/mcp'
What is the mttr MCP server?
mttr is an MCP server listed in the public MCP registry as si.mttr/mttr. Reads a site as search engines and AI assistants do, ranks its fixes, and checks them live. This page covers its hosted endpoint (https://mttr.si/mcp).
Is the mttr MCP server safe to use?
mttr 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 mttr MCP server expose?
mttr 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 mttr MCP server require authentication?
No. We connected to mttr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the mttr MCP server still maintained?
mttr is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.