Skip to content
ProtocolProbe
Explore

MCP servers › si.mttr › mttr

MCP server · registry snapshot 2026-10-26 · last tested 2026-10-26

si.mttr/mttr

by mttr.si · 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

1 of 2 record checks metRead-only · tools listed 2026-10-26version 1.0.0streamable HTTP62 tools

Summary

si.mttr/mttr is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain mttr.si. On 2026-10-26 ProtocolProbe connected to it in read-only mode and read its inventory: 62 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

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
62
Last tested
2026-10-26

Tool list size

14,748 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (62 tools). Counted with Anthropic's token counter on 2026-10-26, from the tool list we read on 2026-10-26. Median across 23,424 counted servers: 2,725 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-26 (mttr.si), 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).

Add to your client

Observed fact

This server accepted a session without any credential and lists 3 tools whose name or declaration suggests they change data (mttr_approvals_set, mttr_content_drop, mttr_portfolio_set). That is our reading of the names; we did not call them. Source: our connection, 2026-10-26.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-26
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-10-24 (registry, as of the 2026-10-26 snapshot)
First listed version
2026-10-24 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-26
Package and repository
checked 2026-10-26
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-24, listed on 2026-10-26 with version 1.0.0 (published 2026-10-24).

Source: the official MCP Registry list on 2026-10-24 and on 2026-10-26.

What it is

What does this server offer?

Observed inventory
62tools
0resources
0prompts

None of its 62 tools are described as changing anything. For 62 the reading was uncertain, so no mark is shown.

  • mttr_sites

    “Lists the sites mttr has read, each with its latest score, page count and the rule to fix first.”

    Publisher declares: read-only yes · open-world no

    6 inputs
    • qstring“Text the site name must contain.”
    • statestring“Only sites in this state.”
    • sortstring“What to sort by.”
    • dirstring“Which way to sort.”
    • limitnumber“How many to return.”
    • offsetnumber“How many to skip, for the next part of a long list.”
  • 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 it…”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • mttr_pages

    “The pages of a site from its latest run, with status, depth, words and the rules each fails.”

    Publisher declares: read-only yes · open-world no

    9 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • failingstring“A rule id.”
    • qstring“Text the path must contain.”
    • kindstring“Only pages of this kind.”
    • sectionstring“Only pages in this section, such as /guides.”
    • sortstring“What to sort by.”
    • dirstring“Which way to sort.”
    • limitnumber“How many to return.”
    • offsetnumber“How many to skip, for the next part of a long list.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 2 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • pathstringrequired“The page, as a path such as /guides/gravel.”
  • 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, i…”

    Publisher declares: read-only yes · open-world yes

    1 input, 1 required
    • urlstringrequired“The product page, as a full public address such as https://example.com/products/linen-shirt.”
  • 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 es…”

    Publisher declares: read-only yes · open-world yes

    2 inputs
    • urlstring“One page, as a full public address such as https://example.com/guides/a-page.”
    • sitestring“A whole site, as a domain such as example.com, from its latest read instead: the share of its pages an agent reads, how much of each is the page, where that st…”
  • mttr_schema_create

    “Makes JSON-LD for one page from the fields given, as the free schema creator does, 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“The values, by field key, as text: such as { "name": "Acme Plumbing", "city": "Phoenix", "telephone": "+1-602-555-0142" }.”
  • 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:car…”

    Publisher declares: read-only yes · open-world yes

    1 input, 1 required
    • urlstringrequired“The link to be posted, as a full public address such as https://example.com/in-post.”
  • 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, st…”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • urlstringrequired“The brand's site, such as example.com or https://example.com/.”
  • 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.”

    Publisher declares: read-only yes · open-world yes

    1 input, 1 required
    • hoststringrequired“The host to check, such as example.com or www.example.com.”
