_ registry / mcp + a2a http-sse · checked 38m ago

io.verityscore/geo-audit

https://verityscore.io

Registry code: b9a318c3f41401e7

api record

Verity Score provides GEO readiness auditing for Shopify e-commerce stores. Use check_ai_readiness for a quick real-time check of any website. Use get_geo_score for a full audit score (queues unknown stores for 72h analysis). Use get_recommendations for actionable fixes. Use explain_topic to learn about GEO concepts (schema.org, robots.txt, llms.txt, etc.). Use get_vertical_info for industry-specific checklists.

endpoint
https://api.verityscore.io/mcp
door code
529a76c8a545c5ed
protocol
http-sse ·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 io.verityscore/geo-audit live?
Yes — it answered the hub's last check (checked 38m ago). It answered 99% of checks over the last 30 days.
Is io.verityscore/geo-audit free to use?
Yes — the hub reached it with no key and no payment.
What tools does io.verityscore/geo-audit have?
5 tools: get_recommendations, check_ai_readiness, explain_topic, get_geo_score, get_vertical_info.
Is io.verityscore/geo-audit 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.4%

90 days 99.2%· all time 99.2%

latency
133ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 791 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
productivity & business marketing & seo
used for
  • check a store's ai readiness
  • get a shopify store's geo score
  • get fixes to improve ai visibility
  • explain a geo concept
takes → gives
web pages → data, text
tools
5 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 5 tools
1 open 4 never probed 1 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.

  • get_vertical_info reads open 15h ago

    Get AI commerce checklist and benchmarks for a specific e-commerce vertical (beauty, fashion, food, electronics, etc.). Without argument, lists all 15 supported verticals.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "vertical": {
      "type": "string",
      "maxLength": 50,
      "description": "Vertical name (e.g. \"beauty\", \"food\"). Omit to list all."
    }
  }
}
    arguments 11 lines
  • get_recommendations reads unknown 10h ago

    Get the top 3 priority recommendations to improve AI visibility for a Shopify store. Returns actionable fixes with expected impact. If not yet audited, the store is queued for audit within 72 hours.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 100,
      "minLength": 3,
      "description": "Store domain (e.g. \"mybrand.com\")"
    }
  }
}
    arguments 15 lines
  • check_ai_readiness reads unknown 15h ago

    Quick AI readiness check for any website. Checks 5 AI discovery files in real-time: robots.txt, llms.txt, ai.txt, agent-card.json, sitemap.xml. Returns a score from 0 to 5 with per-file recommendations.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 100,
      "minLength": 3,
      "description": "Website domain (e.g. \"mybrand.com\")"
    }
  }
}
    arguments 15 lines
  • explain_topic reads unknown 15h ago

    Explains a GEO or AI commerce concept with actionable guidance for Shopify merchants. Topics: schema.org, robots.txt, llms.txt, AggregateRating, ACP, UCP, Perplexity Shopping, ChatGPT Shopping, claims, E-E-A-T, and more.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "topic"
  ],
  "properties": {
    "topic": {
      "type": "string",
      "maxLength": 100,
      "minLength": 2,
      "description": "Topic keyword (e.g. \"schema.org\", \"robots.txt\", \"reviews\")"
    }
  }
}
    arguments 15 lines
  • get_geo_score reads unknown 10h ago

    Get the GEO readiness score for a Shopify store. Returns score, vertical, top findings, and report link. If not yet audited, the store is queued for audit within 72 hours.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 100,
      "minLength": 3,
      "description": "Store domain (e.g. \"mybrand.com\")"
    }
  }
}
    arguments 15 lines
_ try it over mcp 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 b9a318c3f41401e7.

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