Machine Relations Index
REMOTE · MACHINERELATIONS.AI
Which source domains AI answer engines cite, by buyer category and question shape.
Available components
Last scanned (19 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1793 tokens (~298/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 3 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Tool coverage: 64% → 73% ▲ functional
- “mri_get_cited_sources” added an optional parameter “cursor” cosmetic
- “mri_get_engine” added an optional parameter “cursor” cosmetic
- “mri_list_categories” added an optional parameter “release” cosmetic
- “mri_list_engines” added an optional parameter “release” cosmetic
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 235 → 274 ▼ functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “mri_get_cited_sources” rewrote its description, which is the text the model reads security
- Tool “mri_get_domain” rewrote its description, which is the text the model reads security
- Schema quality: 957 → 1410 ▼ functional
- Tool coverage: 71% → 64% ▼ functional
- Schema quality: excellent → good functional
- New tool “mri_get_engine” functional
- New tool “mri_list_engines” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://machinerelations.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=machinerelations.ai | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | bac937a8db5f9f6a0e28d80ec2dc1734 |
| SANs: machinerelations.ai, *.machinerelations.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of machinerelations.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| machinerelations.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://machinerelations.ai/mcp | Verified | 200 | |
| http (plaintext) | http://machinerelations.ai/mcp | HTTPS enforced | 308 | https://machinerelations.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
mri_get_category Get an MRI category ~77
Return 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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category key from mri_list_categories, e.g. cybersecurity. |
No output schema declared.
No examples provided.
mri_get_cited_sources Which sources AI engines cite ~236
Ranked source domains that AI answer engines cite, pooled across engines, 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 research, community, academic/government, market database, wire distribution). This rate is not split by engine. For one engine, use mri_get_engine.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category key, e.g. cybersecurity. |
| cursor | string | – | Page token from the previous response's next.cursor. When set, offset is ignored. |
| limit | integer | – | – |
| offset | integer | – | – |
| question_shape | string | yes | Buyer question pattern: best_x (best X tools), how_choose (how to choose), is_x_worth (is it worth it), news_topic (recent news), problem_first (how to solve a problem), top_list (top platforms), x_v… |
| source_role | string | – | Optional filter, e.g. editorial_media for publications only, vendor_owned, analyst_research, community_social. |
No output schema declared.
No examples provided.
mri_get_domain How often AI engines cite a site ~157
For one domain or URL, return how often AI answer engines cite it: overall citation rate, the rate on each engine (overall.byEngine: cited runs, that engine's observed runs, and whether the engine's sample clears the evidence floor), confidence tier, rank among all cited domains and within its source role, and per-category segment rates. Use to answer 'does ChatGPT cite <site>' or 'what share of Perplexity runs cite <site>'. A published byEngine row with runsCited 0 means that engine did not cite the domain. byEngine is the whole window, not a rate inside one category.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A domain (techcrunch.com) or any URL on it. |
No output schema declared.
No examples provided.
mri_get_engine Sources one answer engine cites ~201
Ranked sources one answer engine cites, by that engine's citation rate across the whole window. Pass category to limit the list to sources with a published segment in that category; the rate stays the whole-window rate and is not a rate inside the category. Collecting categories and engines below the evidence floor withhold the ranking. Use to answer 'what sources does Perplexity cite most?' or 'which sources does Google AI Overviews cite among published <category> sources'.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category key. Limits the ranking to sources with a published segment in that category. |
| cursor | string | – | Page token from the previous response's next.cursor. When set, offset is ignored. |
| engine | string | yes | Engine key from mri_list_engines: chatgpt, claude, gemini, google_ai_mode, google_ai_overviews, perplexity. |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
mri_list_categories List MRI categories ~82
List 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 category key.
| Name | Type | Req | Description |
|---|---|---|---|
| release | string | – | Optional release id. Any release other than the current one returns release_unavailable. |
No output schema declared.
No examples provided.
mri_list_engines List MRI answer engines ~75
List each answer engine with the model the release roster names, the engine's observed runs and days, whether that sample clears the evidence floor, and the most-cited source on that engine across the whole window.
| Name | Type | Req | Description |
|---|---|---|---|
| release | string | – | Optional release id. Any release other than the current one returns release_unavailable. |
No output schema declared.
No examples provided.
How do I install the Machine Relations Index MCP server?
Machine Relations Index is a hosted endpoint at https://machinerelations.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · machinerelations.ai
claude mcp add --transport http ai-machinerelations-mri 'https://machinerelations.ai/mcp'
What is the Machine Relations Index MCP server?
Machine Relations Index is an MCP server listed in the public MCP registry as ai.machinerelations/mri. Which source domains AI answer engines cite, by buyer category and question shape. This page covers its hosted endpoint (https://machinerelations.ai/mcp).
Is the Machine Relations Index MCP server safe to use?
Machine Relations Index scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Machine Relations Index MCP server expose?
Machine Relations Index exposes 6 tools: mri_list_categories, mri_get_category, mri_get_cited_sources, mri_get_domain, mri_list_engines, mri_get_engine. Their descriptions and schemas cost roughly 828 tokens of context every time the server is loaded.
Does the Machine Relations Index MCP server require authentication?
No. We connected to Machine Relations Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Machine Relations Index MCP server still maintained?
Machine Relations Index is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.