Show 50 more tools
  • 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.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • mttr_rescan

    “Asks mttr to read a site again, after it has been changed.”

    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.”
  • mttr_citations

    “What assistants were found to cite for a site, question by question, from lookups already made, and the credits left for more.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • 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.”

    Publisher declares: read-only no · destructive no · open-world yes

    2 inputs, 2 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • questionstringrequired“What a buyer would ask an assistant, in their words.”
  • mttr_signup

    “Signs the person up with their email, the one call that works before mttr has a key for them.”

    Publisher declares: read-only no · destructive no · open-world no

    1 input, 1 required
    • emailstringrequired“The person's email address.”
  • mttr_claim

    “Starts claiming a site for the person: the TXT record or the file that proves they control it.”

    Publisher declares: read-only no · destructive no · open-world no

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • mttr_claim_check

    “Checks the record or file from mttr_claim and, once it is found, adds the site to the person's account.”

    Publisher declares: read-only no · destructive no · open-world yes

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • 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.”

    Publisher declares: read-only no · destructive no · open-world no

    2 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • showboolean“True to name it, false to make it anonymous again.”
  • 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.”

    Publisher declares: read-only no · destructive no · open-world no

    7 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 you found along the way, such as what was true of the site’s code.”
    • filesstring“The files touched, separated by commas.”
    • rulesstring“The mttr rules worked on, by id, separated by commas.”
    • proposalnumber“The proposal this step carried out or checked, by its id from mttr_propose, when the site works by approval.”
  • 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 pers…”

    Publisher declares: read-only no · destructive no · open-world no

    2 inputs, 2 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • modestringrequired“approve to ask the person before each change, automatic to deploy as you go.”
  • 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…”

    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“What the change is, in a few words on one line, at most 120 characters.”
    • summarystringrequired“What the change does and why, in a few sentences the person can judge, at most 2000 characters.”
    • rulestring“The mttr rule it answers, by id, such as answer-first.”
    • pagesstring“The pages it changes, as paths separated by commas, such as /pricing,/about.”
    • diffstring“The change as a unified diff, at most 20,000 characters.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • idnumberrequired“The proposal id that mttr_propose returned.”
  • mttr_proposals

    “The person's proposals, newest first, each with where it stands, for one site or all of them.”

    Publisher declares: read-only yes · open-world no

    1 input
    • sitestring“Only proposals for this site, and its mode.”
  • 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 fix…”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • 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…”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • 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.”

    Publisher declares: read-only no · destructive no · open-world no

    3 inputs, 3 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • briefnumberrequired“The brief's id, from mttr_content_next.”
    • pathstringrequired“The page's path on the site, starting with /, such as /services/sump-pumps.”
  • 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.”

    Publisher declares: read-only no · destructive yes · open-world no

    2 inputs, 2 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • briefnumberrequired“The brief's id, from mttr_content_next.”
  • 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 c…”

    Publisher declares: read-only yes · open-world no

    2 inputs, 2 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • briefnumberrequired“The brief's id, from mttr_content_next.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • mttr_queue_done

    “Says a queued task is done, by its id from mttr_queue.”

    Publisher declares: read-only no · destructive no · open-world no

    1 input, 1 required
    • idnumberrequired“The task id from mttr_queue.”
  • 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.”

    Publisher declares: read-only no · destructive no · open-world no

    1 input
    • daysnumber“How many days the link lasts, from 1 to 90.”
  • 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 f…”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • 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 D…”

    Publisher declares: read-only no · destructive no · open-world no

    5 inputs
    • publishboolean“True to publish, false to hide.”
    • namestring“A display name, at most 40 characters.”
    • homestring“One of the person's sites proved by DNS or a file, as a domain.”
    • sitestring“A site in the portfolio, to set how it is shown.”
    • shownstring“named, or code for its code on the profile.”
  • 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.”

    Publisher declares: read-only no · destructive no · open-world no

    2 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • outboolean“True to take it out, false to put it back.”
  • mttr_job

    “How a rescan stands: waiting, running, done or failed, and how many reads are ahead of it.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • idnumberrequired“The job id that mttr_rescan returned.”
  • mttr_events

    “The newest things that happened: reads asked for, finished and failed, scores that moved, rules that were fixed.”

    Publisher declares: read-only yes · open-world no

    2 inputs
    • sitestring“Only events for this site.”
    • limitnumber“How many to return.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    1 input
    • daysnumber“The range, in days: 1, 7 or 30.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    5 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • showstring“Which links.”
    • qstring“Text a path, a site or the link text must contain.”
    • limitnumber“How many to return.”
    • offsetnumber“How many to skip, for the next part of a long list.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • linksstring“Which links to count between sections.”
  • mttr_map

    “Every page of a site's latest read, one of three ways.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • viewstring“tree (the default), links or meaning.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 2 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • withstringrequired“The other site, as a domain already read.”
    • viewstring“rules (the default) or content.”
  • mttr_reviews

    “Verdicts a model could not be relied on for, which wait for a person and count neither for nor against a score.”

    Publisher declares: read-only yes · open-world no

    1 input
    • offsetnumber“How many to skip, for the next part of a long list.”
  • mttr_rules

    “The rulebook: every rule mttr checks, with its stage, its weight and how to fix a failure.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • mttr_similar

    “Pages of a site that mean nearly the same thing, grouped, which may compete for one search.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • pathstring“A page, as a path such as /guides/gravel.”
    • limitnumber“How many to return.”
  • mttr_near

    “The sites closest in meaning to one site, closest first: the ones writing about the same work, which are its likeliest rivals.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • limitnumber“How many to return.”
  • 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 o…”

    Publisher declares: read-only yes · open-world no

    7 inputs
    • instring“A line of work, such as trades, for its own board.”
    • statestring“A US state by its two letters, such as MO, for the board of the sites there.”
    • citystring“A city in that state, such as Dallas, for the board of the sites there.”
    • sizestring“Sites of about one size, by the pages a read took of them.”
    • 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.”
  • 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, w…”

    Publisher declares: read-only yes · open-world no

    4 inputs, 1 required
    • nodestringrequired“What to open: site:example.com, s:<code> for an unnamed site, market:<code>, work:<id> such as work:trades, rule:<id> such as rule:answer-first, page:example.c…”
    • trailstring“The steps walked so far, as the last reply gave them under "onward".”
    • bystring“What kind of edge led here, so Next takes another kind.”
    • whystring“On a site node: a named site near it, for the passages of the two that came closest.”
  • mttr_markets

    “The markets last found: groups of sites close in meaning, each named by the site at its centre, largest first.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • 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 si…”

    Publisher declares: read-only yes · open-world no

    4 inputs, 1 required
    • qstringrequired“The question, in plain words.”
    • marketstring“Only this market, named by the site at its centre, as mttr_markets gives it.”
    • sitesstring“Only these sites, as domains separated by commas.”
    • limitnumber“How many to return.”
  • 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 clo…”

    Publisher declares: read-only yes · open-world no

    4 inputs, 3 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • pathstringrequired“The page, as a path such as /guides/gravel.”
    • rulestringrequired“A page rule id, as mttr_rules gives it.”
    • limitnumber“How many to return.”
  • 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 s…”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • 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.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • limitnumber“How many to return.”
  • 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, placeho…”

    Publisher declares: read-only yes · open-world no

    4 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • showstring“strong (the default): pages with hidden or left-in text; all: any sign.”
    • limitnumber“How many to return.”
    • offsetnumber“How many to skip, for the next part of a long list.”
  • 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, ea…”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
  • mttr_backlinks

    “The sites mttr has read that link to a site, the most pages first, with how many sites were counted.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • limitnumber“How many to return.”
    • offsetnumber“How many to skip, for the next part of a long list.”
  • mttr_traffic

    “Clicks from Google search, from Search Console.”

    Publisher declares: read-only yes · open-world no

    4 inputs
    • sitestring“The site, as a domain such as example.com.”
    • showstring“lost (the default), gained, or all pages by clicks.”
    • limitnumber“How many to return.”
    • offsetnumber“How many to skip, for the next part of a long list.”
  • 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 crawle…”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • limitnumber“How many to return.”
  • 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).”

    Publisher declares: read-only yes · open-world no

    5 inputs, 1 required
    • sitestringrequired“The site, as a domain such as example.com.”
    • showstring“queries (the default), pages, near: queries close to the top, unanswered: searches no passage on the site comes close to, brand searches left out, or better: s…”
    • pagestring“A full page address, to list only the queries that page was shown for.”
    • limitnumber“How many to return.”
    • offsetnumber“How many to skip, for the next part of a long list.”

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-10-26.

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 139
Tools with a description
100% of 62
Typical description length
316 characters

