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

ai-crawlability-check

https://mcp.milan-novotny.com

Registry code: 425fe86e6962782b

api record

AI Crawlability Check answers one question about any public URL: can AI search engines and assistants (ChatGPT, Claude, Perplexity, Google AI Overviews, Copilot) crawl it, index it and quote it? Start with check_ai_crawler_access for robots.txt and bot access. Use check_ai_indexability for noindex, canonical, JavaScript rendering and sitemap coverage. Use check_ai_citability for content structure and evidence, and check_seo_basics for on-page SEO. Every tool is read-only and returns a 0-100 score, per-check status with the measured value, and fixes. Report the measured values as given and do…

endpoint
https://mcp.milan-novotny.com/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 ai-crawlability-check live?
Yes — it answered the hub's last check (checked 15h ago). It answered 100% of checks over the last 30 days.
Is ai-crawlability-check free to use?
Yes — the hub reached it with no key and no payment.
What tools does ai-crawlability-check have?
5 tools: check_seo_basics, get_review_rubric, check_ai_crawler_access, check_ai_indexability, check_ai_citability.
Is ai-crawlability-check 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
100%

90 days 100%· all time 100%

latency
188ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ 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 5 tools
5 never probed 0 of 5 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.

  • check_seo_basics unknown 15h ago

    Fetches a public page and runs 24 measurable on-page SEO checks: title and meta description length, H1, heading hierarchy, keyword placement and density, slug, canonical, internal and external links, anchor text, image alt text, schema and social tags. Pass the target keyword to enable the keyword checks. Does not cover rankings or backlinks.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public http(s) URL of the page to check, for example https://example.com/pricing."
        },
        "keyword": {
          "type": "string",
          "description": "Target keyword or phrase. Optional; without it the keyword checks are skipped."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • get_review_rubric unknown 15h ago

    Returns a scoring rubric as text for the judgment items the URL tools cannot measure: geo (would an AI engine quote this article?) or seo (pre-publish SEO review). Fetches nothing.

    mcp-tool

    {
      "type": "object",
      "required": [
        "type"
      ],
      "properties": {
        "type": {
          "enum": [
            "geo",
            "seo"
          ],
          "type": "string",
          "description": "Which rubric to return."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • check_ai_crawler_access unknown 42h ago

    Reports which AI crawlers may fetch a public URL. Reads the site's robots.txt and returns allowed or blocked, with the deciding rule, for each known AI crawler from OpenAI, Anthropic, Perplexity, Google, Microsoft, Apple, Meta, Amazon and others, split into search and answer-time bots versus training bots. Also checks whether the server answers an automated request, noindex and nosnippet directives, declared sitemaps, Content-Signal lines and llms.txt. Use for "are we blocking GPTBot or ClaudeBot?", "can ChatGPT read this page?" or an AI crawler audit of robots.txt.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public http(s) URL of the page to check, for example https://example.com/pricing."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • check_ai_indexability unknown 42h ago

    Checks whether a public page can be indexed by search and AI engines once a crawler reaches it. Measures HTTP status and redirects, noindex, canonical target, how much copy exists in the raw HTML without JavaScript, client-side rendering signals, title and H1, XML sitemap coverage, response time, HTML size, structured data validity, dates and language. Use for "why is this page not showing up in ChatGPT or Perplexity?", "is this page indexable?" or to check a JavaScript-rendered page. It does not query any index.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public http(s) URL of the page to check, for example https://example.com/pricing."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • check_ai_citability unknown 15h ago

    Fetches a public page and scores how quotable its content is for AI engines once it is crawled and indexed. Measures answer-first structure, question headings, lists and tables, FAQ, paragraph and sentence length, statistic and source density, named entities, schema, author, freshness and llms.txt, plus a short crawler-access summary. Use for "will AI cite this page?", "is this article LLM-friendly?" or a GEO check. Tuned for articles and guides.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public http(s) URL of the page to check, for example https://example.com/pricing."
        }
      },
      "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 425fe86e6962782b.

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

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.