mcpField
D
disruption-intelligence-mcp

disruption-intelligence-mcp

Local
github.com/forgemeshlabsBusiness & Marketing1Updated 3w ago

About disruption-intelligence-mcp

disruption-intelligence-mcp is an MCP server connecting clients to the hosted Forgemesh API for commercial disruption signals, including layoffs, company context, and territory data. It is a thin client with no local scoring or ingestion logic; paid calls return x402 payment challenge details without settling payments.

Key features

  1. 01Query WARN and layoff intelligence
  2. 02Search company context and risk summaries
  3. 03Analyze territory disruption and Ripple indexes
  4. 04Retrieve Ripple Signals, Paths, and reports
  5. 05Inspect x402 payment challenges

Use cases

  1. 01Track risk and events for a company
  2. 02Compare disruption around postal codes
  3. 03Review Ripple signals to choose follow-up research

MCP support

The MCP server exposes commercial disruption queries and x402 challenge inspection to MCP clients, forwarding requests to the hosted Forgemesh API. Paid calls default to returning payment instructions and challenge metadata rather than settling payment.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"forgemeshlabs-disruption-intelligence": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/disruption-intelligence-mcp"
]
}
}
}
Run commandnpx -y @forgemeshlabs/disruption-intelligence-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@forgemeshlabs/disruption-intelligence-mcp0.1.10

Tools

14

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project README

Disruption Intelligence MCP

M8ven Score mcpservers.org

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

ToolEndpointCost behavior
get_api_statusGET /healthFree
get_discovery_metadataGET /index.json, /llms.txt, /openapi.json, /.well-known/x402.jsonFree
inspect_x402_challengeUnpaid request to a paid endpointReturns x402 challenge metadata
analyze_territory_disruptionGET /territory/:zip/disruption?radius=Paid; challenge-first by default
search_company_contextGET /companies/search?q=Paid; challenge-first by default
get_company_risk_summaryGET /companies/:id/intelligencePaid; challenge-first by default
get_event_severityGET /events/:id/severityPaid; challenge-first by default; paid output includes confidence-rated industry_classification
get_event_company_intelGET /events/:id/company-intelPaid; challenge-first by default; paid output includes confidence-rated industry_classification
get_event_timelineGET /events/:id/timelinePaid; challenge-first by default
search_gold_inventoryGET /ripple/search?q=Compatibility tool name; free Ripple inventory counts and unlock pricing only
get_ripple_indexGET /ripple/index?q=&scope=&limit=Paid at $0.01; challenge-first by default; returns location-only Ripple index cards
get_gold_signalsGET /ripple/signals?q=&limit=&state=Compatibility tool name; paid at $0.10; challenge-first by default; returns Ripple Signals after settlement
get_gold_briefGET /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_impactsGET /ripple/signals/:id/sector-impactsCompatibility tool name; paid at $0.15; challenge-first by default; returns Ripple Paths after settlement

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.