GMPSignal Real-Time Intelligence MCP (59 Tools)

Official

Overview Schema Source Related Servers Discussions Admin

gmpsignal-mcp

README.md

# GMPSignal Real-Time Intelligence MCP Server (59 Tools)

An MCP (Model Context Protocol) server implementation exposing **59 real-time B2B lead, startup dealflow, ecommerce, crypto arbitrage, and cybersecurity intelligence tools** over both `stdio` JSON-RPC 2.0 (via `bin/cli.js` / Docker) and Streamable HTTP (`https://xpayr.com/gmpsignal/mcp`).

## Features

- **Full MCP `stdio` Server (`bin/cli.js`)**: Implements `initialize`, `tools/list`, and `tools/call` over standard input/output for Claude Desktop, Cursor, Windsurf, and Glama Docker inspection.
- **59 Live Intelligence Tools**: Crypto orderbook arbitrage, DEX security audits, YC/GitHub startup dealflow, tech-stack & B2B contact enrichment, Shodan/CVE perimeter scans, trademark & procurement monitors.
- **Zero-Commission Crypto Checkout & x402**: Obtain an instant `GMPSIGNAL_API_KEY` via XPayr at https://xpayr.com/gmpsignal/ or pay-per-call via `x402` Base USDC (`$0.005/call`).

## Installation & Usage

### Run as a Local `stdio` MCP Server

```json
{
  "mcpServers": {
    "gmpsignal": {
      "command": "npx",
      "args": ["-y", "gmpsignal-mcp"],
      "env": {
        "GMPSIGNAL_API_KEY": "YOUR_X_API_KEY"
      }
    }
  }
}
```

### Run via Docker

```bash
docker build -t gmpsignal-mcp .
docker run -i --rm -e GMPSIGNAL_API_KEY=YOUR_X_API_KEY gmpsignal-mcp
```

### Remote Streamable HTTP Transport

- Endpoint: `https://xpayr.com/gmpsignal/mcp`
- Discovery Manifest: `https://xpayr.com/gmpsignal/server.json`
- OpenAPI 3.1 Spec: `https://xpayr.com/gmpsignal/openapi.json`

## License

MIT — see [LICENSE](./LICENSE).

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.3/5.0

Scored 2026-11-15 08:55 across 59 tools

Disambiguation2/5

Several clusters of tools have nearly indistinguishable boundaries: three earthquake feeds (turkey_earthquakes_afad, europe_mediterranean_earthquakes_emsc, earthquake_monitor_usgs_emsc_afad), six Greenhouse hiring feeds split only by vertical (AI/ML, fintech, cybersecurity, e-commerce, B2B tech), and at least five IP/port/CVE scanners (cloud_perimeter, shodan_internetdb, vpn_gateway_firewall_cve, cyber_cve_kev_epss, ot_ics_scada, b2b_cyber_insurance). Identical boilerplate descriptions ('Real-time structured data extraction feed for X') give the agent no disambiguating signal beyond the long tool name itself.

Naming Consistency3/5

All names are snake_case and descriptive, which is superficially consistent, but the ordering convention is mixed: some lead with the source brand (eksi_sozluk_scraper, hepsiemlak_scraper, shodan_internetdb_...), others lead with the domain or region (turkey_fuel_prices, global_product_recalls, europe_mediterranean_earthquakes). No verb is used anywhere, so the name conveys the data source rather than the action, leaving agents to infer that everything is a read/extract.

Tool Count2/5

59 tools is far above the practical ceiling for a single agent-facing tool surface; selection becomes a scanning problem rather than a reasoning one. Each tool nominally maps to a distinct upstream data feed, so it is not pure duplication, but the count is well past the point where a well-scoped set would be separable into coherent sub-collections.

Completeness4/5

The domain is 'read-only real-time intelligence feeds', and for that domain the surface is broad and self-consistent: every feed is an extraction endpoint, so create/update/delete gaps are not meaningful. The one real gap is the absence of any discovery, aggregation, or cross-feed correlation tool to help an agent navigate 59 sibling endpoints.

Maintenance

ActivityMaintained

ResponsivenessNo recent community issues

TDQS

Maintenance

Resources