Plugged.in Proxy vs io.github.Philongevity/phi-longevity-prism
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.Philongevity/phi-longevity-prism is an MCP server published by Philongevity. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. 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 |  Plugged.in Proxy |  io.github.Philongevity/phi-longevity-prism |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b7c32590b270 Forks (GitHub): 29 Pulls (Docker Hub): 36 621 Stars (Docker Hub): 3 Stars (GitHub): 139 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.2 Downloads/month (npm): 792 Downloads/week (npm): 564 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.7.2 Downloads/month (npm): 792 Downloads/week (npm): 564 Forks (GitHub): 0 Stars (GitHub): 0 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 | Plugged.in Proxy | io.github.Philongevity/phi-longevity-prism |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 139 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 36 621 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 29 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-06 |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/veriteknik/pluggedin-mcp-proxy | github.com/philongevity/phi-mcp-server |
| Changes in the last 7 days (differs) | 0 | 11 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 13 h ago |
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
Plugged.in Proxy
A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.
io.github.Philongevity/phi-longevity-prism
Every doctor, your complete record: connect your patient portals or upload records from any doctor.
How to run each
Plugged.in Proxy As a local MCP server: Docker image
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxyRequires: PLUGGEDIN_API_KEY (secret)
io.github.Philongevity/phi-longevity-prism As a remote MCP server
claude mcp add --transport http phi-longevity-prism https://philongevity.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.Philongevity/phi-longevity-prism has a remote endpoint we check. How we check endpoints
Tools each declares
Only Plugged.in Proxy has
pluggedin_ask_knowledge_basepluggedin_delete_notificationpluggedin_discover_toolspluggedin_list_notificationspluggedin_mark_notification_donepluggedin_send_notification
Only io.github.Philongevity/phi-longevity-prism has
check_care_gapsexplain_my_lab_resultsfull_prism_reportget_job_resultget_lab_analysisget_methodologyget_my_medical_recordshow_to_get_started_for_my_ownerlist_supported_biomarkersprepare_for_my_appointmentquick_checksample_prism_report
Show the remaining 1
start_lab_analysis
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.Philongevity/phi-longevity-prism as of 2026-10-30). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of io.github.Philongevity/phi-longevity-prism publish no settings it asks for, so we do not compare settings.
What it can do: Plugged.in Proxy · What it can do: io.github.Philongevity/phi-longevity-prism · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.