io.github.itsryanarmani/peptideclinic vs FHIR MCP Server
io.github.itsryanarmani/peptideclinic is an MCP server published by itsryanarmani. Marketplaces we read that list it: 1 (Official MCP Registry). FHIR MCP Server is an MCP server published by wso2. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.itsryanarmani/peptideclinic |  FHIR MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.11.0 Downloads/month (PyPI): 456 Downloads/week (PyPI): 483 Forks (GitHub): 59 Stars (GitHub): 137 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.11.0 Downloads/month (PyPI): 456 Downloads/week (PyPI): 483 Forks (GitHub): 59 Stars (GitHub): 137 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.itsryanarmani/peptideclinic | FHIR MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 137 |
| Forks (GitHub) (differs) | No figure on GitHub | 59 |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | Remote server (peptideclinic.fyi/mcp) | On your machine (fhir-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/itsryanarmani/directory | github.com/wso2/fhir-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-07 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 21 h ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.itsryanarmani/peptideclinic
Find a licensed peptide clinic, in person or by telehealth.
FHIR MCP Server
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
How to run each
io.github.itsryanarmani/peptideclinic As a remote MCP server
claude mcp add --transport http peptideclinic https://peptideclinic.fyi/mcpFHIR MCP Server As a local MCP server: PyPI package
claude mcp add --env "FHIR_SERVER_BASE_URL=<YOUR_FHIR_SERVER_BASE_URL>" --transport stdio fhir-mcp-server -- uvx fhir-mcp-serverRequires: FHIR_SERVER_BASE_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.itsryanarmani/peptideclinic has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.itsryanarmani/peptideclinic publish no settings it asks for, so we do not compare settings.
What it can do: io.github.itsryanarmani/peptideclinic · What it can do: FHIR MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.