Company Hiring Signals

io.github.fxjimaPublished by GitHub account fxjimav0.1.3Updated Nov 20, 2026

Hiring signals by company domain: open and new roles, functions and remote share across 6 ATSs.

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Apify-hosted remote MCP server that gives an assistant hiring signals by company domain: open and new roles, functions and remote share across six ATSs.

What you can do
  • Retrieve hiring signals for a company identified by its domain
  • See open roles and newly posted roles
  • Break roles down by function and by remote share
  • Aggregate results across six applicant tracking systems
  • No tool list is published, so exact operations are not documented.
When to use it
Useful when you want an assistant to gauge a company's hiring activity, growth or remote-friendliness from job postings, for example in sales, recruiting or market research.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. An Apify account is needed: either OAuth sign-in from the MCP client or an Apify API token sent in the Authorization header as a Bearer token.
Before you install
The Authorization header carries an Apify API token, which is a billable account credential; keep it secret and prefer OAuth sign-in. Apify usage may consume paid plan credits. Queries about company domains are sent to Apify's hosted service.

Installation

In SourceWeft

  1. Open Company Hiring Signals in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.fxjima%2Fcompany-hiring-signals/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "company-hiring-signals": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=fxjima/company-hiring-signals"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.3LatestNov 20, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Signals integrations