MedRecPro Drug Label Server

Name: MedRecPro Drug Label Server
Author: chriserikbarnes

by chriserikbarnesversion 1.0.3i★ –iRuns in the cloud

Registry namecom.medrecpro/drug-label-server

Install

Overview

Description from the maker (original English)

Search and export FDA drug labels by brand name, generic ingredient, or UNII code.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Clinics & health

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://www.medrecpro.com/mcp

Run this in your terminal

claude mcp add --transport http drug-label https://www.medrecpro.com/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "drug-label": {
      "url": "https://www.medrecpro.com/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "drug-label": {
      "type": "http",
      "url": "https://www.medrecpro.com/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://www.medrecpro.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain medrecpro.com (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Clinics & healthi

More stars than 0% of the other 1022 servers in this category
Published to the registry more recently than 2% of the other 1022 servers in this category
Basic checks equal to or better than 100% of the other 1022 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MedRecPro Drug Label Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.3) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Google Health MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated today

Install

FHIR MCP Server

by wso2

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 10 days ago

Install

Google Health MCP

by davidmosiah

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

Runs on your computer★ 79MITUpdated 4 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

MedRecPro MCP Server

MCP (Model Context Protocol) server for the MedRecPro application. Acts as an OAuth 2.1 gateway between MCP clients (Claude, etc.) and the MedRecPro Web API.

Version: 1.0.0 Runtime: ASP.NET Core 8.0 Production URL: https://www.medrecpro.com/mcp

Architecture

                             Azure App Service: "MedRecPro" (Windows, IIS)

+--------------------------------------------------+ | | +------------------+ | / site\wwwroot MedRecProStatic | | Claude / MCP | HTTPS | /api site\wwwroot\api MedRecPro API | | Client |------->| /mcp site\wwwroot\mcp MedRecProMCP | +------------------+ | | | +--------------------------------------------------+ v | +------------------+ v | Cloudflare | +------------------+ | (CDN/WAF/DNS) | | Azure Key Vault | +------------------+ | (medrecprovault)| +------------------+

The MCP server runs as an IIS virtual application at /mcp on the same Azure App Service as the main MedRecPro UI and API. IIS handles path-based routing to three separate ASP.NET Core processes:

Virtual Path	Physical Path	Project	Purpose
`/`	`site\wwwroot`	MedRecProStatic	UI / Static content
`/api`	`site\wwwroot\api`	MedRecPro	Web API
`/mcp`	`site\wwwroot\mcp`	MedRecProMCP	MCP Server (this project)

Endpoints

All endpoints are externally prefixed with /mcp by the IIS virtual application.

External URL	Method	Description
`/mcp`	POST	MCP Streamable HTTP transport (JSON-RPC)
`/mcp/health`	GET	Health check (returns JSON status)
`/mcp/docs`	GET	HTML technical documentation page
`/mcp/getting-started`	GET	HTML getting-started page (user-facing, for directory listing)
`/mcp/docs/images/{filename}`	GET	Serves embedded screenshot images (PNG)
`/mcp/.well-known/oauth-protected-resource`	GET	Protected Resource Metadata (RFC 9728)
`/mcp/.well-known/oauth-authorization-server`	GET	Authorization Server Metadata (RFC 8414)
`/mcp/oauth/authorize`	GET	OAuth authorization endpoint
`/mcp/oauth/token`	POST	Token exchange endpoint
`/mcp/oauth/register`	POST	Dynamic Client Registration (RFC 7591)
`/mcp/oauth/callback/google`	GET	Google OAuth callback
`/mcp/oauth/callback/microsoft`	GET	Microsoft OAuth callback

Note: GET /mcp returns HTTP 405 (Method Not Allowed). This is correct behavior. The MCP transport only accepts POST requests. For browser-accessible pages, use /mcp/docs (technical documentation) or /mcp/getting-started (user-facing guide).

Authentication Flow

1. Claude sends POST to /mcp (unauthenticated)

