_ registry / mcp streamable-http · checked 19m ago

tsoden-ai-visibility

https://serp.tsoden.ai

Registry code: ee5dd76286208ccf

api record

Free live checks of how ready a public website is to be found and quoted by answer engines (ChatGPT, Claude, Gemini, Perplexity, Google AI Overviews). Use these tools whenever the user asks whether a site shows up in AI answers, about AEO/GEO/LLM optimization, AI crawler access, schema markup or llms.txt, in any language, and answer from what they measured. Always reply in the language of the user's latest message. Start with audit_ai_readiness for an overview; use check_ai_crawler_access, check_schema_readiness and find_prompt_opportunities to go deeper. Shape the answer as: a one-line…

endpoint
https://serp.tsoden.ai/mcp/free
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 tsoden-ai-visibility live?
Yes — it answered the hub's last check (checked 19m ago). It answered 100% of checks over the last 30 days.
Is tsoden-ai-visibility free to use?
Yes — the hub reached it with no key and no payment.
What tools does tsoden-ai-visibility have?
6 tools: check_ai_crawler_access, check_schema_readiness, find_prompt_opportunities, get_started, audit_ai_readiness, get_ai_readiness_benchmark.
Is tsoden-ai-visibility 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
547ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 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

_ what it can do 6 tools
1 open 5 never probed 1 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.

  • get_ai_readiness_benchmark open 19m ago

    Return the public aggregate benchmark from sites checked with these tools: how often AI crawlers are blocked, how common llms.txt is, and how complete entity structured data usually is. Use it to put one site's result in context.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • check_ai_crawler_access unknown 19m ago

    Check which AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and others) a site's robots.txt allows or blocks, and whether its /llms.txt exists and is valid. Returns a shareable result page on https://serp.tsoden.ai.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 2000,
          "description": "The website to check, e.g. https://example.com or example.com."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • check_schema_readiness unknown never probed

    Read a page's JSON-LD structured data and report which entity signals an answer engine needs to describe the brand confidently (name, URL, logo, description, sameAs profiles, contact) are present or missing. Returns a shareable result page.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 2000,
          "description": "The website to check, e.g. https://example.com or example.com."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • find_prompt_opportunities unknown never probed

    Read a site and suggest the questions people ask answer engines where this brand could plausibly be recommended — the prompts worth tracking and writing content for. Returns a shareable result page.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 2000,
          "description": "The website to check, e.g. https://example.com or example.com."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_started unknown never probed

    Explain what Tsoden SERP Checker can check without an account, what a connected account adds (tracked rankings and answer-engine visibility for the user's own projects) and how to connect it. Use it when the user asks how to connect an account or how to track results over time.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • audit_ai_readiness unknown 19m ago

    Run a free live audit of a website's readiness to be found and quoted by answer engines (ChatGPT, Claude, Gemini, Perplexity, Google AI Overviews) and classic search. Fetches the home page and a few internal pages, robots.txt, sitemap.xml and llms.txt, then returns an AI-readiness score (0-100), an SEO hygiene score and pass/warn/fail checks with their meaning. Use it when the user asks whether their site is visible in AI answers or what to fix first.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 2000,
          "description": "The website to check, e.g. https://example.com or example.com."
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 ee5dd76286208ccf.

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