Agent Signals MCP logo

Agent Signals MCP

Queries hiring, filings, research, code, news, legal and public-record sources through Apify-hosted MCP tools.

Install Agent Signals MCP

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server 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

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

agent-signals-mcp MCP server connects AI agents to Apify-hosted Actors that search hiring data, SEC filings, academic papers, GitHub, forums, trials, regulations, news, and court opinions. It returns flat JSON with source URLs and collection timestamps, and supports result limits and deduplication for batched queries. Use it when an agent needs citation-ready signals from several public data sources without deploying its own scrapers. Access is provided through a streamable HTTP MCP URL and billed through the user's Apify account.

Use cases

  • Monitor company hiring signals
  • Search SEC filings for disclosures
  • Ground research with academic papers
  • Track brand mentions across news and forums
  • Find trials, regulations, or court opinions

Key features

  • Remote streamable HTTP MCP endpoint
  • Ten public-data search and monitoring sources
  • Flat JSON with source URLs and timestamps
  • Apify pay-per-result billing
  • Actor selection through the URL
  • Per-call result limits and query deduplication

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 37d

How Agent Signals MCP works

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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Agent Signals MCP

agent-signals-mcp is an MCP server that connects AI agents to Apify-hosted Actors for hiring signals, SEC filings, research papers, GitHub repositories, Hacker News, public records, news, Stack Overflow, clinical trials, and court opinions. Its tools return flat JSON with source URLs and collection timestamps for citation and verification.

You do not install or host it locally; add its remote streamable HTTP URL to an MCP client and supply an Apify bearer token. The README provides a Claude Desktop and Claude Code configuration, and the same endpoint can be used from Cursor or another compatible client.

Usage is billed through your own Apify account on a per-result basis for the selected Actors. Set `maxResults` to cap results for a call.

Yes, edit the `actors` list in the MCP URL to include only the Apify Actors you need. This lets you expose a smaller set of sources instead of the full configured collection.

Configure Cursor with the remote MCP URL and an `Authorization` header containing your Apify bearer token.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAgent Signals MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/agent-signals-mcp?style=directory)](https://allmcps.com/mcp/agent-signals-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/agent-signals-mcp"><img src="https://allmcps.com/api/badge/agent-signals-mcp?style=directory" alt="Agent Signals MCP on AllMCPs" /></a>