_ registry / mcp http-sse · checked 2h ago

mesquared-visibility-mcp

https://mesquared-mcp-server.vercel.app

Registry code: 181c44f4ebf98de8

api record

AI visibility scans for business websites with scores, issues, and a full-scan link.

from a public catalogue that lists it, not from the operator

endpoint
https://mesquared-mcp-server.vercel.app/mcp
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 mesquared-visibility-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is mesquared-visibility-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does mesquared-visibility-mcp have?
3 tools: compare_visibility, scan_visibility, visibility_audit_info.
Is mesquared-visibility-mcp 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
227ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 295 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
productivity & business marketing & seo
used for
  • scan a business website for seo and ai visibility
  • compare two websites' visibility scores
  • explain the audit methodology
takes → gives
web pages, text → data
tools
3 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 3 tools
1 open 2 never probed 1 of 3 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.

  • visibility_audit_info reads open 17h ago

    Explain the MeSquared SEO/AEO website-readiness methodology, its measurement boundaries, and how to use the available scan tools.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • compare_visibility reads unknown 17h ago

    Run public-site SEO/AEO website-readiness scans for two business websites and compare aggregate scores, selected evidence, site signals, and top issues. This is a readiness comparison, not observed rank or live citation benchmarking.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "first_url",
    "second_url"
  ],
  "properties": {
    "first_url": {
      "type": "string",
      "maxLength": 2048,
      "minLength": 1,
      "description": "The first business website URL, such as example.com."
    },
    "second_url": {
      "type": "string",
      "maxLength": 2048,
      "minLength": 1,
      "description": "The second business website URL, such as competitor.com."
    }
  }
}
    arguments 22 lines
  • scan_visibility reads unknown 17h ago

    Run a public-site SEO/AEO website-readiness scan for one business website. Returns aggregate readiness scores, selected technical and answer-quality evidence, site signals, and prioritized issues. This does not measure observed rankings, Search Console performance, or live AI mentions/citations.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 2048,
      "minLength": 1,
      "description": "The business website URL to scan, such as example.com."
    }
  }
}
    arguments 15 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 181c44f4ebf98de8.

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

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.