SigParser

com.sigparserPublished by sigparser.comOfficial publisherv1.0.0Updated Oct 24, 2026

Query contacts, companies, relationships, and communication metrics from SigParser.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

SigParser is a remote MCP server that lets an assistant query contacts, companies, relationships and communication metrics from SigParser.

What you can do
Query contacts and companies stored in SigParser, including their details and relationships to one another. Retrieve communication metrics associated with those contacts and companies. Look up relationship data to understand how people and organizations connect. No individual tools are listed, so exact operations depend on the server.
When to use it
Useful when an assistant needs to look up SigParser contact and company records, or answer questions about relationships and communication activity across a contact network.
Requirements
A remote MCP endpoint at ipaas.sigparser.com reached over streamable HTTP. OAuth authentication is required, so a SigParser account with OAuth access is needed. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to SigParser contact and communication data, which may include personal and business information about contacts. Review what the OAuth grant exposes before connecting, and be mindful that queries send requests to a third-party service.

Installation

In SourceWeft

  1. Open SigParser in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.sigparser%2Fsigparser/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sigparser": {
      "type": "http",
      "url": "https://ipaas.sigparser.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.