npm:signallabs-mcp

Item: npm:signallabs-mcp
Rating: 74
Author: wmcp.sh

https://www.npmjs.com/package/signallabs-mcp

74/100 · MCP Trust Grade · checked 4h ago · MCP 1.0.3

What it offers — 15 tools · AI & ML

list_companies

List all tracked companies in your organization

create_company

Track a new company by name or domain

list_products

List products/service verticals for a company

create_product

Add a product/service vertical to a company

list_competitors

List competitors for a company (optionally filtered by product)

add_competitor

Add a competitor to a company

discover_competitors

Use AI to automatically discover competitors for a company

get_battlecards

Get battlecards for a company

generate_battlecard

Generate a new AI-powered battlecard (costs 1 credit)

generate_landscape_battlecard

Generate a landscape analysis battlecard comparing multiple competitors at once (costs 1 credit, requires 2+ competitors)

get_signals

Get recent competitive intelligence signals

get_signal_summary

Get an AI-generated executive digest of recent competitive signals

list_documents

List uploaded documents in the data library for a company

get_document

Get details of a specific document including extracted text

ask_competitive_intel

Ask AI questions about your competitive landscape (RAG-powered, uses your battlecards, signals, and documents)

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 15 tool(s) detected in source

Security (OWASP MCP)30%25

⚠ references sensitive file paths / env secrets
scanned 2 source files

Maintenance / popularity20%92

published within 90 days
4 published versions

Tool hygiene15%95

✓ ships TypeScript types
2 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
13 weekly downloads

Findings

WARNMCP08 References sensitive file paths / environment secrets.

INFO Static analysis of npm package signallabs-mcp@1.0.3 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:signallabs-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:signallabs-mcp grade C

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Asignallabs-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade C](https://wmcp.sh/mcp/grade/npm%3Asignallabs-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Asignallabs-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Asignallabs-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3Asignallabs-mcp/badge.svg" alt="MCP Trust Grade C · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.