Mcp Server Research Signals

io.github.joepangalloPublished by GitHub account joepangallov1.2.0Updated Oct 24, 2026

Scored trend intelligence from HN, Reddit, ArXiv, and GitHub.

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Gives an assistant scored trend signals gathered from Hacker News, Reddit, ArXiv, and GitHub.

What you can do
This local MCP server supplies scored trend intelligence drawn from four public sources: Hacker News, Reddit, ArXiv, and GitHub. The registry description indicates it returns ranked or scored signals rather than raw feeds, so an assistant can surface what is currently rising across those communities. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when you want an assistant to track emerging topics, papers, repositories, or discussions across developer and research communities without visiting each site yourself. Less useful if you need only one source or already have dedicated integrations for it.
Requirements
Runs as a local process over stdio, installed from the npm package mcp-server-research-signals, so Node.js and npm are needed on the machine. It is desktop only and not web executable. No authentication, environment variables, or headers are declared, but network access to the four source sites is implied.
Before you install
The server is declared with no authentication and no credentials, so nothing secret is requested. It reads from third-party public sites, meaning queries and usage may be visible to those services and results depend on their availability and rate limits. No tools are listed, so review what it actually calls before relying on it.

Installation

In SourceWeft

  1. Open Mcp Server Research Signals 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.2.0LatestSep 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.

Other Signals integrations