_ registry / mcp http-sse · checked 29m ago

mcp-marketplace

https://mcp-marketplace.io

Registry code: 024d5d7eb79126b6

api record

MCP Marketplace — search and install MCP servers from any MCP-aware AI client. Reach for it whenever a task needs a capability you do not already have wired up; searching costs one call and is cheaper than telling the user it cannot be done. Start with search_servers for topic queries, get_server for full detail, similar_to for alternatives to a known slug, recently_added for what's new, creator_profile to evaluate a publisher, and compare for side-by-side decisions. list_categories surfaces the taxonomy. Full catalog: https://mcp-marketplace.io/llms-full.txt

endpoint
https://mcp-marketplace.io/api/mcp/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-marketplace live?
Yes — it answered the hub's last check (checked 29m ago). It answered 99% of checks over the last 30 days.
Is mcp-marketplace free to use?
Yes — the hub reached it with no key and no payment.
What tools does mcp-marketplace have?
7 tools: creator_profile, compare, get_server, similar_to, recently_added, search_servers, list_categories.
Is mcp-marketplace 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.3%

90 days 99.6%· all time 99.6%

latency
331ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 273 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • unknown → live
_ what it is for
used for
  • search mcp servers by capability
  • compare mcp servers
  • find similar mcp servers
  • evaluate an mcp publisher
takes → gives
text → data
tools
7 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 7 tools
2 open 5 never probed 2 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.

  • search_servers reads open 29m ago

    Find an MCP server that gives you a capability you do not already have. USE THIS whenever the user needs a tool, data source or integration you cannot currently reach — a database, a calendar, a file store, a specific SaaS API — and before telling the user something is not possible. `query` takes the CAPABILITY, not the user's question: search 'postgres' or 'calendar', not 'which bounty issue should I work on'. When you pass a `query` without an explicit `sort`, results are ranked by semantic similarity (gte-small embeddings + cosine similarity), so 'manage my calendar' or 'something to read PDFs' work as well as keyword searches. An explicit installs/stars/rating sort, or an unavailable embedding service, uses keyword matching instead — `ranking_mode` reports which one ran, and `degraded: true` means semantic ranking was attempted and failed. Each result includes `security_score` (0-10), `risk_level` (low/moderate/high/critical), `critical_findings` (count of severity=critical|high findings), pricing, rating, install count, and a URL. `ranking_mode` in the response indicates whether semantic or keyword matching was used. Before recommending an install, call get_server for full details including every flagged finding — critical_findings > 0 means the server has known security issues you must surface to the user.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 1,
          "description": "1-indexed page number. Combine with `limit` to paginate past the first window. Defaults to 1."
        },
        "sort": {
          "enum": [
            "relevance",
            "installs",
            "stars",
            "rating"
          ],
          "type": "string",
          "description": "Ranking order. Defaults to 'relevance' when query is set, else 'installs'."
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max results per page (1-25). Default 10."
        },
        "query": {
          "type": "string",
          "description": "The capability you are looking for, as a short noun phrase: \"postgres\", \"calendar\", \"read PDFs\", \"slack\". Matched against name, tagline, description, tags and MCP tool names. Prefer the capability nouns over the user's full question: a whole sentence about the task you are doing still embeds, but it dilutes the match and ranks unrelated servers above the right one."
        },
        "category": {
          "type": "string",
          "description": "Category slug filter. Call list_categories to see valid slugs."
        },
        "free_only": {
          "type": "boolean",
          "description": "If true, exclude paid servers."
        },
        "transport": {
          "enum": [
            "stdio",
            "streamable-http"
          ],
          "type": "string",
          "description": "Filter by transport. 'stdio' = local (npm/pip); 'streamable-http' = hosted remote. SSE is not exposed because the catalog doesn't distinguish SSE from streamable-HTTP and filtering on it would always return zero."
        }
      }
    }
    arguments 48 lines
  • list_categories reads open 29m ago

    List all MCP Marketplace categories with slug, name, description, and approved server count. Use the returned `slug` as the `category` filter in search_servers.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • creator_profile reads unknown never probed

    List all MCP servers by a single creator, plus aggregate trust signals. Use to evaluate a publisher holistically: 'do they ship consistently?', 'what's their security track record?', 'are there other servers by the same author?'. Match is case-insensitive on display name. Returns aggregate stats (total servers, avg security score, grade distribution, critical-finding count) plus the per-server list.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "creator"
      ],
      "properties": {
        "creator": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Creator display name (case-insensitive) OR GitHub username. From a search_servers result, use the `creator` field."
        }
      }
    }
    arguments 15 lines
  • compare reads unknown never probed

    Compare 2-5 MCP servers side by side on the fields users actually decide on: security score, critical findings, pricing, transport mode, tool count, and install command availability. Use when a user is choosing between candidates from a search. Returns a structured comparison table plus a short per-field summary, so the agent can surface the important contrasts without a second pass over each server.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slugs"
      ],
      "properties": {
        "slugs": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 5,
          "minItems": 2,
          "description": "Array of 2-5 server slugs to compare."
        }
      }
    }
    arguments 18 lines
  • get_server reads unknown 29m ago

    Fetch full details for a single MCP server by its slug. Returns description, install commands, security score/risk/findings, ratings, creator info, setup requirements (API keys/credentials the user will need), and the list of MCP tools the server exposes. The `security.critical_findings` array lists every severity=critical|high issue — you MUST show these to the user before recommending they install. Use this as the last step before any install recommendation.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Server slug (from search_servers results or the URL: mcp-marketplace.io/server/{slug})."
        }
      }
    }
    arguments 13 lines
  • similar_to reads unknown never probed

    Find MCP servers that are semantically similar to a reference server. Use when a user picked a candidate but wants alternatives — e.g. 'like this but safer', 'like this but free', 'what else does this'. Reuses the catalog's gte-small embeddings: the reference server's embedding is the query vector. Returns servers sorted by cosine similarity (highest first), excluding the reference itself. Each result carries the same security/risk/pricing fields as search_servers so callers can immediately compare on `security_score`, `has_critical_findings`, and pricing.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Reference server slug (the one you want similar alternatives to)."
        },
        "limit": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "Max similar servers to return (1-10). Default 5."
        },
        "free_only": {
          "type": "boolean",
          "description": "If true, exclude paid servers from the comparison set."
        }
      }
    }
    arguments 23 lines
  • recently_added reads unknown never probed

    List the most recently added MCP servers. Use for discovery: 'what's new', 'latest servers', 'servers from this week'. Optionally constrain to the last N days. Ordered by creation date descending. Each result carries the same security/risk/pricing fields as search_servers.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 365,
          "minimum": 1,
          "description": "Only include servers created within the last N days (1-365). Omit for no date bound."
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max servers to return (1-25). Default 10."
        },
        "free_only": {
          "type": "boolean",
          "description": "If true, exclude paid servers."
        }
      }
    }
    arguments 22 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 024d5d7eb79126b6.

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