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

rankbits

https://rankbits.com

Registry code: d29e0e1a856230b5

api record

RankBits checks how visible a brand/website is across AI assistants (ChatGPT, Grok, Perplexity, Gemini, AI Overviews, ...). Typical flow: create_scan with a URL, poll get_scan until progress.complete is true, then read the aggregate visibility metrics and per-prompt results. Use enable_tracking to re-run a finished scan on a schedule and get_scan_tracking to read the visibility history. Requires a RankBits API token (create one at https://rankbits.com/api).

endpoint
https://rankbits.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 rankbits live?
Yes — it answered the hub's last check (checked 12m ago). It answered 98% of checks over the last 30 days.
Is rankbits free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does rankbits have?
7 tools: create_scan, get_account, get_scan, enable_tracking, get_scan_tracking, list_scans, list_providers.
Is rankbits 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
98.3%

90 days 98.9%· all time 98.9%

latency
260ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 368 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • scan a brand's visibility in ai assistants
  • track ai visibility over time
  • list ai engines to query
takes → gives
web pages, text → data
tools
5 reads2 changes data
_ 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 7 tools
7 auth-required 7 of 7 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.

  • create_scan changes data auth-required never probed

    Start an AI-visibility scan for a website. Returns immediately with a pending scan; poll get_scan for results.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Website URL to scan, e.g. 'https://acme.com'."
        },
        "location": {
          "type": "string",
          "description": "Country the engines search from, e.g. 'de-de' (Germany) or 'ca-fr' (Canada, French). Omit or 'global' for no location. Gemini, Perplexity and Grok always answer globally."
        },
        "providers": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "AI engine keys to query (see list_providers). Defaults to all engines allowed by the plan."
        },
        "competitors": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Competitor domains/brands to compare against."
        },
        "custom_only": {
          "type": "boolean",
          "description": "Use only custom_prompts; skip prompt generation."
        },
        "prompt_count": {
          "type": "integer",
          "description": "Number of AI-generated prompts to test (default 10, capped by plan)."
        },
        "custom_prompts": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Your own prompts to test in addition to generated ones."
        },
        "compare_competitors": {
          "type": "boolean",
          "description": "Also measure competitor visibility."
        },
        "include_discovered_competitors": {
          "type": "boolean",
          "description": "Auto-discover competitors from AI answers."
        }
      }
    }
    arguments 53 lines
  • get_account reads auth-required 9h ago

    Get the authenticated RankBits account: user info, plan, limits, and remaining scan/response budget.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • get_scan reads auth-required 17h ago

    Get a scan's status, progress, aggregate visibility metrics, and (once finished) per-prompt results across AI engines.

    mcp-tool

    {
      "type": "object",
      "required": [
        "scan"
      ],
      "properties": {
        "scan": {
          "type": "string",
          "description": "Scan reference: the public_id (preferred) or numeric id."
        }
      }
    }
    arguments 12 lines
  • enable_tracking changes data auth-required never probed

    Enable scheduled tracking on a completed scan so it re-runs automatically and builds a visibility history.

    mcp-tool

    {
      "type": "object",
      "required": [
        "scan"
      ],
      "properties": {
        "scan": {
          "type": "string",
          "description": "Scan reference: the public_id (preferred) or numeric id."
        },
        "frequency_days": {
          "type": "integer",
          "description": "Re-run every N days (clamped to plan limits)."
        }
      }
    }
    arguments 16 lines
  • get_scan_tracking reads auth-required 17h ago

    Get tracking status, visibility history over time, and related tracked runs for a scan's lineage.

    mcp-tool

    {
      "type": "object",
      "required": [
        "scan"
      ],
      "properties": {
        "scan": {
          "type": "string",
          "description": "Scan reference: the public_id (preferred) or numeric id."
        }
      }
    }
    arguments 12 lines
  • list_scans reads auth-required 9h ago

    List the account's scans, newest first.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Max scans to return (default 20, max 100)."
        },
        "domain": {
          "type": "string",
          "description": "Filter by exact domain, e.g. 'acme.com'."
        },
        "include_tracked_runs": {
          "type": "boolean",
          "description": "Also include automated tracked re-runs (default false: root scans only)."
        }
      }
    }
    arguments 18 lines
  • list_providers reads auth-required 9h ago

    List the AI engines RankBits can query (key, label, enabled) and which ones the current plan allows.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 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 d29e0e1a856230b5.

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