MCP toolsRivals and marketsUpdated
Nearest sites
What does mttr_near do?
The sites closest in meaning to one site, closest first: the ones writing about the same work, which are its likeliest rivals. A key may make this call on the sites it has claimed.
When to use it
- You do not know who the rivals are.
What you ask
You say“Which sites are closest to example.com?”
Your assistant calls
mttr_near({ 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
- Each site with how close it reads, and how many of its pages its meaning is drawn from.
- Until the site has been read for meaning, an empty list and a note that says so.
- Close means similar in meaning, never better or cited.
rival.exampleDrain and septic work, same region
88% alikenorth.examplePlumbing, a wider range of work
79% alikepipes.exampleCommercial drains
66% alike
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}/near, with your key as a bearer token:
curl "https://mttr.si/api/v1/sites/example.com/near" \
-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_near in the API reference.