MCP toolsAccount and sitesUpdated
Claim a site
What does mttr_claim do?
Starts proving a site is yours. It gives you a short token to put up as a DNS TXT record or as a file on the site. Once it is found, the site joins your account. A key may make this call on the sites it has claimed.
When to use it
- You want Search Console figures, visits, citations or rivals for your own site.
- You want the site on your work board and progress page.
What you ask
You say“Claim example.com for me.”
Your assistant calls
mttr_claim({ 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 token, as the TXT record to add and as the file to publish instead.
- Where each goes: the domain or
_mttr.before it, or/.well-known/mttr.txt. - What to call next: Check a claim.
- 1Token given
- 2Record put up
- 3Record found
- 4Site added
Add a TXT record mttr-verify=… at example.com, or publish it at /.well-known/mttr.txt.
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is POST /api/v1/account/claim, with your key as a bearer token:
curl -X POST "https://mttr.si/api/v1/account/claim" \
-H "Authorization: Bearer $MTTR_KEY" \
-H "Content-Type: application/json" \
-d '{"site":"example.com"}'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_claim in the API reference.