# agent-signals-mcp [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/hassanahashish-design/agent-signals-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/agent-signals-mcp

## Description
Hiring, SEC, research papers, GitHub & Hacker News as JSON for AI agents. Pay-per-result on Apify.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "agent-signals-mcp": {
    "url": "https://mcp.apify.com/?actors=oblanceolate_mandola%2Fcompany-hiring-signals%2Coblanceolate_mandola%2Fsec-edgar-filings%2Coblanceolate_mandola%2Fresearch-paper-search%2Coblanceolate_mandola%2Fgithub-repo-search%2Coblanceolate_mandola%2Fhacker-news-monitor%2Coblanceolate_mandola%2Ffederal-register-monitor%2Coblanceolate_mandola%2Fclinical-trials-search%2Coblanceolate_mandola%2Fstackoverflow-search%2Coblanceolate_mandola%2Fgdelt-news-monitor%2Coblanceolate_mandola%2Fcourt-opinions-search"
  }
}
```

## Documentation

## What agent-signals-mcp does

agent-signals-mcp MCP server groups search and monitoring tools for public information sources behind one Apify-hosted MCP endpoint. The available sources cover company hiring pages from Greenhouse, Lever, and Ashby; SEC EDGAR filings; academic papers indexed by OpenAlex; GitHub repositories; Hacker News; Stack Overflow; ClinicalTrials.gov; the US Federal Register; GDELT global news; and US court opinions.

The tools return flat JSON intended for agent workflows. Results include a `sourceUrl` and `scrapedAt` value, allowing downstream applications to link back to the source and record when the data was collected. The collection can support research grounding, hiring-signal analysis, due diligence, brand monitoring, and other workflows that need current public-web or public-record data.

## How it works

The agent-signals-mcp MCP server is configured as a remote, streamable HTTP server hosted through Apify. The connection URL contains an `actors` parameter that selects the Apify Actors exposed through the MCP connection. A client sends tool requests through MCP, and the selected Actor performs the corresponding search or collection task.

Usage is charged to the user's Apify account according to each Actor's pay-per-result pricing. Batched queries are deduplicated, and `maxResults` can cap spending for an individual call. Each Actor also provides an OpenAPI description on its Apify API tab.

## Setup and configuration

No local installation or hosting is required. Add the remote MCP URL to a compatible client and provide an Apify token in the request's `Authorization` header. The documented configuration uses a bearer token and includes the Actors for hiring, SEC filings, research papers, GitHub, Hacker News, Federal Register, clinical trials, Stack Overflow, GDELT news, and court opinions.

You can reduce the exposed tool set by editing the URL's `actors` list and retaining only the Actor identifiers required by the client. An Apify account token is required for authenticated access; the README links to Apify's account integrations page for obtaining one.

## Tools and capabilities

The available tools support these operations:

- Search hiring postings across Greenhouse, Lever, and Ashby using one normalized result structure.
- Search SEC EDGAR filings by full text, filer, CIK, and date.
- Find research papers through OpenAlex, including citation, venue, year, and DOI-related information.
- Search GitHub repositories and inspect stars, forks, issues, and last-push details.
- Monitor Hacker News mentions with points, comments, and dates.
- Search US Federal Register documents by keyword.
- Search ClinicalTrials.gov records by condition, drug, or sponsor.
- Search Stack Overflow questions by keyword.
- Find worldwide news mentions through GDELT.
- Search US court opinions for case names, courts, dates, and citation counts.

## Limitations and notes

agent-signals-mcp MCP server depends on Apify and the configured Actors, so it is not a locally self-contained data service. Billing is handled through the user's Apify account rather than through a separate subscription described in the README. Costs vary by Actor and are listed on the corresponding Apify page.

The server provides access to the sources and result fields described above; it does not establish that a result is complete, authoritative beyond its source, or suitable for a legal, financial, medical, or hiring decision. Clients should use the supplied source URL to verify important findings. Empty and failed requests are stated to be free, but successful results remain subject to per-result pricing and any selected result limit.

_Full upstream README: https://allmcps.com/mcp/agent-signals-mcp/readme_