Disruption Intelligence MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X402_NETWORK | No | Optional network identifier for future paid execution. | |
| X402_PRIVATE_KEY | No | Optional private key for future paid execution. | |
| DISRUPTION_API_BASE | No | Base URL for the Disruption Intelligence API. | https://disruption.forgemesh.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_api_statusA | Check the hosted Disruption Intelligence API health endpoint. Free. |
| get_discovery_metadataB | Fetch free discovery metadata from index.json, llms.txt, openapi.json, and x402 well-known metadata. Free. |
| inspect_x402_challengeA | Make an unpaid request to a paid endpoint and return the structured x402 payment challenge. Does not settle payment. |
| analyze_territory_disruptionA | Thin wrapper for GET /territory/:zip/disruption?radius=. Paid endpoint; returns x402 challenge in default non-settling mode. |
| search_company_contextA | Thin wrapper for GET /companies/search?q=. Paid endpoint; returns x402 challenge in default non-settling mode. |
| get_company_risk_summaryB | Thin wrapper for GET /companies/:id/intelligence. Paid endpoint; returns x402 challenge in default non-settling mode. |
| get_event_severityB | Thin wrapper for GET /events/:id/severity. Paid endpoint; enriched paid responses include industry_classification with method, confidence, and coverage_note. Returns x402 challenge in default non-settling mode. |
| get_event_company_intelA | Thin wrapper for GET /events/:id/company-intel. Paid endpoint; enriched paid responses include event industry_classification with method, confidence, and coverage_note. Returns x402 challenge in default non-settling mode. |
| get_event_timelineA | Thin wrapper for GET /events/:id/timeline. Paid endpoint; returns x402 challenge in default non-settling mode. |
| search_gold_inventoryB | Compatibility tool for free inventory-only Ripple Signal search. Returns counts and unlock pricing without revealing signal details. |
| get_ripple_indexA | Thin wrapper for GET /ripple/index. Paid endpoint currently priced at $0.01; returns location-only Ripple index cards with signal IDs, bands, and unlock URLs while withholding companies, employee counts, commercial angles, and impact paths. |
| get_gold_signalsA | Compatibility tool for GET /ripple/signals. Paid endpoint currently priced at $0.10; returns Ripple Signals and Ripple Path inventory, challenge-first by default. |
| get_gold_briefC | Compatibility tool for GET /ripple/brief. Paid endpoint currently priced at $0.25; returns a Disruption Intelligence Ripple Report, challenge-first by default. |
| get_gold_sector_impactsA | Compatibility tool for GET /ripple/signals/:id/sector-impacts. Paid endpoint currently priced at $0.15; returns Ripple Paths with deep operational spend and downstream sector impacts for one signal, challenge-first by default. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools target distinct resources, but the 'gold' family (get_gold_signals, search_gold_inventory, get_gold_brief, get_gold_sector_impacts) and the ripple index overlap conceptually, making selection less obvious. Event tools and company tools are clearer, though get_company_risk_summary and get_event_company_intel could still be confused.
Tool names consistently use a verb_noun pattern, mostly get_*, with search_, analyze_, and inspect_ as readable variations. The main inconsistency is mixing 'gold' and 'ripple' branding across related tools.
14 tools is slightly on the high side but still reasonable for a multi-faceted intelligence API covering company, event, territory, ripple signals, metadata, and API status. The count is manageable, though several thin paid-endpoint wrappers add breadth without much conceptual variety.
The server covers discovery, API health, company intelligence, event intelligence, territory analysis, and ripple/gold signal products. Minor gaps exist, such as no explicit event search or signal detail unlock flow beyond the generic x402 challenge mechanism, but agents can work around these.