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

citead-score

https://mcp.citead.com

Registry code: 5f1b2789df655e02

api record

Free GEO scoring by Citead (citead.com), no API key. score_url fetches a public page and scores it; score_text scores text you pass inline (markdown, plain text or HTML). The GEO score (0 to 100) measures how easy the content is for a language model to understand, reuse and cite: information density, quotable sentences, self-contained paragraphs, sourced and dated facts, clear structure, freshness. Naturalness is returned as a criterion but does not count in the score. It is computed by deterministic rules, without a language model: the same content always gets the same score. It does not…

endpoint
https://mcp.citead.com/public/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 citead-score live?
Yes — it answered the hub's last check (checked 6h ago). It answered 99% of checks over the last 30 days.
Is citead-score free to use?
Yes — the hub reached it with no key and no payment.
What tools does citead-score have?
2 tools: score_text, score_url.
Is citead-score 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
98.7%

90 days 99.2%· all time 99.2%

latency
165ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 253 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • score a web page for llm citability
  • score text for generative engine optimization
takes → gives
web pages, text → data
tools
2 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • score_text reads unknown 23h ago

    Compute the GEO score of a text with Citead: an article draft, a page copy, markdown, plain text or HTML. Returns the overall score (0 to 100), the score of each criterion (semantic richness, AI citability, freshness, content organization, authority and citations, and naturalness, which does not count in the score), the main fixes to apply, and a link to Citead's free live editor. The GEO score (0 to 100) measures how easy the content is for a language model to understand, reuse and cite: information density, quotable sentences, self-contained paragraphs, sourced and dated facts, clear structure, freshness. Naturalness is returned as a criterion but does not count in the score. It is computed by deterministic rules, without a language model: the same content always gets the same score. It does not guarantee that an AI assistant will cite the page. Free, no API key, the text is not stored. Texts under 300 words get a capped score (at most 65).

    mcp-tool

    {
      "type": "object",
      "title": "score_textArguments",
      "required": [
        "content"
      ],
      "properties": {
        "title": {
          "anyOf": [
            {
              "type": "string",
              "maxLength": 300
            },
            {
              "type": "null"
            }
          ],
          "title": "Title",
          "default": null,
          "description": "Page title. Defaults to the first heading."
        },
        "content": {
          "type": "string",
          "title": "Content",
          "maxLength": 200000,
          "minLength": 1,
          "description": "The text to score: markdown, plain text or HTML."
        },
        "language": {
          "anyOf": [
            {
              "enum": [
                "en",
                "fr"
              ],
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Language",
          "default": null,
          "description": "Language of the text. Omit to detect it. Only English and French have dedicated rules; other languages use the English ones."
        }
      }
    }
    arguments 47 lines
  • score_url reads unknown 23h ago

    Fetch a public web page and compute its GEO score with Citead. Returns the overall score (0 to 100), the score of each criterion (semantic richness, AI citability, freshness, content organization, authority and citations, and naturalness, which does not count in the score), the main fixes to apply, and a citead.com link that shows the analysis again. The GEO score (0 to 100) measures how easy the content is for a language model to understand, reuse and cite: information density, quotable sentences, self-contained paragraphs, sourced and dated facts, clear structure, freshness. Naturalness is returned as a criterion but does not count in the score. It is computed by deterministic rules, without a language model: the same content always gets the same score. It does not guarantee that an AI assistant will cite the page. Free, no API key. Citead does not store the page content or its score; it keeps only daily counts of outcomes, the domain name of sites that block its fetcher (45 days) and per-IP rate-limit counters. The details_url page does not publish the result to the public leaderboard. Pages behind a login or rendered only by JavaScript may not be fetchable: use score_text with the page text instead.

    mcp-tool

    {
      "type": "object",
      "title": "score_urlArguments",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Url",
          "maxLength": 2048,
          "minLength": 4,
          "description": "Public http(s) URL of the page to score."
        }
      }
    }
    arguments 16 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 5f1b2789df655e02.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5f1b2789df655e02/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/5f1b2789df655e02/badge.svg)](https://brick.blue/agent/5f1b2789df655e02?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
60%

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.