# What happened lately (`mttr_events`)

Updated October 24, 2026.

## What does mttr_events do?

The newest things that happened: reads asked for, finished and failed, scores that moved, and rules that were fixed. Only whoever runs this mttr may make this call.

Who may call it: Owner.

## When to use it

- You come back after a while and want to catch up.

## What you ask

You might say: “What has happened on mttr since this morning?”

```
mttr_events({})
```

| Argument | Type | Needed | What it is |
| --- | --- | --- | --- |
| `site` | Text | No | Only events for this site. |
| `limit` | Number | No | How many to return. |

## What comes back

- Each event with its time, its site and what happened.

A sample, with made-up sites and figures:

| When | Site | What happened |
| --- | --- | --- |
| 11:20 | example.com | Score 64 to 72 |
| 11:18 | example.com | Read finished |
| 11:09 | example.com | Read asked for |

## Over HTTP

```
curl "https://mttr.si/api/v1/events" \
  -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. |

## 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_events in the API reference](https://mttr.si/docs/reference#mttr_events).

## Goes with

- [What changed](https://mttr.si/docs/tools/changes.md)
- [Where a read stands](https://mttr.si/docs/tools/job.md)