Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Same link preview data as link-preview-api, ~1/3 the price via a shared cache.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
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:
https://link-preview-cache-api.onrender.com/mcpRun this in your terminal
claude mcp add --transport http link-preview-cache-api https://link-preview-cache-api.onrender.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"link-preview-cache-api": {
"url": "https://link-preview-cache-api.onrender.com/mcp"
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"link-preview-cache-api": {
"type": "http",
"url": "https://link-preview-cache-api.onrender.com/mcp"
}
}
}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:
https://link-preview-cache-api.onrender.com/mcpMenu 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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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
The registry name was verified with the GitHub account cmondillo, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.
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.
In the same category: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
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
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.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
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.
A portfolio of small, single-purpose paid services sold directly to AI agents — no human checkout flow, no dashboard login, no subscription. An agent calls the API, gets an HTTP 402 Payment Required quote, pays a few cents in USDC, and gets its answer. Fully automatic on both sides.
Each service lives in its own self-contained folder under projects/ and follows the same pattern:
api/app/mcp_server.py) — the same product, the same price, a second interface for coding agents that discover tools over MCP rather than raw HTTP.| Project | What it sells | Status |
|---|---|---|
link-preview-api | Pay-per-call URL metadata (Open Graph/title/description/image) extraction | Live on Base mainnet, earning real USDC: https://link-preview-api-z4nf.onrender.com |
content-moderation-api | Pay-per-call profanity/explicit-content detection with redaction, sold over both HTTP and MCP | Live on Base mainnet, earning real USDC: https://content-moderation-api-hhy1.onrender.com |
link-preview-cache-api | Same product as link-preview-api, ~⅓ the price — backed by a shared cache. First instance of a general "x402 cache" pattern | Live on Base mainnet, earning real USDC: https://link-preview-cache-api.onrender.com |
projects/ /: its own code, tests, Dockerfile, deploy config, and README. Nothing product-specific is shared between projects.api/ — the paid service itselfautomation-client/ — a sample agent that pays for and consumes itdeploy/ — ready-to-use deploy configs (Render/Fly/etc.)README.md — the business case, architecture, and exact steps to take it from "runs on my machine" to "earning money"LISTING.md — the marketplace/directory listing copy, ready to publishscripts/ holds portfolio-level *publishing* tooling — not product code, reused across every project the same way (e.g. submitting a new tool to x402-list.com's API). See PUBLISHING.md for the full playbook: what's genuinely automatic, what's scripted, and what stays a deliberate manual step and why.