MCP toolsRead and fixUpdated
What changed
What does mttr_changes do?
What the latest read of a site changed against the one before it: the score, rules now passing, rules newly failing, and pages added and removed. Any key may make this call, on any public site.
When to use it
- A read you asked for is done.
- A score moved and you want to know why.
What you ask
You say“What changed on example.com since the last read?”
mttr_changes({ site: "example.com" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | Yes | The site, as a domain such as example.com. |
What comes back
- The score then and now.
- Rules now passing and rules newly failing.
- Pages added and removed.
- For a site that sends its own visit counts, its visits in the week before the read and the week since, so a fix can be judged by what followed it.
Now passing
- Show sources on guides
- Add a tap-to-call link
Newly failing
- Fix description lengths
3 pages added, 1 removed
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON. A score says pages are well formed. It does not say an assistant cites the site.
Over HTTP
It is GET /api/v1/sites/{site}/changes, with your key as a bearer token:
curl "https://mttr.si/api/v1/sites/example.com/changes" \
-H "Authorization: Bearer $MTTR_KEY"When it fails
| When | Status | What to do |
|---|---|---|
| Your assistant has no key yet | 401 over MCP | Sign up with mttr_signup, then connect again with the key it gives. |
| mttr has no public report of the site yet | 404 | Ask for a read with mttr_rescan, then watch it with mttr_job. |
Every error’s wording is in the API reference.
The call in full, with its HTTP address, each argument’s type, who may make it and the call in four languages, is mttr_changes in the API reference.