Ext Ops Panel
Open dashboard
Comparison

Plugged.in Proxy vs Oura Ring

Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). Oura Ring is an MCP server published by AntVsl. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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

Where each is published
MarketplacePlugged.in ProxyOura Ring
Docker MCP Catalog Listed
Version: sha256:b7c32590b270
Forks (GitHub): 30
Pulls (Docker Hub): 36 074
Stars (Docker Hub): 3
Stars (GitHub): 137
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.2
Downloads/month (PyPI): 266
Downloads/week (PyPI): 39
Forks (GitHub): 1
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

Plugged.in Proxy vs Oura Ring
FactPlugged.in ProxyOura Ring
Marketplaces that list it11
Stars (GitHub) (differs)137 (better)0 (worse)
Pulls (Docker Hub) (differs)36 074No figure on Docker Hub
Forks (GitHub) (differs)30 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/pluggedin-mcp-proxy)On your machine (my-oura-mcp)
Transportstdiostdio
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 19, secrets among them: 2
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/veriteknik/pluggedin-mcp-proxygithub.com/antvsl/oura_mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

In its own words, on Docker MCP Catalog:

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.

Oura Ring

In its own words, on Official MCP Registry:

Sleep, readiness, HRV, resting heart rate, activity and stress from your Oura Ring

How to run each

Plugged.in Proxy As a local MCP server: Docker image

Claude Code
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-proxy

Requires: PLUGGEDIN_API_KEY (secret)

Oura Ring As a local MCP server: PyPI package

Claude Code
claude mcp add --env "OURA_CLIENT_SECRET=<YOUR_OURA_CLIENT_SECRET>" --env "OURA_MCP_TOKEN=<YOUR_OURA_MCP_TOKEN>" --transport stdio oura-mcp -- uvx my-oura-mcp

Requires: OURA_CLIENT_SECRET (secret), OURA_MCP_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of Oura Ring publish no list of tools, so we do not compare tools.

Settings each asks for

Only Plugged.in Proxy asks for

  • PLUGGEDIN_API_BASE_URL
  • PLUGGEDIN_API_KEY (secret)

Only Oura Ring asks for

  • OURA_API_MODE
  • OURA_CLIENT_ID
  • OURA_CLIENT_SECRET (secret)
  • OURA_MCP_TOKEN (secret)
  • OURA_OAUTH_ALLOWED_REDIRECT_ORIGINS
  • OURA_PUBLIC_URL
  • OURA_REDIRECT_URI
  • OURA_TOKEN_STORE
  • OURA_TZ

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Plugged.in Proxy · What it can do: Oura Ring · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built