VendorIndex
REMOTE · MCP.VENDORINDEX.DEV
Rank vendors/libraries per use case from verified pricing, agent-friction and health.
Available components
Last scanned (10 minutes ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 444 tokens (~74/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.vendorindex.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vendorindex.dev | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 28831ebbac26eb9913b1e3081f5738f7 |
| SANs: vendorindex.dev, mcp.vendorindex.dev, *.mcp.vendorindex.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.vendorindex.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| vendorindex.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.vendorindex.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.vendorindex.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_vendors ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| use_case | string | yes | – |
| vendors | array | yes | – |
No output schema declared.
No examples provided.
get_category_ranking ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| use_case | string | – | – |
No output schema declared.
No examples provided.
get_vendor ~50
Full detail for one vendor: cited pricing (structured rates + source URL + verified date + confidence), agent-friction checks, SDKs, capabilities, portability and health signals.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor | string | yes | – |
No output schema declared.
No examples provided.
list_categories ~58
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
recommend ~69
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?'.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| limit | integer | – | – |
| use_case | string | yes | – |
No output schema declared.
No examples provided.
search_vendors ~52
Find vendors by free-text query across name, id, category and capability (e.g. 'embedding', 'soc2', 'fast_inference'). Returns matches with their categories.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the VendorIndex MCP server?
VendorIndex is a hosted endpoint at https://mcp.vendorindex.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.vendorindex.dev
claude mcp add --transport http andy-chak-vendorindex 'https://mcp.vendorindex.dev/mcp'
What is the VendorIndex MCP server?
VendorIndex is an MCP server listed in the public MCP registry as io.github.andy-chak/vendorindex. Rank vendors/libraries per use case from verified pricing, agent-friction and health. This page covers its hosted endpoint (https://mcp.vendorindex.dev/mcp).
Is the VendorIndex MCP server safe to use?
VendorIndex scores 55 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the VendorIndex MCP server expose?
VendorIndex exposes 6 tools: list_categories, get_category_ranking, recommend, get_vendor, compare_vendors, search_vendors. Their descriptions and schemas cost roughly 372 tokens of context every time the server is loaded.
Does the VendorIndex MCP server require authentication?
No. We connected to VendorIndex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VendorIndex MCP server still maintained?
VendorIndex is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.