mttr

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

• 接続方法: クラウドで動く
• トランスポート: Streamable HTTP
• カテゴリ: 検索・AIの記憶
• 入力が必要なもの：Authorization

インストール

使っているAIアプリを選んで、設定をコピーしてください。

必要なもの

• クラウドで動くインストール不要。インターネット経由でつながります

どのアプリを使っていますか？

claude mcp add --transport http mttr https://mttr.si/mcp --header 'Authorization: your-value'

{
  "mcpServers": {
    "mttr": {
      "url": "https://mttr.si/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "mttr": {
      "type": "http",
      "url": "https://mttr.si/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

自分で入力する値

• Authorization 秘密 HTTP header
  Bearer and a free mttr key (mk_...) from https://mttr.si/agents. Without one, an agent can sign up with mttr_signup.

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

ツールの名前と説明は、サーバーが2026年11月7日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

• clickd_site

  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 on

• clickd_brief

  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 perso

• clickd_pages

  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

• clickd_rescan

  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 exa

• clickd_changes

  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

• clickd_rivals

  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`

• clickd_citations

  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

• clickd_claim

  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 clai

• clickd_propose

  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

• clickd_proposals

  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

• clickd_log_work

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

• clickd_todo

  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

• clickd_rules

  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, eac

• clickd_leaderboard

  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.

• clickd_signup

  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 o

• clickd_check

  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

• clickd_schema_create

  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 t

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック

• ! 注意

  作者とリポジトリが一致

  レジストリにソースのリポジトリが載っていないため、公開者（mttr.si）とコードを照合できません

• … 未チェック

  今もメンテナンスされている

  このリポジトリはまだGitHubから読み取っていません

• … 未チェック

  ライセンスがある

  このリポジトリはまだGitHubから読み取っていません

• ✓ 合格

  エンドポイントが応答する

  202ミリ秒で応答（HTTP 200）

• – 対象外

  OAuthでサインイン

  サインイン不要

• ✓ 合格

  ツールの説明に隠れた指示がない

  17件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

検索・AIの記憶のほかのサーバーとの比較i

• このカテゴリのほかの5660件のうち0%よりスターが多い
• このカテゴリのほかの5660件のうち74%より最近レジストリに公開
• 基本チェックの結果が、このカテゴリのほかの5660件のうち39%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方：★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

作者のREADME

リポジトリにREADMEが見つかりません