Hosted MCP server/Search

Applystead MCP server

Hosted at applystead.com·Streamable HTTP

Applystead publishes open jobs from employers' own career sites through an MCP server at https://applystead.com/mcp. Three public read-only tools, search_jobs, get_company_jobs and check_job_posting, need no sign-in and allow 60 requests a minute from one address. Account tools act on the member's own Applystead plan and open a sign-in page the first time they need the account. The provider also publishes a developer API and free job feeds.

applystead.com Streamable HTTP No sign-in for job search; OAuth for account tools Source checked Nov 12, 2026 Server responded when checked Reviewed 2026-11-16
About

Where it fits

Job seekers and job-board builders who want live openings from employer career sites inside an assistant, with optional account actions for Applystead members.

  • Search open jobs by title, company, remote country or posting age.
  • List a company's open roles and its ten newest jobs.
  • Check whether a job posting URL is open, closed or unsupported.

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.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Applystead as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http applystead https://applystead.com/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://applystead.com/mcp
Host
applystead.com · /mcp
Transport
Streamable HTTP
Authentication
No sign-in for job search; OAuth for account tools
Server name
applystead
Listing type
Community or directory listing

The installer uses the server name applystead. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

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.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that applystead appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Search open jobs by title, company, remote country or posting age. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server responded when checked

We reached applystead.com when we checked. That only means the address answered; it does not prove the MCP connection, sign-in, or tools work. The provider page was available when we checked.

Provider page available on Nov 12, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

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 sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • 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.
Review path

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.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Applystead documentationhttps://applystead.com/developers