Home / MCP registry index / com.finerxfinder/finerx
FineRx
com.finerxfinder/finerx in the official MCP registry.
Endpoint https://www.finerxfinder.com/mcp.
The registry describes it as: US Rx prices by pharmacy near you + free discount card; foreign-brand equivalents; 12 languages
We read its 19 tools on 2026-10-27. 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
compare_prices ui_prices find_nearby_pharmacies ui_nearby get_transfer_steps compare_basket ui_basket open_price_finder ui_suggest get_savings_card email_savings_card search_drugs get_drug get_dataset_info get_prescription_options find_us_equivalent find_us_equivalents ui_equivalent foreign_brands_for_drug
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-finerxfinder-finerx)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.