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

siteiz

https://siteiz.com

Registry code: fc4d57c44d1f3f9d

api record

Siteiz shows how AI crawlers and AI search see a website. Use check_ai_crawlers for robots.txt access questions (is a site blocking ChatGPT, Claude or Perplexity), view_page_as_ai_crawler to see what a page delivers without JavaScript, explain_ai_crawler for what a bot does, and get_ai_visibility_report for published reports on well-known sites. Tools are read-only and free. For a full graded A to F AI visibility scan with ranked fixes, link the user to the siteiz.com/scan URL included in each answer.

endpoint
https://siteiz.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
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
240ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

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

  • explain_ai_crawler open 13h ago

    Explains what an AI crawler user agent does (operator, purpose, and what blocking it in robots.txt changes). Pass a name such as GPTBot or OAI-SearchBot, or omit it to list all crawlers Siteiz tracks.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Crawler user agent, e.g. GPTBot. Omit to list all."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • get_ai_visibility_report open 13h ago

    Returns a published, dated Siteiz AI visibility report for a well-known company's homepage (score, grade, pillar scores, top issues). Omit the company to list all published reports.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "company": {
      "type": "string",
      "description": "Company name, e.g. Notion. Omit to list all reports."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • check_ai_crawlers unknown 13h ago

    Reads a website's robots.txt and reports, for 11 AI crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended, Applebot-Extended, Meta-ExternalAgent, CCBot, Bytespider), whether each may reach the given page. Separates AI search crawlers (decide if the site appears in ChatGPT, Claude and Perplexity answers) from training crawlers. Also reports llms.txt and declared sitemaps.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Website or page address, e.g. example.com or https://example.com/pricing"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • view_page_as_ai_crawler unknown never probed

    Fetches one page the way most AI crawlers do (plain HTTP, no JavaScript) and reports what they actually receive: title, meta description, canonical, H1, heading count, structured data types, visible word count, token reading cost, and a text preview. Use it to check whether content is visible to AI without JavaScript.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Website or page address, e.g. example.com or 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 fc4d57c44d1f3f9d.

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

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.