VendorIndex
io.github.andy-chak/vendorindexandy-chakstreamable-httpv0.1.0Scanned
Rank vendors/libraries per use case from verified pricing, agent-friction and health.
6 tools: 1 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 1Claude Code: ask
recommendRecommend the top vendors for a specific category + use case, with the reasoning (which dimensions drove the pick).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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?'.
Only reads 5Show 5 read-only tools
compare_vendorsSide-by-side comparison of several vendors for one category + use case: weighted totals, per-dimension scores and health trend.No findings
Why it is in this group
- The name "compare_vendors" says "compare": a word for reading.
Description, as the server wrote 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.
get_category_rankingGet the ranked vendors for a category, scored per use case (deterministic, from verified pricing + agent-friction + health).No findings
Why it is in this group
- The name "get_category_ranking" says "get": a word for reading.
Description, as the server wrote it 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.
get_vendorFull detail for one vendor: cited pricing (structured rates + source URL + verified date + confidence), agent-friction checks, SDKs, capabilities, portability and health signals.Reads text others writeNo findings
Why it is in this group
- The name "get_vendor" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it Full detail for one vendor: cited pricing (structured rates + source URL + verified date + confidence), agent-friction checks, SDKs, capabilities, portability and health signals.
list_categoriesList every vendor category VendorIndex covers (e.g.No findings
Why it is in this group
- The name "list_categories" says "list": a word for reading.
Description, as the server wrote it 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.
search_vendorsFind vendors by free-text query across name, id, category and capability (e.g.No findings
Why it is in this group
- The name "search_vendors" says "search": a word for reading.
Description, as the server wrote it Find vendors by free-text query across name, id, category and capability (e.g. 'embedding', 'soc2', 'fast_inference'). Returns matches with their categories.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http vendorindex https://mcp.vendorindex.dev/mcpclaude mcp add --transport http vendorindex https://mcp.vendorindex.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__vendorindex__list_categories",
"mcp__vendorindex__get_category_ranking",
"mcp__vendorindex__get_vendor",
"mcp__vendorindex__compare_vendors",
"mcp__vendorindex__search_vendors"
],
"ask": [
"mcp__vendorindex__recommend"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vendorindex. Review it before you use it.
Capability tags behind 1 rule
- mcp__vendorindex__get_vendor untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/io.github.andy-chak/vendorindex/verify?hash=187998ea4ad1971994048666c8c5adfee3cfd68d52cc47111a2e7c97413cb6e5" | jq -e '.changed == false'Pinned hash 187998ea4ad1, from Nov 3, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.andy-chak/vendorindex/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.andy-chak/vendorindex)Source: MCP Registry · repository. Synced Nov 3, 2026, 13:17 UTC.