Keywordise is an MCP server with 49 tools an agent can call, among them answer_screening_question, cancel_subscription, create_account. It answers at https://keywordise.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Auto-apply to jobs: matches your CV, tailors a fresh CV per posting, and applies for you.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
answer_screening_question | Record the person's answer to one screening question on one application. The answer is written in the person's name and saved to their answer book, so the same question is never asked again. When it is the last required answer, the applicat Inputs: application_id, question_id, answer |
cancel_subscription | Cancel the Pro subscription at the end of the current billing period. Access stays until then. Irreversible from here; the person can resubscribe later. |
create_account | Register a new Keywordise account from the terminal and receive an API key for it. Requires accept_terms=true: the person accepts the Terms and Privacy Policy (https://keywordise.com/terms) and authorises Keywordise to apply for jobs on the Inputs: email, password, accept_terms |
create_api_key | Mint an additional API key for this account, for another machine or assistant. Shown once. Five active keys maximum. Inputs: label |
delete_my_account | Erase the account and everything in it: profile, CV files, matches, applications, answers, keys. Irreversible. Requires confirm_email equal to the account's address. Inputs: confirm_email |
delete_saved_answer | Remove one answer from the answer book (an answer_id from list_saved_answers). Inputs: answer_id |
describe_what_i_want | Turn a plain sentence ('remote data roles in Germany or the Netherlands, senior, not agencies') plus the saved CV into concrete targeting rules. Returns the inferred rules and the chips a person would confirm; with apply=true they are saved Inputs: sentence, preset, apply |
explain_job_match | For one vacancy: the match percentage, the requirements this account's CV covers and the ones it is missing. With narrative=true, also a short written assessment with strengths and gaps (a paid model call; limited to 60 per hour). Inputs: job_id, narrative |
export_my_data | The account's complete data as one JSON file (profile, targeting, matched jobs, applications, saved answers, run history, audit trail). Returned as a file; large accounts are told to download it in the app instead. |
get_account | The account behind this key: email and whether it is confirmed, plan state (trial days left, applications used and remaining, subscription), and how many API keys are active. |
get_apply_run_status | Live progress of the latest run: running or not (from a heartbeat, not a status claim), processed of total, the job being worked on now, confirmed, needs review, skipped, closed. |
get_billing_portal_link | A link to the payment provider's customer portal for this account's subscription, where invoices, the payment method and cancellation live. |
get_feed_reach | How many jobs the current targeting shows versus how many each single rule is hiding, and which one change would widen the feed most. Every number comes from re-asking the feed's own predicate with one control relaxed. |
get_job_posting | The full description of one matched vacancy, with a short summary and highlights, plus the link that opens the posting from the app. Inputs: job_id |
get_match_status | Live status of the latest match run (scanned, inserted, elapsed) and the feed counts it produced, for polling after upload_cv, update_targeting or refresh_matches. |
get_my_cv_pdf | The account's base CV (the saved profile, untailored) rendered as a PDF in the chosen design, returned as a file. No model call. Inputs: design |
get_my_profile | The CV profile Keywordise holds for this account (name, contact, summary, skills, roles, education), the job-targeting rules (countries, remote preference, keywords) and the plan status (applications remaining). Call this first. |
get_profile_gaps | The gaps in the saved profile that weaken applications (missing dates on a role, no contact phone, empty summary, …), each with a severity, so they can be fixed with update_profile. |
get_sent_cv_pdf | The tailored CV PDF that went to the employer for one application, returned as a file. Inputs: application_id |
get_targeting | Every targeting rule the feed and the apply run obey: remote mode, geo scope and countries, locations, include/exclude keywords, title allow/block lists, seniority, salary, languages, work authorisation, company allow/block, daily and per-c |
get_tracker | The tracker board: applications grouped by the stage the person set (saved, applied, interview, offer, rejected) with their own notes. |
get_upgrade_link | A checkout link for the Pro plan ($49/month, 200 applications a month) from the active payment provider. The person opens it in a browser to pay; the account upgrades automatically when the payment lands. |
list_api_keys | The active API keys on this account: prefix, label, created and last used. Never the key itself. |
list_blocking_questions | Questions employers asked on applications that are stalled until this account answers them, grouped by application, each with a suggested answer drawn from what the person answered before. Answer with answer_screening_question. Inputs: limit |
list_countries_with_jobs | The countries the live pool actually has inventory in (ISO-2, name, job count), for choosing geo_countries in update_targeting. |
list_cv_designs | The CV designs a tailored CV can be rendered in, with the account's current pick. |
list_facts_to_provide | The universal screening facts this account has not answered yet (right to work, notice period, salary expectation, …), ranked by how many waiting applications each one unblocks. Answer them with save_answer. |
list_hidden_jobs | The jobs this account hid or disliked, newest first, so one can be put back. |
list_matching_jobs | Live vacancies matched to this account's CV, ranked. Each job carries a calibrated match percentage, a recruiter-pass verdict with a one-line reason, and whether an application was already sent. Filter by match tier and freshness; page with Inputs: limit, offset, sort, match, fresh, applied |
list_my_applications | Every application sent for this account: company, title, stage, outcome, when it went out, how many screening questions it still waits on, and the employer's acknowledgement where one was received. Inputs: limit, only_waiting_on_me, include_cover_letter |
list_run_history | The last five match runs and the last five application runs, with their counts and status. |
list_saved_answers | The answer book: every screening answer this account has given or taught, which future applications reuse automatically in any phrasing or language. |
login | Exchange the account's email and password for a new API key, so a terminal or an assistant can act on the account. The key is shown once; keep it. Up to five keys may be active per account (revoke_api_key frees a slot). Inputs: email, password, label |
move_tracker_card | Set the tracker stage of one application: saved, applied, interview, offer or rejected. Inputs: application_id, stage |
preview_tailored_cv | Rewrite this account's CV for one vacancy the way Keywordise would send it: headline, summary, the roles selected for this job with rewritten bullets, curated skills and a cover letter, every segment labelled tailored, verbatim or pinned. N Inputs: job_id |
rate_job | Feedback on one job: hide or dislike removes it from the feed and teaches the matcher what this person rejects; interested is a positive signal. Undo with unhide_job. Inputs: job_id, action, reason |
refresh_matches | Match the account's CV against the vacancies added since it last looked, in the background. Idempotent and cheap when nothing is new. force=true runs a full re-match regardless. Inputs: force |
resend_verification_email | Send the email-confirmation link again to this account's address. Applying is blocked until the address is confirmed; nothing else is. |
revoke_api_key | Revoke one of this account's API keys immediately. Any terminal or assistant using it stops working at once. Revoking the key you are calling with ends this session. Inputs: key_id |
save_answer | Add or replace a screening answer in the answer book ('What is your notice period?' → '1 month'). Applications already waiting on that fact are completed and sent in the background. Only save what the person actually stated. Inputs: question, answer, kind, options |
set_cv_design, set_tracker_note, start_apply_run, stop_apply_run, suggest_keywords, unhide_job, update_profile, update_targeting, upload_cv
Every block below points at https://keywordise.com/mcp. Pick your client and copy.
claude mcp add --transport http keywordise https://keywordise.com/mcp
{
"mcpServers": {
"keywordise": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://keywordise.com/mcp"]
}
}
}{
"mcpServers": {
"keywordise": {
"url": "https://keywordise.com/mcp"
}
}
}{
"servers": {
"keywordise": {
"type": "http",
"url": "https://keywordise.com/mcp"
}
}
}{
"context_servers": {
"keywordise": {
"url": "https://keywordise.com/mcp"
}
}
}{
"mcpServers": {
"keywordise": {
"serverUrl": "https://keywordise.com/mcp"
}
}
}{
"mcpServers": {
"keywordise": {
"url": "https://keywordise.com/mcp"
}
}
}name: Keywordise
version: 0.0.1
schema: v1
mcpServers:
- name: Keywordise
type: streamable-http
url: https://keywordise.com/mcp{
"mcpServers": {
"keywordise": {
"httpUrl": "https://keywordise.com/mcp"
}
}
}{
"mcpServers": {
"keywordise": {
"type": "http",
"url": "https://keywordise.com/mcp"
}
}
}{
"mcpServers": {
"keywordise": {
"url": "https://keywordise.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fkeywordise.com%2Fmcp&type=streamable_http&id=keywordise&name=Keywordise
It answered our last check on 17 October 2026 in 112 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by keywordise.com and served from keywordise.com, the vendor's own domain: https://keywordise.com/mcp.
49, as returned by the server's own tools/list on 1 September 2026: answer_screening_question, cancel_subscription, create_account, create_api_key, delete_my_account, delete_saved_answer, describe_what_i_want, explain_job_match, and 41 more.
It answered our last check on 17 October 2026 in 112 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://keywordise.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.keywordise. Endpoint host: keywordise.com. ARD identifier: urn:air:com.keywordise:mcp:keywordise.
First indexed 1 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.