Disruption Intelligence MCP

Disruption Intelligence MCP

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.

Install

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

Claude Desktop

Example config:

{

"mcpServers": { "disruption-intelligence": { "command": "npx", "args": ["@forgemeshlabs/disruption-intelligence-mcp"] } } }

See examples/claude-desktop-config.json.

Tools

Ripple Output

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.

Industry Classification Output

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.

Free vs Paid Behavior

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.

Configuration

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

API docs and product context:

https://github.com/forgemeshlabs/disruption-intelligence

Hosted API:

https://disruption.forgemesh.io

Security Boundary

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.