MCP.Market

FineRx MCP server

online · 100% uptime
by finerxfinder.com·com.finerxfinder/finerx·v2.2.0

US Rx prices by pharmacy near you + free discount card; foreign-brand equivalents; 12 languages

A86/100grade A
What users say
No reviews yet
Be the first
Safety scan
A86/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed FineRx yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

FineRx tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How FineRx compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 72% of 48,243 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
632 ms
faster than 25% of 30,027 servers

Release history: 3 versions in the registry since 2026-09-09, latest 2026-10-03, typically one every 13 days.

Install FineRx in Claude Code, Cursor or VS Code

claude mcp add --transport http finerx https://www.finerxfinder.com/mcp
Add to Cursor

Grade history

  • 2026-10-02restoreB → Ascore 86: Write-action tools reachable without authentication

FineRx: common questions

Is FineRx MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the FineRx safety report
How do I install FineRx?
It runs remotely at www.finerxfinder.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does FineRx need an API key?
Yes. The registry entry asks for FINERX_API_KEY.
Is FineRx maintained?
The last commit was 44 days ago (2026-09-23). The latest release is v2.2.0.
Is FineRx up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does FineRx compare with other MCP servers?
safety score 86/100 (higher than 72% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 632 ms (faster than 25% of 30,027 servers). Full comparison.