# Check a claim (`mttr_claim_check`)

Updated October 24, 2026.

## What does mttr_claim_check do?

Looks for the record or file from Claim a site, and once it is found adds the site to 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 have put the record or the file up.
- A check said not yet, and a few minutes have passed.

## What you ask

You might say: “I added the TXT record. Check my claim on example.com.”

```
mttr_claim_check({ site: "example.com" })
```

| Argument | Type | Needed | What it is |
| --- | --- | --- | --- |
| `site` | Text | Yes | The site, as a domain such as example.com. |

## What comes back

- Whether the proof was found, and where.
- When it was found, the site is yours: its private parts now answer to your key.
- When it was not, what was looked for, so you can compare it with what you put up.

A sample, with made-up sites and figures:

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

Found the TXT record at example.com. The site is on your account.

## Over HTTP

```
curl -X POST "https://mttr.si/api/v1/account/claim/check" \
  -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_check in the API reference](https://mttr.si/docs/reference#mttr_claim_check).

## Goes with

- [Claim a site](https://mttr.si/docs/tools/claim.md)
- [Your work board](https://mttr.si/docs/tools/todo.md)