pipeworx-io Business Data Suite - MCP Servers¶

What It Is¶

pipeworx-io shipped 18+ MCP servers on July 2, 2026 - the single largest one-day batch in MCP ecosystem history. Their business data suite wraps major APIs for finance, business intelligence, security, marketing, real estate, and logistics.

Pattern: Every business API gets a clean MCP wrapper. Single dependency (TypeScript), consistent tool naming, shared configuration pattern.

Business Data Servers¶

Finance¶

Server	API	Use Case
mcp-tradier	Tradier Brokerage API	Real-time stock & options market data, quotes, chains
mcp-eodhd	EOD Historical Data	Global equities historical data, fundamentals, dividends

Business Intelligence¶

Server	API	Use Case
mcp-diffbot	Diffbot Knowledge Graph	Company enrichment, web content extraction, KG queries
mcp-coresignal	Coresignal API	LinkedIn-adjacent company profiles, employee insights
mcp-peopledatalabs	People Data Labs	Person/company enrichment, professional data

Security¶

Server	API	Use Case
mcp-shodan	Shodan REST API	Internet scanning, exposed services, IoT discovery
mcp-pulsedive	Pulsedive API	Threat intelligence IOC enrichment, malware analysis

Marketing¶

Server	API	Use Case
mcp-seo-backlinks	DataForSEO Backlinks	Backlink intelligence, domain authority, link profiling
mcp-emailable	Emailable API	Email verification, deliverability scoring

Maps & Location¶

Server	API	Use Case
mcp-here	HERE Maps API	Geocoding, reverse geocoding, routing, POI search, map tiles

Quick Start (Any Server)¶

# Clone
git clone https://github.com/pipeworx-io/mcp-tradier.git
cd mcp-tradier
npm install
npm run build

# Add to Hermes
hermes mcp add tradier --command "node" --args "dist/index.js" --workdir "$(pwd)" \
  --env TRADIER_API_KEY="your-key"

Manual Configuration (Example: Tradier)¶

{
  "mcpServers": {
    "tradier": {
      "command": "node",
      "args": ["dist/index.js"],
      "workdir": "/path/to/mcp-tradier",
      "env": {
        "TRADIER_API_KEY": "your-tradier-api-key"
      }
    }
  }
}

All pipeworx MCPs follow this pattern - replace tradier with the server name and set the appropriate API key.

Recommended Stack for Business Operators¶

For a complete business intelligence workflow, combine:

Market Intelligence:
├── SentiSense (market sentiment, analyst ratings)
├── mcp-tradier (real-time stock/options data)
├── mcp-eodhd (historical financial data)
└── HPSILab Quant (options analytics, Monte Carlo)

Company Intelligence:
├── mcp-diffbot (web-scale company enrichment)
├── mcp-coresignal (LinkedIn-adjacent professional data)
└── mcp-peopledatalabs (person/company enrichment)

Security/Infra:
└── mcp-shodan (internet asset discovery)

API Key Requirements¶

Server	API Key Source	Free Tier?
mcp-tradier	tradier.com	30-day trial
mcp-eodhd	eodhd.com	Yes (20 calls/day)
mcp-diffbot	diffbot.com	Yes (1,000 calls/month)
mcp-coresignal	coresignal.com	No
mcp-peopledatalabs	peopledatalabs.com	Yes (1,000 records/month)
mcp-shodan	shodan.io	Yes (limited)
mcp-seo-backlinks	dataforseo.com	No ($0.003/call)
mcp-emailable	emailable.com	Yes (250 verifications/month)

Why pipeworx-io Matters¶

The "every API gets an MCP wrapper" industrialization signals that MCP server creation is shifting from artisanal (one-off, hand-crafted) to industrial (systematic, templated). This is the same pattern that made npm/pip successful - a low-friction packaging format enables an explosion of integrations.

Integration with CorpusIQ¶

CorpusIQ is the connector layer that lets AI assistants read the systems a business already runs on - accounting, payments, CRM, email, files and analytics - and answer with the source named. It is read-only by design: it retrieves data and never writes to, or acts in, a connected system, which is what makes it safe to point at live accounts.

This page is part of the CorpusIQ directory, the reference we maintain for the MCP server and agent-skill ecosystem. Run alongside CorpusIQ, a third-party server like this one can be combined with a company's own business data in a single answer.

See what CorpusIQ connects

Limitations¶

All pipeworx MCPs are single-API wrappers - no cross-source intelligence
Require individual API keys (no unified auth)
New servers - limited battle-testing, expect bugs
No TypeScript SDK abstractions - each MCP is standalone