_ registry / mcp streamable-http · checked 7h ago

machinerelations-mri

https://machinerelations.ai

Registry code: e7c9696c9c6c67d3

api record

Machine Relations Index (MRI) by Jaxon Parrott, Machine Relations Research — machinerelations.ai. The Index measures which source domains AI answer engines (ChatGPT, Claude, Gemini, Google AI Mode, Google AI Overviews, Perplexity) cite when buyers ask questions, by category and question shape. Use mri_list_categories first to find the category key; mri_get_cited_sources for the ranked sources answer engines cite, pooled across engines, for a category and question shape; mri_list_engines and mri_get_engine for one engine's citation rates; mri_get_domain for how often a given site is cited,…

endpoint
https://machinerelations.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is machinerelations-mri live?
Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
Is machinerelations-mri free to use?
Yes — the hub reached it with no key and no payment.
What tools does machinerelations-mri have?
6 tools: mri_get_cited_sources, mri_get_domain, mri_get_engine, mri_get_category, mri_list_categories, mri_list_engines.
Is machinerelations-mri safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.6%· all time 99.6%

latency
416ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 247 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • find sources ai answer engines cite for a category
  • check how often ai engines cite a domain
  • list ai citation categories
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
2 open 4 never probed 2 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • mri_list_categories reads open 16h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "release": {
          "type": "string",
          "description": "Optional release id. Any release other than the current one returns release_unavailable."
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • mri_list_engines open 16h ago

    List each answer engine with its latest-successful model metadata and historical modelPeriods (null when unavailable), 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.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "release": {
          "type": "string",
          "description": "Optional release id. Any release other than the current one returns release_unavailable."
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • mri_get_cited_sources reads unknown 16h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category",
        "question_shape"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 100,
          "minimum": 1
        },
        "cursor": {
          "type": "string",
          "description": "Page token from the previous response's next.cursor. When set, offset is ignored."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "minimum": 0
        },
        "category": {
          "type": "string",
          "description": "Category key, e.g. cybersecurity."
        },
        "source_role": {
          "type": "string",
          "description": "Optional filter, e.g. editorial_media for publications only, vendor_owned, analyst_research, community_social."
        },
        "question_shape": {
          "enum": [
            "best_x",
            "how_choose",
            "is_x_worth",
            "news_topic",
            "problem_first",
            "top_list",
            "x_vs_y"
          ],
          "type": "string",
          "description": "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_vs_y (A vs B)."
        }
      },
      "additionalProperties": false
    }
    arguments 46 lines
  • mri_get_domain reads unknown 24h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "A domain (techcrunch.com) or any URL on it."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • mri_get_engine unknown 24h ago

    Ranked sources one answer engine cites, by that engine's citation rate across the whole window; an engine whose collection changed inside the window also returns collectionRegime, its sources since the change, which is what it cites now. 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'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "engine"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 100,
          "minimum": 1
        },
        "cursor": {
          "type": "string",
          "description": "Page token from the previous response's next.cursor. When set, offset is ignored."
        },
        "engine": {
          "type": "string",
          "description": "Engine key from mri_list_engines: chatgpt, claude, gemini, google_ai_mode, google_ai_overviews, perplexity."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "minimum": 0
        },
        "category": {
          "type": "string",
          "description": "Optional category key. Limits the ranking to sources with a published segment in that category."
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • mri_get_category reads unknown 24h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category"
      ],
      "properties": {
        "category": {
          "type": "string",
          "description": "Category key from mri_list_categories, e.g. cybersecurity."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e7c9696c9c6c67d3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e7c9696c9c6c67d3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e7c9696c9c6c67d3/badge.svg)](https://brick.blue/agent/e7c9696c9c6c67d3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.