Revternal MCP server

@pipeworx/revternal

Revternal MCP — people and developer intelligence from Revternal (api.revternal.com): search a live index of ~12M developer profiles, behavioural intel per developer, and person-level search and enrichment across job titles, companies, and skills.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

• revternalsearchdevelopers(...) — search developers by role, primary language, location, recency.
• revternaldeveloperintel(github_username) — behavioural profile: work pattern, collaboration style, professionalism signals.
• revternalenrichdeveloper(github_url) — full developer profile from a GitHub URL.
• revternalpeoplesearch(...) — search any person by job title, seniority, location (ISO-3 countries + cities), current company domain, skills, or stealth-founder status; cursor pagination.
• revternalenrichperson(linkedinurl, fetchlive?) — full person profile from a LinkedIn /in/ URL: experience, education, skills, certifications, photo. fetchlive: false (default) reads Revternal's existing record (found: false if none); fetchlive: true requests a fresh fetch.
• revternalindexstats() — index size and processing status.

Auth

Platform-keyed — works out of the box through the gateway. You may also pass your own Revternal key as _apiKey (sent as x-api-key).

Data sources

• https://api.revternal.com (docs: https://revternal.com/docs)

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "revternal": {
      "url": "https://gateway.pipeworx.io/revternal/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/revternal/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1679+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/revternal_search_developers \
  -H 'Content-Type: application/json' \
  -d '{"primary_language":"Rust","active_within_days":30,"limit":20}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/revternalsearchdevelopers. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "revternal": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-revternal"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-revternal

Shortened. The full README is on GitHub.