Ext Ops Panel
Open dashboard
Comparison

scalekit-mcp-auth vs Tailscale RMCP

scalekit-mcp-auth is a plugin bundle for AI coding tools published by scalekit-inc. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Tailscale RMCP is an MCP server published by dinglebear.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplacescalekit-mcp-authTailscale RMCP
Claude Code: claude-plugins-community Listed
Version: 1.3.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.4
Downloads/month (npm): 226
Downloads/week (npm): 50
Forks (GitHub): 0
Stars (GitHub): 5
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

scalekit-mcp-auth vs Tailscale RMCP
Factscalekit-mcp-authTailscale RMCP
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)5 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.scalekit.com)Remote server (ts.dinglebear.ai/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 1
Hooks it runs (differs)1Not published
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/scalekit-inc/claude-code-authstackgithub.com/dinglebear-ai/rtailscale
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 32 h ago, requires a keyNot responding since 2026-10-15

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

scalekit-mcp-auth

In its own words, on Claude Code: claude-plugins-community:

Secure MCP servers with OAuth 2.1, token introspection, dynamic client registration, and CIMD so AI agents can call your MCP tools with verified identities

Tailscale RMCP

In its own words, on Official MCP Registry:

Tailscale device, route, DNS, key, user, and ACL management over MCP and CLI.

How to run each

scalekit-mcp-auth As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install scalekit-mcp-auth@claude-community

Tailscale RMCP As a remote MCP server

Claude Code
claude mcp add --transport http rtailscale https://ts.dinglebear.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: TAILSCALE_API_KEY (secret), Authorization header

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

Only the endpoint of scalekit-mcp-auth responded at the last daily 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 scalekit-mcp-auth publish no settings it asks for, so we do not compare settings.

What it can do: scalekit-mcp-auth · What it can do: Tailscale RMCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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