The tool set

Counted from the listing

Tools
62
Size of the list
about 12,020 tokens for an agent to load (characters ÷ 4)
Naming
62 of 62 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 62 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, comparing tools within groups of 40. 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-10-26 (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://mttr.si/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "mttr": {
      "url": "https://mttr.si/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "mttr": {
      "type": "http",
      "url": "https://mttr.si/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"mttr","type":"http","url":"https://mttr.si/mcp"}'
Claude Code
claude mcp add --transport http mttr https://mttr.si/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "mttr": {
      "type": "streamableHttp",
      "url": "https://mttr.si/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "mttr": {
      "httpUrl": "https://mttr.si/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.mttr]
url = "https://mttr.si/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "mttr": {
      "url": "https://mttr.si/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://mttr.si/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 #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mttr.si/mcpSession openedmatchesour test · 2026-10-26
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-26

Choosing

Record checks

Public records · not a safety rating

1 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.
  • 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-10-26. 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. How each check works · Leaderboards

Common questions about si.mttr/mttr

Answered from the data above

Who publishes si.mttr/mttr?

The registry ties the namespace si.mttr to the domain mttr.si; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does si.mttr/mttr need an API key or sign-in?

It opened a session without any credential on 2026-10-26. The registry entry declares no required credential; no declaration is not a guarantee.

Has si.mttr/mttr been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Found this page useful?

Anonymous · no sign-in

A 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

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-26
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. 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.

Exercised · 3
  • 1Inventory
    tool-list    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution    Calls 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-leak    Plants 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
    ssrf    Checks 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-confirmation    Checks 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-handling    Sends 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
    sampling    Checks 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-data    Checks 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-boundary    Checks 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-channel    Checks 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-hiding    Checks 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-redirect    Checks 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-deputy    Checks 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
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough    Checks 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-validation    Checks 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-10-26, 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.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 2,836 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 62 tools, 0 resources, 0 prompts.
  4. 8,497 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.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-26; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
remote (hosted by the publisher)
registry · 2026-10-26
MCP capability
tools
our test · 2026-10-26
Transport
streamable HTTP
registry · 2026-10-26
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-26
Lifecycle status
active
registry · 2026-10-26
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“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. “si.mttr/mttr: MCP server record.” Data checked 2026-10-26. https://protocolprobe.com/mcp/servers/si.mttr/mttr

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

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/si.mttr/mttr)](https://protocolprobe.com/mcp/servers/si.mttr/mttr)

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