Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Give your agents the live web.
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.
STOPHY_API_KEY, AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"stophydotdev": {
"command": "npx",
"args": [
"-y",
"@stophy/mcp"
],
"env": {
"STOPHY_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http stophydotdev https://api.stophy.dev/mcp --header 'Authorization: Bearer {api_key}'claude mcp add stophydotdev --env STOPHY_API_KEY=your-value -- npx -y @stophy/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"stophydotdev": {
"url": "https://api.stophy.dev/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"stophydotdev": {
"command": "npx",
"args": [
"-y",
"@stophy/mcp"
],
"env": {
"STOPHY_API_KEY": "your-value"
}
}
}
}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": {
"stophydotdev": {
"type": "http",
"url": "https://api.stophy.dev/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"stophydotdev": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@stophy/mcp"
],
"env": {
"STOPHY_API_KEY": "your-value"
}
}
}
}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.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.
stophy_search_endpointsStart here. Send plain words for the data you want. Returns endpoints with their inputs, filters and cost, ready for stophy_call. Costs nothing.
stophy_describe_endpointOptional. Returns an endpoint's full inputs, filter notes, an example and output fields. Costs nothing.
stophy_callSend an endpoint id and its input. Returns the data and what the call cost.
stophy_scrapeScrape any public web page as markdown, HTML, links, a screenshot or JSON. 1 credit for any page, however it is reached. json with a schema or a prompt, summary and highlights add 4 credits each when they return something. CSS rules and attributes add nothing. A PDF adds 1 credit
stophy_searchSearch the web, news and images in one call. 2 credits per 10 results from each source, plus 1 credit for each web re...
stophy_mapScrape the list of pages on a website. 1 credit per call. Input: url, search, sitemap, includeSubdomains, ignoreQuery...
stophy_crawlCrawl a website in the background. 1 credit a page, however it is reached. A page that cannot be read costs nothing. ...
stophy_extractPull the fields you name from any public page as JSON, each checked against the page. $0.01 for most pages: the page'...
stophy_signupNeeds no key. Returns a claimUrl for your person to approve and a secret code. Call it again with the code to collect the key once they approve. Returns at once, so call again later.
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 stophydotdev, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 303 ms (HTTP 200)
No sign-in needed
Read 9 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.
You need to fill in: STOPHY_API_KEY, Authorization
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.3.0) reached the registry 4 days 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, zanadir
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.
Find what a repository's CI is missing, and which security checks cannot fail the build.
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.
Give your agents the live web over MCP. Your agent reaches every Stophy endpoint through three tools.
Most apps connect to the hosted server directly, with nothing to install.
| URL | How you connect | What your agent can use |
|---|---|---|
https://api.stophy.dev/mcp | No key | The endpoints marked keyless: true in the endpoint list, within a free allowance |
https://api.stophy.dev/mcp | Authorization: Bearer header | Every endpoint |
https://mcp.stophy.dev/mcp | Sign in with your browser | Every endpoint |
Get an API key at stophy.dev/signup.
In Claude on the web, Desktop or mobile, open Customize > Connectors, choose Add custom connector, and paste https://mcp.stophy.dev/mcp. Sign in when Claude asks.
To sign in with your browser, add the server, then run /mcp and choose Authenticate:
claude mcp add --transport http stophy https://mcp.stophy.dev/mcp
To use an API key:
claude mcp add --transport http stophy https://api.stophy.dev/mcp --header "Authorization: Bearer <key>"
To start without a key:
claude mcp add --transport http stophy https://api.stophy.dev/mcp
To use the key in your STOPHY_API_KEY environment variable:
codex mcp add stophy --url https://api.stophy.dev/mcp --bearer-token-env-var STOPHY_API_KEY
To sign in with your browser instead, add the sign-in URL, then log in:
codex mcp add stophy --url https://mcp.stophy.dev/mcp
codex mcp login stophy
Use the Add to Cursor button above to sign in with your browser, or add this to .cursor/mcp.json to use a key:
{
"mcpServers": { "stophy": { "url": "https://api.stophy.dev/mcp", "headers": { "Authorization": "Bearer " } } } }
To start without a key, leave out headers.
Some apps can only start a local MCP server. For those, use this package. It runs on your computer and passes every request to the hosted server, so it always has the same tools.
npx -y @stophy/mcp
With STOPHY_API_KEY set, your agent can use every endpoint. Without it, your agent can use the endpoints that need no key, within a free allowance.
Add this to claude_desktop_config.json, then restart Claude Desktop:
{
"mcpServers": { "stophy": { "command": "npx", "args": ["-y", "@stophy/mcp"], "env": { "STOPHY_API_KEY": " " } } } }
To start without a key, leave out env.
The package needs Node.js 18 or later.
| Variable | What it does |
|---|---|
STOPHY_API_KEY | Your Stophy API key. Optional. |
STOPHY_MCP_URL | The server to connect to. The default is https://api.stophy.dev/mcp. |
| Tool | What it does |
|---|---|
stophy_search_endpoints | Finds the endpoint for a task, with its cost |
stophy_describe_endpoint | Shows the input an endpoint takes and what it returns |
stophy_call | Runs an endpoint with id, input and optional fields, and returns JSON |
Your agent usually searches, then describes, then calls. Endpoint ids are camelCase, such as googleSearch or youtubeSearch. Lists come back as results, and fields keeps only the keys you name on each row. Each result says what it cost.
To point at one thing, send its link or its id, never both: videoUrl or videoId, placeUrl or placeId, userUrl or username. The endpoint description lists the pair.
One call returns one page from the site. Most calls cost $0.0015, long lists cost $0.0015 per 10 results, and a few cost more. See pricing. Some list endpoints take page and return page: ask for the next number, and stop when results comes back empty. Others return a cursor when there is more: pass it back unchanged as cursor to get the next page.
https://mcp.stophy.dev/mcp (sign in) and https://api.stophy.dev/mcp (no key or an API key). Your client sends requests only there.STOPHY_API_KEY that you set yourself. The local package also reads an optional STOPHY_MCP_URL..mcp.json, .grok-plugin/plugin.json, mcp.json, plugin.json) only point at the hosted server. They run no code on your machine.MIT