# SigParser
ID: 01-sigparser
Page: https://gtmmcps.com/tools/01-sigparser
JSON: https://gtmmcps.com/data/tools/01-sigparser.json
Documentation references: https://gtmmcps.com/docs/01-sigparser/
Category: Data & Enrichment
MCP support: official
Testing: RESEARCHED
API access: enterprise-leaning
Last checked: 2026-09-07
Endpoint check: not-probed; date: Not recorded

A relationship-intelligence and contact-capture product that scans connected mailboxes, calendars and address books, parses email signatures, and turns the result into contact and company records with who-knows-who relationship scores, exportable to a CRM, a spreadsheet or a data warehouse.

## MCP links
- https://ipaas.sigparser.com/api/mcp

## Sources
- https://www.sigparser.com/pricing
- https://www.sigparser.com/developers
- https://www.sigparser.com/how-to-category/ai-and-mcp
- https://ipaas.sigparser.com/api/mcp

## Research notes
READ THE mcp_status QUALIFIER BEFORE CITING THIS ENTRY. Verified 2026-09-07: POST of an MCP initialize to https://ipaas.sigparser.com/api/mcp returned HTTP 401 and a GET returned HTTP 405, exactly how a live auth-gated MCP endpoint behaves, and that host is first-party (SigParser's own API documentation prints pagination URLs on ipaas.sigparser.com). What is missing is any vendor page describing the server: sigparser.com/mcp and sigparser.com/developers/mcp both return 404, sigparser.com/llms.txt returns 404, the developers page never mentions MCP, and the site's own sitemap declares a content category at /how-to-category/ai-and-mcp which renders "No items found". The official call here therefore rests entirely on a first-party endpoint that answers as an MCP server, with zero first-party prose about it. That is weaker evidence than every other official entry in this file and is flagged rather than smoothed over; re-check for a published docs page before this is used on camera. Note also the mismatch between the gate and the product: the API tier is $499/month and sales-routed, while the underlying value (contacts mined from mailboxes the buyer already owns) is exactly what a solo operator would most want to automate. 2026-09-07: Official MCP registry carries com.sigparser/sigparser (DNS-verified sigparser.com namespace) with remote https://ipaas.sigparser.com/api/mcp; that URL returned 401 to an MCP initialize (https://ipaas.sigparser.com/api/mcp).

## Named capabilities
Tool names below are reported by sources. Their presence is not a successful call.

## CLI evidence
Status: none-found

Read current vendor documentation before configuring or running commands.