MCP toolsRulebook and crawlUpdated
The rulebook
What does mttr_rules do?
Every rule mttr checks, with its stage, its weight and how to fix a failure. The same rulebook every page is held to. A key may make this call on the sites it has claimed.
When to use it
- You want to know what a rule asks before fixing it.
What you ask
You say“What does mttr check, and how much does each rule weigh?”
Your assistant calls
mttr_rules({})It takes nothing. Ask for it as it is.
What comes back
- Each rule with its id, title, stage, weight and fix.
| Rule | Stage | Weight |
|---|---|---|
| Serve a robots.txt | Access | 3 of 5 |
| Link to pages from related content | Understand | 2 of 5 |
| Make near-copy pages distinct | Trust | 5 of 5 |
| Add a tap-to-call link | Act | 3 of 5 |
The first rule of each stage, from the rulebook as it stands. The answer itself is JSON, with every rule and its fix.
Over HTTP
It is GET /api/v1/rules, with your key as a bearer token:
curl "https://mttr.si/api/v1/rules" \
-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. |
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_rules in the API reference.