_ registry / mcp streamable-http · checked 1h ago

vendorindex

https://mcp.vendorindex.dev

Registry code: 9b4b4bb20aefc29a

api record

VendorIndex is the reference an agent consults to pick a vendor/library/service. Rankings are deterministic and per-use-case, computed from verified (cited) pricing, agent-friction and health — rank is never for sale, and internet sentiment never affects it. Start with list_categories to find valid ids, then get_category_ranking or recommend.

endpoint
https://mcp.vendorindex.dev/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 vendorindex live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is vendorindex free to use?
Yes — the hub reached it with no key and no payment.
What tools does vendorindex have?
6 tools: recommend, compare_vendors, search_vendors, list_categories, get_category_ranking, get_vendor.
Is vendorindex 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
411ms

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.

  • list_categories open 1h ago

    List every vendor category VendorIndex covers (e.g. transactional-email, llm-models, embeddings-apis, llm-gateways), each with its use cases and vendor count. Call this first to discover valid category and use_case ids.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_category_ranking open 1h ago

    Get the ranked vendors for a category, scored per use case (deterministic, from verified pricing + agent-friction + health). Omit use_case to get the ranking for every use case in the category. Returns each vendor's weighted total and per-dimension scores.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category"
      ],
      "properties": {
        "category": {
          "type": "string"
        },
        "use_case": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • get_vendor open 1h ago

    Full detail for one vendor: cited pricing (structured rates + source URL + verified date + confidence), agent-friction checks, SDKs, capabilities, portability and health signals.

    mcp-tool

    {
      "type": "object",
      "required": [
        "vendor"
      ],
      "properties": {
        "vendor": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • recommend unknown never probed

    Recommend the top vendors for a specific category + use case, with the reasoning (which dimensions drove the pick). Best when an agent needs a single answer to 'what should I use for X?'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category",
        "use_case"
      ],
      "properties": {
        "limit": {
          "type": "integer"
        },
        "category": {
          "type": "string"
        },
        "use_case": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • compare_vendors unknown never probed

    Side-by-side comparison of several vendors for one category + use case: weighted totals, per-dimension scores and health trend. Use for head-to-head questions.

    mcp-tool

    {
      "type": "object",
      "required": [
        "vendors",
        "category",
        "use_case"
      ],
      "properties": {
        "vendors": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "minItems": 2
        },
        "category": {
          "type": "string"
        },
        "use_case": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • search_vendors unknown never probed

    Find vendors by free-text query across name, id, category and capability (e.g. 'embedding', 'soc2', 'fast_inference'). Returns matches with their categories.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 12 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 9b4b4bb20aefc29a.

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