Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Loppee
Overview
Description from the maker (original English)
Agent-first US business trust registry with neutral Trust Cards and published evidence.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://loppee.com/mcp/discoveryRun this in your terminal
claude mcp add --transport http loppee https://loppee.com/mcp/discoveryOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"loppee": {
"url": "https://loppee.com/mcp/discovery"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"loppee": {
"type": "http",
"url": "https://loppee.com/mcp/discovery"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://loppee.com/mcp/discoveryMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain loppee.com (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32398 servers in this category
- Published to the registry more recently than 50% of the other 32398 servers in this category
- Basic checks equal to or better than 100% of the other 32398 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Loppee safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.4) reached the registry 41 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, AI Deprecations
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
AI Deprecations
by aideprecations.com
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Loppee MCP
Public metadata for Loppee's narrow, no-auth MCP discovery surface.
Connect
- MCP URL:
https://loppee.com/mcp/discovery - Transport: Streamable HTTP
- Authentication: none
- Registry identity:
com.loppee/loppee - Source repository: https://github.com/loppee-ai/loppee-mcp
Configure 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.
Claude custom connector
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.
Cursor
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=eyJ1cmwiOiJodHRwczovL2xvcHBlZS5jb20vbWNwL2Rpc2NvdmVyeSJ9The 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.
OpenClaw
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.
Public tool boundary
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.
Privacy and neutrality
- The tool schemas accept no address, city, state, ZIP, coordinates, location handoff, or device-location input.
- The endpoint returns no private customer or owner data.
- Payment does not change lookup, comparison, verification, reviews, evidence, or recommendation explanation on this surface.
- Missing or unresolved records must remain unresolved rather than fabricated.
Loppee Personal, authenticated consumer MCP, Loppee Business, and Back Office are separate products with different authorization boundaries. They are not published through this repository.
Registry metadata
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.
Design note: repository links this public metadata repository
Starting 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.
Verification
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.
Links
- Website: https://loppee.com
- Agent information: https://loppee.com/agents
- Privacy: https://loppee.com/privacy
- Terms: https://loppee.com/terms
- Support: https://loppee.com/support
Source and license
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.