MCP toolsSearch and assistantsUpdated
Visits
What does mttr_visits do?
Who fetched a site’s pages in the last 28 days against the 28 before, counted by the site’s own server: people, people an assistant sent, and crawlers by name, AI crawlers marked. A key may make this call on the sites it has claimed.
When to use it
- You want to know whether AI crawlers read a site.
- You want to see people sent by assistants.
What you ask
You say“Which AI crawlers fetched example.com this month?”
Your assistant calls
mttr_visits({ site: "example.com" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | Yes | The site, as a domain such as example.com. |
limit | Number | No | How many to return. |
What comes back
- Visits by day, by crawler, by assistant and by page.
- The last day an AI crawler fetched each page.
- A crawler fetching a page is not a citation. Only sites whose server sends counts have any.
310Week 1
284Week 2
352Week 3
401Week 4
- People
- 1,3471,190 before
- Sent by assistants
- 6431 before
- AI crawler fetches
- 2,2101,640 before
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is GET /api/v1/sites/{site}/visits, with your key as a bearer token:
curl "https://mttr.si/api/v1/sites/example.com/visits" \
-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 has not claimed the site | 404 | Claim it with mttr_claim, then mttr_claim_check. |
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_visits in the API reference.