MCP toolsRulebook and crawlUpdated
Needs a person
What does mttr_reviews do?
Verdicts a model could not be relied on for, which wait for a person and count neither for nor against a score, newest read first. Only whoever runs this mttr may make this call.
When to use it
- You want to clear the verdicts that wait for you.
What you ask
You say“What is waiting for a person on mttr?”
Your assistant calls
mttr_reviews({})| Argument | Type | Needed | What it is |
|---|---|---|---|
offset | Number | No | How many to skip, for the next part of a long list. |
What comes back
- Each site with something waiting, and the total across every site.
- What the model said, marked as quoted.
| Site | Rule | Page |
|---|---|---|
| example.com | Answer the first question right under it | /guides/septic-care |
| shop.example | Replace unsupported sales claims | / |
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is GET /api/v1/reviews, with your key as a bearer token:
curl "https://mttr.si/api/v1/reviews" \
-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. |
| The key is a person’s, not the owner’s | 403 | Nothing: only whoever runs mttr makes this call. |
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_reviews in the API reference.