Where it fits
Recruiters and analysts detecting hiring growth or freezes across Greenhouse, Lever, and Ashby with free snapshots.
- Run the npx install if the hosted endpoint is unavailable.
- Track job openings across Greenhouse.
- Detect hiring freezes on Lever.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Hiring Change Intelligence
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Hand the current conversation to a new background agent that picks up the work right away.
Turns a decision the user cannot fully answer into a questionnaire for someone else to fill in.
Covers writing documents for agents. Use it when creating or editing skills, or when modifying AGENTS.md or CLAUDE.md.
No skills found
Try a different search term or clear the filters.
Local npx install (fallback)
Runs the documented local stdio server. Use it as a fallback when the hosted endpoint is unreachable; the endpoint status is separate from the install path.
- Run the package
Start the local server with npx -y hiring-change-intelligence.
- Register it in your client
Add a local stdio server entry that runs npx with the argument -y hiring-change-intelligence, or merge the README's mcpServers JSON config.
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name hiring-change-intelligence. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
hiring-change-intelligenceappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Run the npx install if the hosted endpoint is unavailable. Check the result before you give the server more access.
- 3Check permissions.
The provider documents no credential for this endpoint, so there is no scope or token to review. Remove the server when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page was available when we checked.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The server connects but no tools appear. Confirm the URL and transport, then restart the client.
- The first tool call times out. Try a smaller request and check the provider's status or rate limits.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider source
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Hiring Change Intelligence repositoryhttps://github.com/contentforge-press/hiring-change-intelligence