Home / MCP registry index / com.kongreviews/kongreviews
Kong Reviews
com.kongreviews/kongreviews in the official MCP registry.
Endpoint https://kongreviews.com/mcp.
The registry describes it as: Pick a tech stack from a PRD and see what it costs now and at scale, after startup perks.
We read its 34 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
recommend_stack compare_architectures list_vendors list_capabilities search_directory search_showcase get_pricing estimate_cost compare_vendors check_fit project_stack find_cost_cliffs find_perks extract_requirements plan_stack evaluate_change detect_stack audit_stack plan_migration diff_stack price_change accept_change save_stack get_project_context list_saved_stacks get_saved_stack get_build_pack record_setup_progress check_build update_saved_stack record_bills explain_bill delete_saved_stack delete_account
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-kongreviews-kongreviews)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.