Open jobs read from a company's own careers system: Greenhouse, Ashby, Lever.
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
find_job_boardGiven a company website, find which applicant tracking system it uses and the board token needed to read its jobs.Given a company website, find which applicant tracking system it uses and the board token needed to read its jobs.
No input schema was published for this tool.
list_jobsList all currently open roles at a company. Accepts a plain company website — the job board is detected automatically.List all currently open roles at a company. Accepts a plain company website — the job board is detected automatically.
No input schema was published for this tool.
detect_changesReport what changed in a company hiring since the last time this tool looked at it: roles opened, roles closed, titles or locations changed, compensation changed.Report what changed in a company hiring since the last time this tool looked at it: roles opened, roles closed, titles or locations changed, compensation changed.
No input schema was published for this tool.
hiring_summarySummarise what a company is hiring for right now: how many open roles, which functions they fall into (engineering, sales, AI/ML, security, data...), and where they are located.Summarise what a company is hiring for right now: how many open roles, which functions they fall into (engineering, sales, AI/ML, security, data...), and where they are located.
No input schema was published for this tool.
4 of 4 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Open jobs read from a company's own careers system: Greenhouse, Ashby, Lever.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.