Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Agent-first US business trust registry with neutral Trust Cards and published evidence.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
https://loppee.com/mcp/discoveryEjecuta esto en tu terminal
claude mcp add --transport http loppee https://loppee.com/mcp/discoveryPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"loppee": {
"url": "https://loppee.com/mcp/discovery"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"loppee": {
"type": "http",
"url": "https://loppee.com/mcp/discovery"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
https://loppee.com/mcp/discoveryLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con el dominio loppee.com (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Aún sin revisar; revisamos los endpoints por turnos
Aún sin revisar; revisamos los endpoints por turnos
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
El repo de GitHub cambió por última vez –, y la última versión (0.1.4) llegó al registro hace 41 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, DepTime
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
What changed in a Python library, in which release, and what replaces it. Answered locally.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Public metadata for Loppee's narrow, no-auth MCP discovery surface.
https://loppee.com/mcp/discoverycom.loppee/loppeeConfigure the URL above as a remote HTTP MCP server in a compatible client. This repository does not contain credentials and does not require an API key.
Add Loppee to Claude prefills Claude's custom-connector dialog. Claude still asks the signed-in user to review and confirm the name and URL; the link does not publish a directory listing or grant permissions.
The canary and directory-review packet is in distribution/claude-connectors-directory.md.
Copy the following official Cursor MCP install link into a browser with Cursor installed. Cursor shows the decoded remote-server configuration and asks the user to confirm before installation:
cursor://anysphere.cursor-deeplink/mcp/install?name=loppee&config=eyJ1cmwiOiJodHRwczovL2xvcHBlZS5jb20vbWNwL2Rpc2NvdmVyeSJ9
The decoded configuration is exactly:
{
"url": "https://loppee.com/mcp/discovery" }
For manual or project setup, use mcp.json. The candidate Cursor Marketplace manifest is .cursor-plugin/plugin.json. Neither file contains an account, header, credential, key, or local command. The Marketplace preflight is in distribution/cursor-marketplace.md.
The metadata-only Agent Plugins Bundle source is in clawhub/loppee-discovery. It contains no skill, runtime code, credential, header, key, customer data, owner tool, write tool, or location input.
The current ClawHub CLI incorrectly requires a native openclaw.plugin.json from compatible bundles. Loppee will preserve the narrower Agent Plugins Bundle instead of changing it into a native plugin or publishing it as a Skill. The live admission blocker and reproduction are tracked in openclaw/clawhub#3513. See distribution/openclaw-clawhub.md for the verified package boundary and publication gate.
The endpoint exposes exactly five read-only named-business research tools:
| Tool | Purpose |
|---|---|
lookup_business | Find pay-independent exact or genuine-prefix matches for a named business. |
get_trust_card | Read the published Trust Card for an identified Loppee business. |
get_business_reviews | Read paginated public reviews and their published disclosures. |
explain_recommendation | Read the published recommendation basis for an identified business. |
compare_businesses | Compare two to twenty identified published Loppee businesses. |
Every tool is declared read-only, non-destructive, and closed-world. This surface exposes no category discovery, address or location input, pricing, checkout, customer account, business-owner, write, or Back Office authority.
Loppee Personal, authenticated consumer MCP, Loppee Business, and Back Office are separate products with different authorization boundaries. They are not published through this repository.
server.json records published version 0.1.4 of the existing com.loppee/loppee Official MCP Registry listing (published 2026-09-26T13:41:56.310498Z, the latest version). It changed metadata only: the source repository (https://github.com/loppee-ai/loppee-mcp, after the GitHub owner rename from 4dwebspro-cell to loppee-ai) and agent_docs_url. The /mcp/discovery remote, tools and policies are unchanged from 0.1.3 (published 2026-08-24T18:33:32.121626Z), which the Registry still reports as active. Versions 0.1.0 through 0.1.2 are retained as deprecated history. Registry versions are immutable after publication.
repository links this public metadata repositoryStarting with 0.1.4, the manifest's repository field intentionally points to this public repository (https://github.com/loppee-ai/loppee-mcp, stable GitHub repository id 1345142388). Versions 0.1.0–0.1.3 omitted the field because the Registry schema describes repository as the server's source code, and Loppee's production source repository is private. We now link this repository deliberately: it is the canonical, public, inspectable home of the listing's metadata, connection documentation and security contact, and the stable repository id lets clients detect a deleted-and-recreated repository. It does not contain, and does not claim to contain, the server implementation.
Official MCP Registry publication and GitHub MCP Registry curation are separate gates. Loppee's GitHub Registry onboarding request was submitted on 2026-08-28; submission is not inclusion. See distribution/github-mcp-registry-onboarding.md for the public request and the remaining verification gate.
Before any future Registry release or downstream directory submission, Loppee validates server.json with the official mcp-publisher; checks the live MCP initialize capabilities, tools/list, resources/list, and prompts/list; verifies the exact five-tool catalog and annotations with no resource or prompt capability; and exercises the read-only tools. Those release checks run from Loppee's private product repository and CI; no backend source, credentials, workflows, or operational runbooks are published here.
The 0.1.3 production canary completed at 2026-08-24T18:36:20Z on build e09c360f1d29269a72a1d9e272b1ead29c101c0e: exactly five tools were listed, resources, resource templates, and prompts were unsupported, all five tool calls succeeded, the public-output privacy scan and text/structured-content parity checks passed, and anonymous access to the separate /mcp surface returned 401.
This public repository intentionally contains metadata and documentation only. It does not contain the Loppee backend, private application source, scripts, workflows, secrets, credentials, or customer data.
No LICENSE file is included. Public visibility does not grant an open-source license.