← All servers

L

loe-exposure

connects

rxfinder.ai

Drug patent expiries ranked by the Medicare Part D spending exposed to them

https://rxfinder.ai/mcpWebsiteNo authMCP 2024-11-05v1.0.0last checked 3 Nov 2026spoke MCP on 100% of 89 checks (30 days)initialize in 68 ms

Last checked 3 Nov 2026

✓Answered the MCP handshake (MCP 2024-11-05)
✓Auth detected: No auth
✓Lists 1 tool
✓No blockers or warnings
✓Spoke MCP on 89 of 89 checks (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http loe-exposure https://rxfinder.ai/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://rxfinder.ai/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://rxfinder.ai/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "mcpServers": {
    "loe-exposure": {
      "url": "https://rxfinder.ai/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "servers": {
    "loe-exposure": {
      "type": "http",
      "url": "https://rxfinder.ai/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 3 Nov 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 1 tools listable

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

No server card

Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.

Tools

loss_of_exclusivity_exposure

Contract history

19 Sep 2026v1.0.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Route it through the gateway

Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.

Add to my gateway

Own this server?

Sign in to claim this listing by proving control of its host.

Sponsor this listing

Pins it in a sponsor slot on the directory front page for 30 days, labelled Sponsored.

Sign in to sponsor · $59 / 30 days

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/loe-exposure/badge.svg)](https://mcpi.app/servers/loe-exposure)