PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon)

● Active

io.github.3dComm/pipeforge-b2b-signals

Live US B2B intent signals: FMCSA, Permits, DNS/SSL, SEC Form D, NPI-2, ATS Hiring & USAspending.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "pipeforge-b2b-signals": {
      "url": "https://mcp.apify.com/?tools=pipeforge/us-socrata-b2b-signal-crossjoin-engine,pipeforge/b2b-domain-tech-stack-dns-ssl-sales-trigger,pipeforge/us-sec-form-d-startup-funding-leads,pipeforge/us-cms-npi2-clinic-owner-phone-leads,pipeforge/us-ats-hiring-intent-sales-triggers,pipeforge/us-federal-contract-awards-expiring-incumbents"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http pipeforge-b2b-signals https://mcp.apify.com/?tools=pipeforge/us-socrata-b2b-signal-crossjoin-engine,pipeforge/b2b-domain-tech-stack-dns-ssl-sales-trigger,pipeforge/us-sec-form-d-startup-funding-leads,pipeforge/us-cms-npi2-clinic-owner-phone-leads,pipeforge/us-ats-hiring-intent-sales-triggers,pipeforge/us-federal-contract-awards-expiring-incumbents
VS Code
code --add-mcp '{"name":"pipeforge-b2b-signals","type":"http","url":"https://mcp.apify.com/?tools=pipeforge/us-socrata-b2b-signal-crossjoin-engine,pipeforge/b2b-domain-tech-stack-dns-ssl-sales-trigger,pipeforge/us-sec-form-d-startup-funding-leads,pipeforge/us-cms-npi2-clinic-owner-phone-leads,pipeforge/us-ats-hiring-intent-sales-triggers,pipeforge/us-federal-contract-awards-expiring-incumbents"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Business & CRM
Version
1.1.0
Registry
active
Published
11/20/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) is maintained, hosted endpoint behind a sign-in.

Maintained
Active
Last commit today (Nov 20, 2026), 0 open issues.
Official registry
Active
Published as io.github.3dComm/pipeforge-b2b-signals in the official MCP registry, version 1.1.0.
Source
No licence found
Public repository, but GitHub reports no recognised licence (0 stars). Check the README before shipping it in a product.
Runs
Hosted by the publisher
Your client talks to mcp.apify.com: prompts and tool arguments leave your machine for that host.
Credentials
Sign-in required
The hosted endpoint answered 401/403 to a credential-free call (checked Nov 22, 2026): it wants an API key or an OAuth login first.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 07:08 UTCStatus history & uptime →
● Needs sign-in

The endpoint is up but wants a key or an OAuth sign-in before the handshake, so its tools can only be read with an account.

Checked by Serverdex with a plain initialize + tools/list call to mcp.apify.com, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 21, 2026
Stars
0
Forks
0
Last push
Nov 20, 2026
License
—

ai-agentsapifyb2b-leadsclaylead-generationmcpmcp-servermodel-context-protocoln8nn8n-workflowsremote-mcpsec-edgar

From the README

PipeForge — Zero-Proxy US B2B Outbound & Federal Signal MCP Pack (6 Live Tools, 1 Endpoint) Connect Claude Desktop, Cursor, Windsurf, or n8n AI Agents to 6 live US federal public-record, ATS hiring-intent & B2B domain intelligence engines in 15 seconds — with $0 proxy costs, 256 MB RAM footprint, and transparent Pay-Per-Event pricing ($3.50–$4.50 / 1,000 verified records). -00C853?style=for-the-badge) Why PipeForge? Most B2B scrapers burn residential proxies, break when DOM selectors change, or scrape stale directories with receptionist phone numbers. PipeForge queries official federal registries, live XML filings, US Treasury award APIs, and direct DNS/TLS sockets: Quick-Start Tip (Actor #1): For a single clean 100%-filled table without mixing feeds, launch the pre-configured FMCSA $0 BIPD Task or Austin/NYC $75K+ Commercial Permits Task directly instead of mode="all". 1-Click MCP Server Setup All 6 live engines are exposed through a single hosted Apify MCP endpoint (published on the Official MCP Registry as io.github.3dComm/pipeforge-b2b-signals): Claude Code CLI (1-Line Install) Claude Desktop (claudedesktopconfig.json) Copy configs/claudedesktopconfig.json and insert your free Apify API token: Cursor (~/.cursor/mcp.json) See configs/cursor_mcp.json for native streamable HTTP MCP config. Example AI Agent Prompts (Copy & Run)…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://mcp.apify.com/?tools=pipeforge/us-socrata-b2b-signal-crossjoin-engine,pipeforge/b2b-domain-tech-stack-dns-ssl-sales-trigger,pipeforge/us-sec-form-d-startup-funding-leads,pipeforge/us-cms-npi2-clinic-owner-phone-leads,pipeforge/us-ats-hiring-intent-sales-triggers,pipeforge/us-federal-contract-awards-expiring-incumbents

Alternatives to PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon)

All PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) alternatives →Best Business & CRM servers →

The most-starred Business & CRM servers in the index, with their live-check result.

ServerStarsLast pushLive check
Contact Affordance7,477Nov 2026Working
Business Contact Finder7,470Nov 2026Working
JobSpy4,739Nov 2026Local / not checked
Relaticle1,915Nov 2026Needs sign-in
ChatbotX1,142Nov 2026Needs sign-in

PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon): questions people ask

Is PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) a remote or a local MCP server?
According to its entry in the official MCP registry, PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) need an API key or a sign-in?
Yes. Its hosted endpoint answered the credential-free Serverdex live check with HTTP 401/403 on Nov 22, 2026: it expects an API key in a header or an OAuth login before it lists its tools.
Is PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) safe to use?
Mostly fine: PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) is maintained, hosted endpoint behind a sign-in. In detail — maintained: Active; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: Sign-in required. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) still maintained?
Active: the repository's last commit today. Last push Nov 20, 2026, 0 GitHub stars. Read from GitHub on Nov 21, 2026.
How do I add PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Business & CRM →

Add the badge to your site

Show visitors that PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) is listed here — it’s also the link we check for a free listing.

PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-3dcomm-pipeforge-b2b-signals?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![PipeForge US B2B Signals (FMCSA, Permits, SEC, NPI-2, ATS, GovCon) — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-3dcomm-pipeforge-b2b-signals?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-3dcomm-pipeforge-b2b-signals) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-3dcomm-pipeforge-b2b-signals) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-3dcomm-pipeforge-b2b-signals)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-3dcomm-pipeforge-b2b-signals"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-3dcomm-pipeforge-b2b-signals"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-3dcomm-pipeforge-b2b-signals"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).