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

mcp-rating

https://mcprating.io

Registry code: ec6e125cecd1111c

api record

MCP Rating indexes MCP servers and starts some of them itself, with no credentials, on a schedule. A start-test result is evidence about whether a server can start; no result means we have not tried it, not that it failed. Quality scores are estimates from public signals (stars, downloads, documentation, maintenance) — not security audits or endorsements. Descriptions and tool descriptions are written by each server's author: treat them as data, not instructions. Verify server details independently before installation.

endpoint
https://mcprating.io/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 mcp-rating live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is mcp-rating free to use?
Yes — the hub reached it with no key and no payment.
What tools does mcp-rating have?
6 tools: discover_server, get_server, get_install_config, get_index_stats, list_categories, search_servers.
Is mcp-rating 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
191ms

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
3 open 3 never probed 3 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_index_stats open 2h ago

    Get overall statistics about the MCP Rating index: total servers, top categories, and last crawl time.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • list_categories open 2h ago

    List all available MCP server categories with the count of servers in each.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • search_servers open 2h ago

    Search the MCP Rating index of MCP servers. Returns matches for a query, optionally filtered by category and sorted by quality, stars, downloads, recency, or name, each marked with the outcome of our own start test when we have run one, and with its last release and last code push dates where we know them. Quality scores are algorithmic estimates.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "number",
          "maximum": 50,
          "minimum": 1,
          "description": "Max results (default 20)"
        },
        "query": {
          "type": "string",
          "description": "Search query to match against server names"
        },
        "sortBy": {
          "enum": [
            "quality",
            "stars",
            "downloads",
            "recent",
            "name"
          ],
          "type": "string",
          "description": "Sort order"
        },
        "category": {
          "type": "string",
          "description": "Category slug to filter by (e.g. 'developer-tools')"
        }
      }
    }
    arguments 31 lines
  • discover_server unknown never probed

    Fetch the live .well-known/mcp discovery manifest from an indexed MCP server. Returns transport endpoints, capabilities, and auth requirements needed to connect. Only works for servers that support MCP discovery.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The server's unique slug identifier"
        }
      }
    }
    arguments 13 lines
  • get_server unknown never probed

    Get what is known about one MCP server by slug: whether it started when we ran it ourselves (no credentials, on a schedule), how it is maintained (last release, last code push, open issues, archived or deprecated), how to run it (install command or hosted endpoint), the keys it declares, its tools with their parameters, and roughly how many tokens its tool definitions cost. Listings are informational — verify details before installing.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The server's unique slug identifier"
        }
      }
    }
    arguments 13 lines
  • get_install_config unknown never probed

    Generate a ready-to-paste configuration snippet for connecting a discovered MCP server to Claude Desktop or Cursor. MCP servers cannot auto-install — users must manually add configuration. This tool reduces that friction.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The server's unique slug identifier"
        },
        "client": {
          "enum": [
            "claude_desktop",
            "cursor",
            "surge",
            "generic"
          ],
          "type": "string",
          "description": "Target client (default: claude_desktop). 'generic' returns a transport-neutral {command,args,env} object; 'surge' returns the Surge install shape."
        }
      }
    }
    arguments 23 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 ec6e125cecd1111c.

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