Server returns 401 with WWW-Authenticate header pointing to PRM
Claude fetches /mcp/.well-known/oauth-protected-resource
Claude fetches /mcp/.well-known/oauth-authorization-server
Claude registers via /mcp/oauth/register (Dynamic Client Registration)
Claude redirects user to /mcp/oauth/authorize?provider=google
User authenticates with Google/Microsoft
Provider redirects to /mcp/oauth/callback/{provider}
MCP server resolves upstream IdP email to numeric DB user ID via POST /api/users/resolve-mcp (auto-provisions user if they don't exist in the database)
MCP server issues authorization code with numeric sub claim (standard JWT name), redirects to Claude
Claude exchanges code for tokens via /mcp/oauth/token
Claude sends authenticated POST to /mcp with Bearer MCP JWT
MCP server forwards MCP JWT to MedRecPro API for each tool call (McpBearer auth scheme)

User Resolution and Auto-Provisioning

During the OAuth callback (step 9), the MCP server must map the upstream identity provider's identifier (Google sub / Microsoft GUID) to a numeric MedRecPro database user ID. The API's getEncryptedIdFromClaim() method expects a numeric NameIdentifier claim — without this resolution, all API calls would fail with 401.

How it works:

OAuthEndpoints.cs extracts email, display name, and provider from upstream IdP claims
UserResolutionService generates a temporary MCP JWT and calls POST /api/users/resolve-mcp
The API's UsersController.ResolveMcpUser() looks up the user by email:

User exists: Returns their encrypted database user ID
User doesn't exist: Auto-provisions a new user record (matching AuthController.createUserForExternalLogin() defaults: EmailConfirmed=true, Timezone="UTC", Locale="en-US", no password), then returns the encrypted ID

UserResolutionService decrypts the encrypted ID using the shared Security:DB:PKSecret via StringCipher
OAuthEndpoints.cs replaces the upstream NameIdentifier claim with the numeric database user ID
McpTokenService.normalizeClaimType() converts ClaimTypes.NameIdentifier to the standard JWT sub claim during token creation, and OutboundClaimTypeMap is cleared to prevent double-mapping
The MCP JWT is issued with the numeric user ID as the sub claim, enabling all API calls to succeed

Key architecture:

TokenForwardingHandler forwards the MCP JWT directly to the API (not the upstream Google/Microsoft token). The API's McpBearer authentication scheme validates these MCP-signed JWTs.
Both the MCP server and API share Security:DB:PKSecret from Azure Key Vault for StringCipher encryption/decryption of user IDs.
UserResolutionService uses a dedicated "MedRecProApiDirect" named HttpClient (without TokenForwardingHandler) to avoid circular token forwarding during resolution.
Claim normalization: McpTokenService normalizes .NET ClaimTypes URIs to standard JWT short names (sub, name, email, given_name, family_name) before token creation. Both JWT handlers set MapInboundClaims = false so claims retain their short names when read back. The API's ClaimHelper resolves user IDs from both ClaimTypes.NameIdentifier (cookie auth) and "sub" (MCP JWT auth).

Compiler Directives (#if DEBUG)

Route paths use compiler directives to handle IIS virtual application path stripping. This follows the same pattern as ApiControllerBase in the MedRecPro API project.

Problem: IIS strips the /mcp prefix from requests before forwarding to the app. A request to www.medrecpro.com/mcp/oauth/authorize arrives at Kestrel as /oauth/authorize. Routes must account for this.

Component	DEBUG (local dev)	RELEASE (Azure/IIS)
MCP transport	`MapMcp("/mcp")`	`MapMcp("/")`
Health check	`GET /`	`GET /health`
Documentation	`GET /mcp/docs`	`GET /docs`
Getting started	`GET /mcp/getting-started`	`GET /getting-started`
Image serving	`GET /mcp/docs/images/{filename}`	`GET /docs/images/{filename}`
OAuth group	`/mcp/oauth`	`/oauth`
Well-known metadata	`/mcp/.well-known/*`	`/.well-known/*`
PRM redirect	`/mcp/.well-known/oauth-protected-resource` redirects to SDK path	Not needed (IIS handles)

Files with compiler directives:

Program.cs - MCP transport, health check, docs, getting-started, image serving, PRM redirect
Endpoints/OAuthEndpoints.cs - OAuth route group prefix
Endpoints/OAuthMetadataEndpoints.cs - Well-known metadata paths

Config-driven (no directives needed):

OAuth callback URLs - Built from McpServer:ServerUrl at runtime
OAuth metadata document contents - Built from McpServer:ServerUrl at runtime
Protected Resource Metadata - Built from McpServer:ServerUrl at runtime

Setup Guide

Prerequisites

.NET 8.0 SDK
Azure subscription with:
App Service (Windows, IIS) - shared with MedRecPro
Key Vault (medrecprovault)
Application Insights (optional)
Cloudflare account with medrecpro.com domain
Google Cloud Console project with OAuth 2.0 credentials
Microsoft Entra ID app registration

1. Local Development Setup

Clone and restore

git clone <repo-url>

cd MedRecProMCP dotnet restore

Configure user secrets

dotnet user-secrets init

dotnet user-secrets set "McpServer:JwtSigningKey" " " dotnet user-secrets set "Jwt:Key" " " dotnet user-secrets set "Jwt:Issuer" "http://localhost:5233/mcp" dotnet user-secrets set "Jwt:Audience" "http://localhost:5233/mcp" dotnet user-secrets set "Jwt:ExpirationMinutes" "60" dotnet user-secrets set "Jwt:UpstreamTokenEncryptionKey" "<32-char-aes-key>" dotnet user-secrets set "Authentication:Google:ClientId" " " dotnet user-secrets set "Authentication:Google:ClientSecret" " " dotnet user-secrets set "Authentication:Microsoft:ClientId" " " dotnet user-secrets set "Authentication:Microsoft:ClientSecret:Dev" " " dotnet user-secrets set "Authentication:Microsoft:TenantId" " " dotnet user-secrets set "Security:DB:PKSecret" " "

Run locally

dotnet run

The server runs at http://localhost:5233. In DEBUG mode, endpoints include the /mcp prefix:

Health check: http://localhost:5233/
MCP transport: http://localhost:5233/mcp (POST only)
Documentation: http://localhost:5233/mcp/docs
Getting started: http://localhost:5233/mcp/getting-started
Screenshot images: http://localhost:5233/mcp/docs/images/{filename}
OAuth metadata: http://localhost:5233/mcp/.well-known/oauth-authorization-server

2. Azure App Service Setup

Add virtual application

In Azure Portal:

Navigate to App Service "MedRecPro" > Configuration > Path mappings
Click "+ Add virtual application or directory"
Configure:

Virtual path: /mcp
Physical path: site\wwwroot\mcp
Type: Check Application

Click Save

Key Vault secrets

Ensure the following secrets exist in Azure Key Vault (medrecprovault). These are shared with the MedRecPro API since both apps use the same Key Vault:

Secret Name	Description
`McpServer--JwtSigningKey`	JWT signing key for MCP tokens (min 32 chars)
`Jwt--Key`	JWT signing key
`Jwt--Issuer`	JWT issuer claim
`Jwt--Audience`	JWT audience claim
`Jwt--ExpirationMinutes`	Token expiration (e.g., `60`)
`Jwt--UpstreamTokenEncryptionKey`	AES encryption key for upstream tokens
`Authentication--Google--ClientId`	Google OAuth Client ID
`Authentication--Google--ClientSecret`	Google OAuth Client Secret
`Authentication--Microsoft--ClientId`	Microsoft Entra App ID
`Authentication--Microsoft--ClientSecret--Prod`	Microsoft client secret (production)
`Authentication--Microsoft--TenantId`	Azure AD Tenant ID
`Security--DB--PKSecret`	Shared encryption key for user ID encryption/decryption (must match API)

Note: Key Vault uses -- as separator. ASP.NET Core maps these to : in configuration (e.g., Jwt--Key becomes Jwt:Key).

Managed identity

The App Service must have a system-assigned managed identity with Get and List permissions on Key Vault secrets. Since the MCP virtual application shares the same App Service as the API, the existing managed identity should already have access.

3. OAuth Provider Configuration

Google Cloud Console

Go to Google Cloud Console > APIs & Services > Credentials
Edit your OAuth 2.0 Client ID
Add authorized redirect URIs:

https://www.medrecpro.com/mcp/oauth/callback/google (production)
http://localhost:5233/mcp/oauth/callback/google

Only the beginning is shown; read the rest in the repo

MedRecPro Drug Label Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Clinics & healthi

Common questions

Alternatives

Mirobody

FHIR MCP Server

Google Health MCP

README from the maker

MedRecPro MCP Server

Architecture

Endpoints

Authentication Flow

User Resolution and Auto-Provisioning

Compiler Directives (#if DEBUG)

Setup Guide

Prerequisites

1. Local Development Setup

Clone and restore

Configure user secrets

Run locally

2. Azure App Service Setup

Add virtual application

Key Vault secrets

Managed identity

3. OAuth Provider Configuration

Google Cloud Console