Job Posting Liveness Checker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. Required to run the actor; the server lists its tool without a token, but a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_job_posting_livenessA | Give job posting URLs from Greenhouse, Lever, Ashby, Workday, or SmartRecruiters. Returns one row per URL: live or closed, job title, company, location, posted date, age in days, and when a run on your account last saw it live. Reads each ATS's own public job API. Pay per event on Apify: 0.003 USD per posting checked; unsupported URLs are free. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlapping purpose. The tool's scope (batch URL liveness check across five named ATS platforms) is clearly stated and self-contained.
A single descriptive snake_case verb_noun name (check_job_posting_liveness) is used, which is fully consistent and immediately readable. There is no competing convention to conflict with.
One tool for a narrowly scoped batch-checking service is defensible, but it feels thin—batch input of URLs is folded into a single call with no way to list supported ATSs, validate URLs, or retrieve history separately. The surface is minimal even for this focused purpose.
The tool covers the core lifecycle (live/closed status plus metadata like title, company, location, posted date, age, and last-seen-live) across five major ATS platforms in one call. Minor gaps exist—no discovery of supported platforms, no per-URL validation endpoint, and unclear handling of mixed supported/unsupported batches beyond the free-unsupported note.