Rank vendors/libraries per use case from verified pricing, agent-friction and health.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http vendorindex https://mcp.vendorindex.dev/mcp
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.
| Argument | Type | Description |
|---|---|---|
| vendors* | array | |
| category* | string | |
| use_case* | string |
{
"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
}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.
| Argument | Type | Description |
|---|---|---|
| category* | string | |
| use_case | string |
{
"type": "object",
"required": [
"category"
],
"properties": {
"category": {
"type": "string"
},
"use_case": {
"type": "string"
}
},
"additionalProperties": false
}Full detail for one vendor: cited pricing (structured rates + source URL + verified date + confidence), agent-friction checks, SDKs, capabilities, portability and health signals.
| Argument | Type | Description |
|---|---|---|
| vendor* | string |
{
"type": "object",
"required": [
"vendor"
],
"properties": {
"vendor": {
"type": "string"
}
},
"additionalProperties": false
}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.
No arguments.
{
"type": "object",
"properties": {},
"additionalProperties": false
}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?'.
| Argument | Type | Description |
|---|---|---|
| limit | integer | |
| category* | string | |
| use_case* | string |
{
"type": "object",
"required": [
"category",
"use_case"
],
"properties": {
"limit": {
"type": "integer"
},
"category": {
"type": "string"
},
"use_case": {
"type": "string"
}
},
"additionalProperties": false
}Find vendors by free-text query across name, id, category and capability (e.g. 'embedding', 'soc2', 'fast_inference'). Returns matches with their categories.
| Argument | Type | Description |
|---|---|---|
| query* | string |
{
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string"
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 3, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.