# mttr Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## mttr

Audits websites for search engine and AI readability, ranks fixes by impact, and checks improvements live.

- Record: https://musedirectory.ai/connector/mttr
- Category: Developer Tools
- Developer: mttr.si (https://mttr.si/agents)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 396ms, checked 2026-10-29T23:16:26Z
- Endpoint: https://mttr.si/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T23:16:26Z)
- Source: Found in the official MCP Registry (si.mttr/mttr) https://registry.modelcontextprotocol.io/v0/servers?search=si.mttr%2Fmttr

mttr reads websites as search engines and AI assistants do, identifies technical issues ranked by priority, and verifies fixes. Tools check structured data, SSL certificates, X cards, multi-location SEO, and track changes across rescans. Requires signup and API key.

Example request: "Show me the top fixes needed on my website to improve how Google and AI assistants read it."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use mttr to help me. It is a free service with an MCP server at https://mttr.si/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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
- 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
- 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 rea
- 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 recommen
- 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:pl
- 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
- 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
- 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 crawle
- 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 
- 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 ad
- 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. An
- 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
- 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 
- 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: cal
- 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
- 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 
- 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; yo
- 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 give
- 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 
- 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.

Screening checks:
- MCP handshake: pass (Answered in 396ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mttr.si not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (62 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)