MCP toolsRead and fixUpdated
Read it again
What does mttr_rescan do?
Asks mttr to read a site again after it has been changed. It answers a job to watch. A site is read at most once every ten minutes. Any key may make this call, on any public site.
When to use it
- A fix is published and you want to see it count.
What you ask
You say“I published the fixes. Read example.com again.”
Your assistant calls
mttr_rescan({ site: "example.com", reason: "Rewrote the service pages" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | Yes | The site, as a domain such as example.com. |
reason | Text | No | What was changed, in a few words. |
What comes back
- A job, with how many reads are ahead of it.
- When asked too soon, when it may be asked again.
- 1Waiting
- 2Running
- 3Done
Job j_318 is in line. 2 reads ahead of it.
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is POST /api/v1/sites/{site}/rescan, with your key as a bearer token:
curl -X POST "https://mttr.si/api/v1/sites/example.com/rescan" \
-H "Authorization: Bearer $MTTR_KEY" \
-H "Content-Type: application/json" \
-d '{"reason":"Rewrote the service pages"}'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. |
| The site is on a private address, or cannot be read | 400 | The answer says “mttr cannot read example.com:” and why. Check the domain. |
| The site was read in the last ten minutes | 429 | The answer gives allowedAt. Ask again after it. |
| The site was removed from mttr | 403 | Nothing: a removed site is not read. |
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_rescan in the API reference.