What did Hlido score MCP Server Templates?

MCP Server Templates scored 48/100 (FADING) in Hlido's independent, hands-on review.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

MCP Server Templates

Name: MCP Server Templates review
Item: MCP Server Templates
Rating: 48
Author: Hlido Editor

Infrastructure · tested 2026-08-05 · re-test due 2026-11-05 · by the Hlido desk, not the vendor

In short: Explicitly superseded by its own successor — the docs open by telling you to migrate. Reviewed as what it now is: a legacy package with a clear exit path.

4 PASS · 1 FAIL of 5 public-surface claims

Visit MCP Server Templates → scorecard.json

Quick answer

MCP Server Templates scores 48/100 (FADING) on Hlido’s independent, hands-on test (reviewed 2026-08-05). FADING (48) because the project itself declares it superseded on the first line of its own documentation and directs readers to MCP Platform.

Hlido Editor · 2026-08-05

MCP Server Templates offers Docker-powered, zero-configuration deployment of Model Context Protocol servers with a CLI and a template library. The dominant fact about it is announced by the project before anything else: the documentation opens with "This project has evolved into MCP Platform", labels itself Legacy Documentation, and gives the migration in two lines — `pip uninstall mcp-templates && pip install mcp-platform`, then replace `mcpt` with `mcpp` in your commands. We score it as what it is today rather than what it was, and a superseded package is a poor choice for new work no matter how sound the original design. That said, the deprecation is handled about as well as deprecations get: the successor is named, linked and documented; the migration is two commands rather than a rewrite; the legacy docs remain published instead of being deleted out from under existing users; and the naming change is explained rather than just imposed. Some content is visibly stale — a features section still headed "Mid-August 2025 Release" — and the modest repository signals (21 stars, 5 forks on the captured page) suggest this never reached wide adoption before moving on. Anyone landing here should follow the project's own advice and go to MCP Platform; the reason to record this entry at all is so that agents and people who find the legacy package know it is legacy.

Why FADING

FADING (48) because the project itself declares it superseded on the first line of its own documentation and directs readers to MCP Platform. The deprecation is handled well — successor named and linked, two-command migration, legacy docs left in place — which keeps it from scoring lower, but a package whose maintainer says to install something else cannot be recommended for new work. Confidence is medium rather than low here: the central finding is stated unambiguously by the vendor.

Public-surface checklist

PASS Homepage loads (required)
PASS Primary value prop (required) — 'Production-ready MCP server templates for instant, zero-configuration deployment'
PASS Cta present (required) — Installation and quick-start commands present
PASS Pricing or access — Open source self-hosted, with a commercial managed option (MCP Platform)
FAIL Evidence or demo — Documentation only; repository signals modest and content partly stale

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-a9c1e8647b3d225e-data-everything-github-io). Our own captures — not vendor marketing material.

MCP Server Templates — run screenshot 1 (home.png) — home.png

MCP Server Templates — run screenshot 2 (page_this-project-has-evolved-into-mcp-platform.png) — page_this-project-has-evolved-into-mcp-platform.png

MCP Server Templates — run screenshot 3 (page_q_.png) — page_q_.png

MCP Server Templates — run screenshot 4 (pagegetting-started_installation_.png) — pagegetting-started_installation_.png

What it does well

Deprecation is announced clearly and immediately rather than left for users to discover
Successor (MCP Platform) is named, linked, and separately documented
Migration is genuinely two commands, not a rewrite: uninstall/install, then mcpt → mcpp
Legacy documentation is left published rather than deleted, so existing users are not stranded
The rename is explained (better reflects the platform's capabilities) rather than imposed silently
Original design is sound — Docker-powered zero-configuration deployment with a real CLI and template library

What it fails at

Superseded by MCP Platform — the vendor's own first instruction is to migrate away
Content is visibly stale, including a features section still headed 'Mid-August 2025 Release'
Modest repository signals (21 stars, 5 forks on the captured page) suggest limited adoption before the move
No security or maintenance commitment stated for the legacy package now that the successor exists
Anything learned here has to be re-learned against MCP Platform's documentation

Red flags

[object Object]

Best for

Existing mcp-templates users who need the legacy reference while migrating
Anyone tracing why a `mcpt` command in an old runbook no longer matches current documentation

Not recommended for

New projects — use MCP Platform, as the vendor instructs
Production deployments needing an actively maintained package with a security commitment
Anyone evaluating MCP deployment tooling for the first time

Pricing & access

Pricing findable on the public surfacePASS Open source self-hosted, with a commercial managed option (MCP Platform) (tested 2026-08-05)

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-05.

Related agents

Agent relevance

CLI MCP

Agentic-Commerce Readiness 51/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

A CLI and templates for deploying MCP servers — infrastructure an agent ends up running behind, not a surface an agent calls. New integrations should target MCP Platform instead.

Agent-friendly score: 4/10

Evidence

Project declares it has evolved into MCP Platform, on the first line of its documentation — source (2026-08-05) verified
Documentation is explicitly labelled Legacy Documentation — source (2026-08-05) verified
Two-command migration: pip uninstall mcp-templates && pip install mcp-platform, then mcpt → mcpp — source (2026-08-05) verified
Docker-powered zero-configuration MCP server deployment with a CLI and template library — source (2026-08-05) verified
Stale content retained, including a 'Mid-August 2025 Release' features heading — source (2026-08-05) verified

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-05

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/data-everything-mcp-server-templates.svg)](https://hlido.eu/check/?agent=data-everything-mcp-server-templates)

HTML

<a href="https://hlido.eu/check/?agent=data-everything-mcp-server-templates"><img src="https://hlido.eu/badge/data-everything-mcp-server-templates.svg" alt="Hlido trust score"></a>