Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
AI-native commercial disruption intelligence for MCP clients and x402-powered agents.
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 …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"disruption-intelligence": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/disruption-intelligence-mcp"
]
}
}
}Run this in your terminal
claude mcp add disruption-intelligence -- npx -y @forgemeshlabs/disruption-intelligence-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"disruption-intelligence": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/disruption-intelligence-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": {
"disruption-intelligence": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/disruption-intelligence-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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 7, 2026
The registry name was verified with the GitHub account forgemeshlabs, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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 on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.11) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
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.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
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.
AI-native commercial disruption intelligence for MCP clients and x402-powered agents.
Disruption Intelligence MCP gives AI agents access to commercial disruption signals through an MCP server backed by the hosted Forgemesh API. It supports WARN/layoff intelligence, company context, geospatial territory disruption, location-only Ripple Index cards, Ripple Signals, Ripple Paths, Disruption Intelligence Ripple Reports, x402 payment challenge inspection, and economic signal workflows without exposing private scoring logic, ingestion systems, schemas, or infrastructure.
This package is a thin client around the hosted API:
https://disruption.forgemesh.io
Architecture:
Agent/MCP client -> this MCP server -> hosted Disruption Intelligence API
The MCP package does not contain engine internals, scoring logic, ingestion architecture, database schema, private topology, wallet addresses, or secrets.
npm install -g @forgemeshlabs/disruption-intelligence-mcp
Published package:
https://www.npmjs.com/package/@forgemeshlabs/disruption-intelligence-mcp
Source repo:
https://github.com/forgemeshlabs/disruption-intelligence-mcp
Local development:
npm install
npm run build node dist/index.js
Example config:
{
"mcpServers": { "disruption-intelligence": { "command": "npx", "args": ["@forgemeshlabs/disruption-intelligence-mcp"] } } }
See examples/claude-desktop-config.json.
| Tool | Endpoint | Cost behavior |
|---|---|---|
get_api_status | GET /health | Free |
get_discovery_metadata | GET /index.json, /llms.txt, /openapi.json, /.well-known/x402.json | Free |
inspect_x402_challenge | Unpaid request to a paid endpoint | Returns x402 challenge metadata |
analyze_territory_disruption | GET /territory/:zip/disruption?radius= | Paid; challenge-first by default |
search_company_context | GET /companies/search?q= | Paid; challenge-first by default |
get_company_risk_summary | GET /companies/:id/intelligence | Paid; challenge-first by default |
get_event_severity | GET /events/:id/severity | Paid; challenge-first by default; paid output includes confidence-rated industry_classification |
get_event_company_intel | GET /events/:id/company-intel | Paid; challenge-first by default; paid output includes confidence-rated industry_classification |
get_event_timeline | GET /events/:id/timeline | Paid; challenge-first by default |
search_gold_inventory | GET /ripple/search?q= | Compatibility tool name; free Ripple inventory counts and unlock pricing only |
get_ripple_index | GET /ripple/index?q=&scope=&limit= | Paid at $0.01; challenge-first by default; returns location-only Ripple index cards |
get_gold_signals | GET /ripple/signals?q=&limit=&state= | Compatibility tool name; paid at $0.10; challenge-first by default; returns Ripple Signals after settlement |
get_gold_brief | GET /ripple/brief?q=&scope=&limit= | Compatibility tool name; paid at $0.25; challenge-first by default; returns a Disruption Intelligence Ripple Report after settlement |
get_gold_sector_impacts | GET /ripple/signals/:id/sector-impacts | Compatibility tool name; paid at $0.15; challenge-first by default; returns Ripple Paths after settlement |
Free Ripple search is intentionally inventory-only. It returns counts, freshness, and unlock pricing without exposing commercial angles, evidence categories, source mix, signal IDs, company names, or raw source records.
get_ripple_index unlocks a low-cost location-only index for choosing where to dig next. It can return signal IDs, event IDs, regions, states, signal types, freshness/depth/confidence/score bands, and unlock URLs, while withholding company names, employee counts, commercial angles, sector names, spend areas, source records, and impact paths.
Paid Ripple endpoints expose distilled commercial intelligence. get_gold_signals returns Ripple Signal summaries, confidence bands, compact evidence labels, and Ripple Path inventory with an unlock endpoint. get_gold_sector_impacts unlocks the deeper operational map for one signal, including downstream spend categories such as fuel, food service, uniforms, maintenance, IT, logistics, office supplies, telecom, insurance, legal, cleaning, travel, and related vendor categories.
Paid event-level API responses now include industry_classification when event context is available. The hosted API returns the industry label, NAICS fields when present, derivation method, confidence level, source text when relevant, and a coverage note. The MCP remains a thin client: it does not infer industries locally and does not rewrite hosted WARN data.
Default mode is safe and non-settling. Free endpoints return API data directly. Paid endpoints are requested without payment credentials, so the hosted API can return an x402 402 Payment Required challenge.
When payment is required, this MCP returns structured payment instructions and challenge metadata instead of dumping an upstream error. It does not require a private key and does not settle payments.
Future paid execution should be opt-in and delegated to a trusted wallet or payment client.
No environment variables are read. The API base URL is fixed to https://disruption.forgemesh.io; every request is bounded (60 s timeout, 2 MB response cap, no redirects) and inspect_x402_challenge only accepts a plain path on that host.
No wallet private key is required or accepted by this package. Paid endpoint calls return x402 challenge metadata for an external wallet or payment client to settle.
API docs and product context:
https://github.com/forgemeshlabs/disruption-intelligence
Hosted API:
https://disruption.forgemesh.io
This repository is an agent-facing thin client wrapper around the hosted API. It intentionally excludes engine code, scoring formulas, ingestion internals, database details, operational topology, wallet addresses, private keys, and secrets.