VendorIndex

Rank vendors/libraries per use case from verified pricing, agent-friction and health.

Should I use this

Quality & Safety

B
Description quality
83%
Schema completeness
72%
Naming quality
93%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (2)

  • LOWTool 'recommend' description lacks action verbin recommend
  • LOWTool 'compare_vendors' description lacks action verbin compare_vendors

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~526Tokens (tool definitions)
~417 BTypical response size
Minimal attention impact (0.41% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "vendorindex": {
      "url": "https://mcp.vendorindex.dev/mcp"
    }
  }
}

Remote endpoints

https://mcp.vendorindex.dev/mcpstreamable-http

What it can do

Tool inventory

Tools (6)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢list_categories

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_category_ranking(category, use_case)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string"
    },
    "use_case": {
      "type": "string"
    }
  },
  "required": [
    "category"
  ],
  "additionalProperties": false
}
⚪recommend(category, use_case, limit)

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?'.

Input Schema

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string"
    },
    "use_case": {
      "type": "string"
    },
    "limit": {
      "type": "integer"
    }
  },
  "required": [
    "category",
    "use_case"
  ],
  "additionalProperties": false
}
🟢get_vendor(vendor)

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

Input Schema

{
  "type": "object",
  "properties": {
    "vendor": {
      "type": "string"
    }
  },
  "required": [
    "vendor"
  ],
  "additionalProperties": false
}
⚪compare_vendors(vendors, category, use_case)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "vendors": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 2
    },
    "category": {
      "type": "string"
    },
    "use_case": {
      "type": "string"
    }
  },
  "required": [
    "vendors",
    "category",
    "use_case"
  ],
  "additionalProperties": false
}
🟢search_vendors(query)

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

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string"
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded6 tools