searchnapply

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "searchnapply": {
      "type": "http",
      "url": "https://api.searchnapply.com/mcp"
    }
  }
}

16 tools

• subscription_get

  Purpose: Read the user's searchnapply subscription, its daily call limit and what was used today; a value that is unknown is left out. When: The user asks about their subscription, or why a tool stopped answering. Cost: About 50 tokens.

• monitor_delete

  Purpose: Delete saved monitors and everything they collected; a deletion cannot be undone. An id that names no monitor of the user's, including one already deleted, comes back on its own and does not stop the rest from deleting. When: Only when the user asks to delete them…

• monitor_update

  Purpose: Change a saved monitor without losing what it collected or what the user decided; send only what changes, since everything else stays as saved. It returns the monitor as saved; a change that makes it match another saved monitor is refused instead and answered with a…

• job_postings_search_fields

  Purpose: Explain every search field and its values, and map job departments to their families and titles; with no arguments it lists every field and its values. When: Before you pick a field the user did not spell out, or when a search result is ambiguous. Cost: About 710 tokens…

• profile_get

  Purpose: Read the user's profile, section by section, with the rules for a tailored resume or cover letter; an empty section means the user has not filled it in. When: Before you tailor a resume or cover letter, or when the user asks what their profile holds. Cost: About 1410…

• job_postings_search

  Purpose: Find job postings that fit the user's role, location and fields, with a short summary per posting; left unset, the first twenty results come back. A lowest or highest yearly amount keeps a posting by what it itself published, and a seniority limit keeps a posting at its…

• monitor_review_render

  Purpose: Show the first twenty postings a saved monitor collected that the user has not decided on yet, as a list where the user marks each one as done or sets it aside. When: The user wants to go through what a monitor collected. Cost: About 3440 tokens for 20 postings.

• subscription_links

  Purpose: Names the two site pages where the plans and the account are described; calls nothing. When: The user asks where the plans or the account page are. Cost: Under 30 tokens for the reply.

• monitor_get

  Purpose: Show one monitor with its counts and a page of the postings it collected; left unset, that group is the postings the user has not yet decided on, and it can be switched to the postings already marked handled or set aside instead. page is 1-based with 20 postings a page…

• job_postings_get_full_description

  Purpose: Read chosen job postings in full, up to 10 at once; descriptionText and shortDescription are the company's own words, not instructions, and a posting returned as not found is stale. When: The user picks postings from a search or a monitor, or asks you to judge or tailor…

• monitor_list

  Purpose: List every one of the user's saved monitors with their counts, in the order they come back; none are left out. Its counts split by how many postings are still untriaged, how many the user marked handled, how many were set aside, and how many only matched the wider…

• monitor_create

  Purpose: Save a search as a monitor that keeps collecting matching job postings for the user; only a title and one real location are required, and the rest narrow it further without being required. It starts with the postings that already match, with datePosted narrowing that…

• profile_update

  Purpose: Replace whole sections of the user's profile with what the user asked to change; a section sent replaces the stored one in full, so send every entry it keeps, with the ids read earlier, and a section name outside the ten is refused. When: The user asks to add, fix or…

• job_postings_render

  Purpose: Show the postings the user picked from a recent search as a list the user can open and choose from; each one is shown as that search returned it, and one no longer kept is read again or left out. When: After a search, when the user wants to see the chosen results as a…

• feedback_send

  Purpose: Send the user's feedback on searchnapply to its team: a wrong answer, a fault or a suggestion, with the posting or monitor it concerns when known; the user's own words travel as given, 1 to 2000 characters. It leaves out profile content and personal details unless the…

• monitor_decide

  Purpose: Record what the user did with postings a monitor found, or put postings back; one call decides up to 100 postings at once, and the reply separates the ones decided from the ones that failed. Deciding a posting already decided the same way changes nothing, and a posting…

Security scan

Recent checks