si.mttr/mttr · v1.0.0 · marketing-and-seo
mttr is healthy: it completed an MCP handshake in 959 ms and exposes 62 tools.
Reads a site as search engines and AI assistants do, ranks its fixes, and checks them live.
Endpoint: https://mttr.si/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 62 |
| Latency | 959 ms |
| Last checked (UTC) | 2026-10-24T23:45:08.023Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-24T23:45:08.023Z | Healthy | 959 |
mttr_sites | Lists the sites mttr has read, each with its latest score, page count and the rule to fix first. |
mttr_site | One site as its latest run found it: the score and its letter `grade`, the four stages with theirs (`grades`), its `rank` among every ranked site ({place, of}), the towns it serves (`served`, from its structured data, its town pages and its own place), and every fix in order with each page that fail |
mttr_brief | The fix list for a site as Markdown, written to be acted on: what to fix, in what order, how, why, and on which pages. Start here. |
mttr_plan | The plan for a site: the fixes worth the most as ordered steps, each with what to do, a few of its pages and the points it is worth, and the words to hand an agent to work through them. |
mttr_pages | The pages of a site from its latest run, with status, depth, words and the rules each fails. Can be narrowed to the pages failing one rule. |
mttr_page | One page of a site: what it says about itself, the rules it fails with the fix for each, and the pages that link to it and that it links to. |
mttr_product_check | Checks one live product page's structured data the way the free schema checker does: each Product, ProductGroup and Offer field by field against the fields Google lists for merchant listings (name, image, offers, price above zero, priceCurrency in ISO 4217, availability, shipping, returns, brand, GT |
mttr_agent_view | Reads one live page the way an agent does, the free "What an agent reads" tool: robots.txt asked first, so a page closed to mttr is not fetched; then its main content as Markdown with words and an estimated token count (about 4 characters a token), and what helped or hurt the reading, each with a st |
mttr_schema_create | Makes JSON-LD for one page from the fields given, as the free schema creator does, and fetches nothing. Types: LocalBusiness, Organization, Product, Article, BreadcrumbList, Service, Event, WebSite, each with the fields Google's own structured data pages mark required or recommended (Service has no |
mttr_x_card | Tests one live link's X card, the free X card tester: robots.txt asked first, so a page closed to mttr is not fetched; then its twitter: tags against what X's archived card docs list (one twitter:card, the site, title, image and its size, and for a player card an https twitter:player with its width |
mttr_locations | Grades a brand's location pages together, the free multi-location grader: robots.txt asked first, so a site closed to mttr is not read; then its home page and sitemap, and up to 25 location pages, state and city listings followed down to the places and subpages every location has left out. Eight che |
mttr_ssl_check | Checks one public host's SSL certificate, the free SSL certificate checker: one TLS handshake on port 443 with the name sent as SNI and nothing sent but the handshake. Whether the certificate is valid for the name, who issued it, valid from and until with the days left (a warning under 30, a failure |
mttr_changes | What the latest run of a site changed against the run before it: the score, rules now passing, rules newly failing, and pages added and removed. Call it after a rescan is done. For a site whose server sends its own counts, "visits" sets people, people an assistant sent and crawler fetches in the wee |
mttr_rescan | Asks mttr to read a site again, after it has been changed. Returns a job to watch with mttr_job. A site is read at most once every ten minutes. |
mttr_citations | What assistants were found to cite for a site, question by question, from lookups already made, and the credits left for more. Costs nothing. |
mttr_cite | Asks ChatGPT, Gemini and Perplexity one question with web search on, and says whether each cites the site, where, whether it names it without citing it, and who it cites instead. Paid in mttr credits; mttr_citations shows the price and the balance first. Only the assistants mttr is connected to are |
mttr_signup | Signs the person up with their email, the one call that works before mttr has a key for them. It answers their key, shown once, and the command that connects with it. Connect again with the key: it reads any public site’s report at once, and claiming their site with mttr_claim adds its private parts |
mttr_claim | Starts claiming a site for the person: the TXT record or the file that proves they control it. Put either one up, then call mttr_claim_check. A claimed site joins their account: its Search Console figures, visits, citations and rivals, their work board and their progress page. Any key reads a site’s |
mttr_claim_check | Checks the record or file from mttr_claim and, once it is found, adds the site to the person's account. A new DNS record can take a few minutes to be seen. |
mttr_list | Names a site the person has claimed on the public leaderboard, with a link to its report, or with show false takes its name off again so it goes by an anonymous code. Only a claimed site can be named. |
mttr_log_work | Tells mttr what you did on a site, after each step: what you planned, changed, checked, or where you got stuck, what you found along the way, the files you touched and the rules you worked on. It shows on your person’s progress page, and mttr reads these to get better. Never send secrets or a site’s |
mttr_approvals_set | Sets how you work on one of the person's claimed sites: automatic, where you deploy each change as you go, or approve, where you propose each change with mttr_propose and deploy it only once the person approves. Turning approve off is emailed to the person. mttr_proposals({ site }) says which a site |
mttr_propose | Before you deploy a change to a site set to approve, proposes it to the person: mttr keeps it and emails them what the change is, the rule and pages, your summary marked as your words, and an Approve and a Decline link, each working once and lapsing after 72 hours. Then wait: call mttr_proposal with |
mttr_proposal | Where one proposal stands: pending, approved, declined or expired, with "deploy" true only once the person approved it, and their reason when they declined. Poll it every few minutes after mttr_propose; deploy only when it says approved. |
mttr_proposals | The person's proposals, newest first, each with where it stands, for one site or all of them. With a site, it also says whether that site is set to approve or automatic: check it before you start work on a site. |
mttr_todo | The person's work across their sites, as their progress page shows it: the next fix to make, with the words to work from, then every other fix by worth, what slipped back, what a read has checked fixed, and sites changed since their last read that need reading again. A fix counts as done only once a |
mttr_content_brain | A claimed site's content brain as files to save under .mttr/brain/ in its repository: what the business does and where, how its pages read, the facts its structured data states, what is worth writing, and every brief so far. Read it before writing any page. |
mttr_content_next | The brief for the page most worth writing next on a claimed site: the question, why, the kind of page and its path, the facts to use, the voice, and the rules it will be held to. mttr does not write the page; you or your person do. At most three briefs are open at once. When the page is live, call m |
mttr_content_done | Says where a content brief's page went on the site, by the brief's id from mttr_content_next and the page's path. The brief goes live when a later read finds that page, and keeps where the site stood then. Ask for a read with mttr_rescan after. |
mttr_content_drop | Drops one of your open content briefs for a site, by its id, freeing its place among the three open at once. A dropped brief is never handed out again. |
mttr_content_posts | Briefs for posts about a page that went live from one of your content briefs: for X and for LinkedIn, the point of the page, one fact of the site's own that carries it, the link, the voice, and the characters left (X counts a link as 23). mttr writes no post and posts nothing; you or your person wri |
mttr_queue | What the person queued for you from their mttr, oldest first: each task with its id, its site, and the words to work from. Check it when you start, and whenever an answer says tasks are waiting. |
mttr_queue_done | Says a queued task is done, by its id from mttr_queue. The fix itself counts only once a later read finds it passing, so ask for a fresh read with mttr_rescan. |
mttr_progress_link | A private link to the person's progress page: their sites, every read, what each changed, and what this agent has asked. Signed with this key; it lapses after the days asked (30 if none, 90 at most) or when the key is rotated. Hand it only to the person. |
mttr_portfolio | The person's portfolio, private to them: one score across every site they have claimed, half for what was improved while they held each site, three tenths for where the sites stand now, and a fifth for search traffic, not counted yet. Every site by its real name with what it gives each part and why, |
mttr_portfolio_set | Changes the person's portfolio: publish or hide it, a display name (shown as chosen by its holder, not checked; null clears it), a home site that says who is behind it (one of their sites proved by DNS or a file), or whether one site is named on it or goes by its code. A site is named only where its |
mttr_portfolio_veto | For the owner of a site: takes it out of every portfolio but their own, at once, or with out false puts it back. Needs the site proved with this key by DNS or a file. To keep a site in portfolios but take its name off, call mttr_list with show false. |
mttr_job | How a rescan stands: waiting, running, done or failed, and how many reads are ahead of it. |
mttr_events | The newest things that happened: reads asked for, finished and failed, scores that moved, rules that were fixed. |
mttr_crawls | The crawl as it stands: the sites being read now, the next in line, and how the reads that ended over the last 1, 7 or 30 days ended. |
mttr_links | The links of a site from its latest run: broken ones by default, or all, those in page content, or the other sites linked to. Link text read from the site comes under "quoted". |
mttr_topics | What a site covers: its subjects and the pages under each, pages competing for the same search, and places a subject is missing from. A model named the subjects, so names come under "quoted". |
mttr_structure | How a site is put together: its sections, how many clicks each sits from the home page, how much of each is linked from page content, and the links between sections. |
mttr_map | Every page of a site's latest read, one of three ways. tree: by address, folders as branches, each page with its state, failing rules, clicks from home and words. links: each page reached from home with its clicks and its first way in, the hubs, and the pages no link leads to (none named when the re |
mttr_compare | Two sites already read, rule by rule: the scores and stages side by side, and the rules each is ahead or behind on by the share of its pages passing. With view "content", their content by meaning instead: their pages measured, page pairs both write about with words on each, and what only one of them |
mttr_reviews | Verdicts a model could not be relied on for, which wait for a person and count neither for nor against a score. Only sites with something waiting, a screen at a time, newest read first, with the total across every site. What the model recorded comes under "quotedDetail". |
mttr_rules | The rulebook: every rule mttr checks, with its stage, its weight and how to fix a failure. |
mttr_similar | Pages of a site that mean nearly the same thing, grouped, which may compete for one search. With a path, the pages nearest that page, each with the two passages that come closest. Read from vectors of the page text, so the site must have been embedded. Passages come under "quoted". |
mttr_near | The sites closest in meaning to one site, closest first: the ones writing about the same work, which are its likeliest rivals. Read from one vector a site kept in the catalog, so both sites must have been embedded. |
mttr_leaderboard | The public leaderboard: every ranked site by the score of its latest read, places shared on a tie, or the board of one crowd: a line of work with "in", a state, a city in that state, a size, or any of them together, each place counted as a site's report counts it. Each with its stages, pages read an |
mttr_explore | One thing mttr knows and every way on from it, each edge marked by what made it: meaning (close in meaning, never better or cited), links (pages linking between sites, or between pages of one site, with their anchor text) or rules (code checking pages against the rulebook). Across sites: a site, a m |
mttr_markets | The markets last found: groups of sites close in meaning, each named by the site at its centre, largest first. A site in a market is writing about the same work as the others in it. |
mttr_search | Ask a question, such as a buyer would, and get the passages that answer it best, and each site once by its best passage under "bySite", from the sites closest to the question, one market, or named sites. At most 12 sites are read. Passages come under "quoted". Close means similar in meaning, not rig |
mttr_examples | How other sites pass a page rule a page fails: pages on sites in the same market, or the nearest sites, that pass the rule and are closest to the page in meaning, each with the passage that comes closest. Worked examples for writing the fix. Passages come under "quoted". |
mttr_market | A site set against its market, or its nearest sites when it has none: its place by score, the median score, and for every rule the share of pages passing here against the market median and the best site, with the rules furthest behind first. |
mttr_gaps | Content gaps: subjects a site’s rivals write about that nothing on the site comes close to in meaning, the one most rivals cover first, each with the rival pages and the nearest page here. Page titles come under "quoted". |
mttr_tells | The signs of generated text on a site's pages: hidden characters that can carry a watermark or hidden instructions (with any message spelled out in tag characters), chat and markdown left in, placeholders never filled in, stock phrasing, and heavy use of dashes. Strong signs first. A sign is not pro |
mttr_competitors | A site's competitors: where it is (from the address or phone numbers on its own pages), the sites near it that do similar work by meaning, everyone near it, and sites doing similar work elsewhere, each with score, pages, and how many sites read link to it, against the site's own. |
mttr_backlinks | The sites mttr has read that link to a site, the most pages first, with how many sites were counted. Links from sites mttr has not read are not known. |
mttr_traffic | Clicks from Google search, from Search Console. With no site, every site read from Search Console with its clicks and impressions against as many days before, and the searches nothing on two or more of the sites answers, grouped by subject. With a site: clicks by day, the totals against as many days |
mttr_visits | Who fetched a site's pages in the last 28 days against the 28 before, counted by the site's own server: people, people an assistant such as ChatGPT or Perplexity sent, and crawlers by name, AI crawlers marked. By day, by crawler, by assistant and by page, with the last day an AI crawler fetched each |
mttr_queries | The searches Google showed a site's pages for, from Search Console, with clicks, impressions and average place: by query, by page, or only those close to the top (places 4 to 20). Only sites whose owner added mttr in Search Console have any. Queries come under "quoted". |