Machine Relations MCP server
Which servers in the official MCP registry are Machine Relations's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-13
- Registry nameai.machinerelations/mriverified in the MCP registry
The registry name sits under machinerelations.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-13
- Tools4
- Server calls itselfmachinerelations-mri
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 183 ms.
mri_list_categoriesList every Machine Relations Index category (e.g. cybersecurity, fintech, enterprise-software, ai-visibility-geo) with the question shapes that have published citation rates, plus the source-role vocabulary. Call this first to get a valid…
mri_get_categoryReturn one category's question shapes (best tools, how buyers choose, comparisons, top lists, problem-first research, is it worth it, news) and the evidence state of each: published with rates, collecting, or not collectable.
mri_get_cited_sourcesRanked source domains that AI answer engines cite for one category and question shape, with citation rate (share of monitored answer runs citing the domain), rank, percentile and source role (editorial publication, vendor-owned, analyst…
mri_get_domainFor one domain or URL, return how often AI answer engines cite it: overall citation rate, which engines cite it, confidence tier, rank among all cited domains and within its source role, and per-category segment rates. Use to answer 'does…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"mri": {
"type": "http",
"url": "https://machinerelations.ai/mcp"
}
}
}OpenAPI spec
5 paths, read 2026-10-13. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.