Signallabs Mcp

io.github.emresemerciogluPublished by GitHub account emresemerciogluv1.0.3Updated Oct 24, 2026

Competitive Intelligence MCP: generate AI battlecards, track competitors, monitor market signals.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Lets an assistant generate AI battlecards, track competitors, and monitor market signals through the Signal Labs competitive intelligence platform.

What you can do
This MCP server connects an assistant to Signal Labs, a competitive intelligence service. Based on the registry description, it supports generating AI battlecards, tracking competitors, and monitoring market signals. No tool list is published in the manifest, so the exact operations exposed are not documented here.
When to use it
Consider it when you want an assistant to help with competitive research: producing battlecards, keeping tabs on named competitors, or watching for market signals, and you already use or are willing to use the Signal Labs platform.
Requirements
Runs as a local process on the user's machine over stdio, installed from the npm package signallabs-mcp, so Node.js is required. It needs a Signal Labs API key supplied through the environment variable SIGNALLABS_API_KEY; the key is obtained from the Signal Labs account settings. Network access to the Signal Labs service is implied. Desktop only.
Before you install
The server requires a secret API key, SIGNALLABS_API_KEY, which grants access to your Signal Labs account; keep it out of logs and shared configuration. The manifest declares no authentication beyond that key. Because no tool list is published, what the tools can read or change in your Signal Labs workspace is not documented, so review behavior before relying on it. No payment, wallet, or private key handling is shown in the input.

Installation

In SourceWeft

  1. Open Signallabs Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.