Company Jobs & Hiring Signals
Server Details
Open jobs and hiring signals for any company, from its public careers page or job board.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- Plainfold/plainfold-mcp
- GitHub Stars
- 0
- Server Listing
- Plainfold MCP tools
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
The four platform tools (abort run, get run, get dataset items, get KV record) are clearly distinct from one another, but the domain tool plainfold--company-hiring-signals 'calls the Actor and retrieves its output results', which overlaps with what get-actor-run and get-dataset-items already do. An agent may be unsure whether to call the actor tool once, or call it and then chain into the generic retrieval tools.
Four of five names follow a clean verb_noun kebab-case pattern (abort-actor-run, get-actor-run, get-dataset-items, get-key-value-store-record). The fifth, plainfold--company-hiring-signals, is a vendor-namespaced actor identifier with a double hyphen, breaking the otherwise consistent scheme.
Five tools is a workable count, but four of them are generic run/storage plumbing and only one delivers the advertised hiring-signals capability, leaving the domain surface thin. The scaffolding is defensible for an Actor-wrapper server, yet the set feels lopsided.
Run lifecycle is covered for a single run (start via the actor tool, poll, abort, read outputs), but there is no way to list runs, datasets, or key-value stores, and no schema/input-discovery tool. For a hiring-signals server, agents also cannot batch or compare companies in one call, forcing repeated single-company invocations.
Available Tools
5 toolsabort-actor-runAbort Actor runADestructiveIdempotentInspect
Abort an Actor run that is currently starting or running. For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request.
USAGE:
Use when you need to stop a run that is taking too long or misconfigured.
USAGE EXAMPLES:
user_input: Abort run y2h7sK3Wc
user_input: Gracefully abort run y2h7sK3Wc
Inputs: runId (required), gracefully. Returns: tip, runId, stats, status, +10 more
get-actor-runGet Actor runARead-onlyIdempotentInspect
Get detailed information about a specific Actor run.
Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep.
summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available.").
nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=...").
waitSecs (0–45, default 30) waits up to that many seconds for terminal status before returning.
USAGE:
Use to check the status of a run started by any Actor-running tool.
Pass waitSecs > 0 to block until terminal (or until the cap elapses).
USAGE EXAMPLES:
user_input: Show details of run y2h7sK3Wc
user_input: Wait for run y2h7sK3Wc to finish
Inputs: runId (required), waitSecs. Returns: tip, runId, stats, status, +10 more
get-dataset-itemsGet dataset itemsARead-onlyIdempotentInspect
Get items (rows) from a dataset — the output/results produced by an Actor run. Returns the rows themselves, not dataset metadata, counts, or a schema. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly. Default limit is 20. Use clean=true to skip empty items and hidden fields.
USAGE:
Use when you need to read data from a dataset (all items or only selected fields).
USAGE EXAMPLES:
user_input: Retrieve results from dataset abc123
user_input: Get only metadata.url and title from dataset username~my-dataset
Inputs: datasetId (required), desc, omit, clean, +4 more. Returns: items, limit, offset, summary, +5 more
get-key-value-store-recordGet key-value store recordARead-onlyIdempotentInspect
Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically.
USAGE:
Use when you need to retrieve a specific record (JSON, text, or binary) from a store.
USAGE EXAMPLES:
user_input: Get record INPUT from store abc123
user_input: Get record data.json from store username~my-store
Inputs: recordKey (required), keyValueStoreId (required). Returns: key, value, summary, contentType, +1 more
plainfold--company-hiring-signalsplainfold/company-hiring-signalsADestructiveInspect
This tool calls the Actor "plainfold/company-hiring-signals" and retrieves its output results. Actor description: Get any company's open jobs from its website: auto-detects Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee & more. Normalized jobs plus a hiring summary: departments, locations, new roles, velocity. No API key. $0.003/company, $0.001/job, $0.0005/run.
Inputs: companies (required), waitSecs, remoteOnly, includeJobs, +5 more. Returns: tip, runId, stats, status, +10 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Open jobs from any company's Greenhouse, Lever, Ashby, Workday and other ATS boards, with signals.
Open jobs from Workday, careers pages and ATSes, plus hiring, tech, intent, DMARC and launch signals
Is a company hiring, for what, and where? Open roles by company domain, live from its ATS.
1Open jobs and hiring changes per company, daily. Free keyless lookup. AI-compiled from job boards.
Related MCP Servers
- AlicenseAqualityBmaintenanceDetects hiring intent signals by scanning job boards for specific companies. Returns structured role data for outbound sales targeting.1369 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to discover applicant tracking system job boards from company domains, list open roles, detect hiring changes over time, and generate hiring summaries across multiple ATS platforms.MIT

company-jobs-feedofficial
AlicenseAqualityAmaintenanceLive open jobs from companies' own Greenhouse, Lever and Ashby boards via their official public APIs, with publish-verified dates, age, long-open and repost signals, filters and change tracking.5MIT- AlicenseNot gradedqualityBmaintenanceEnables live reads of public job boards across Greenhouse, Lever, Ashby, Personio, Pinpoint, and Gem, including fetching boards, resolving companies, checking whether jobs remain open, and retrieving full job details. Supports location- and role-based searches of verified starter boards plus paid multi-company search and monitoring with history, new/closed, and repost signals.68 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.