# Claim a site (`mttr_claim`)

Updated October 24, 2026.

## 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.

Who may call it: Your claimed sites.

## 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 might say: “Claim example.com for me.”

```
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.

A sample, with made-up sites and figures:

1. Token given (here)
2. Record put up
3. Record found
4. Site added

Add a TXT record mttr-verify=… at example.com, or publish it at /.well-known/mttr.txt.

## Over HTTP

```
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. |

## Sources

- [Model Context Protocol: tools](https://modelcontextprotocol.io/specification/2025-06-18/server/tools), Model Context Protocol: How an assistant calls a tool.

The call in full: [mttr_claim in the API reference](https://mttr.si/docs/reference#mttr_claim).

## Goes with

- [Check a claim](https://mttr.si/docs/tools/claim-check.md)
- [Sign up](https://mttr.si/docs/tools/signup.md)