Servidor MCP de Keywordise

• Nombre en el registrocom.keywordise/keywordiseverificado en el registro MCP

El nombre en el registro está bajo keywordise.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-20
• Herramientas69
• El servidor se llamakeywordise
• Versión del servidor2.0.0
• Versión del protocolo2025-06-18

El 2026-10-20 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 191 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta449 ms
• Espacio en el contexto del agente≈ 8234 tokenslas definiciones de todas sus herramientas (69), que el agente lleva en cada turno
• Definiciones de herramientasA · 93 de 100
• Resultados tipados0 de 69 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 31 de 69

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• 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…

• 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).

• 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.

• 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.

• get_upgrade_link

  A checkout link for a paid plan from the active payment provider: Starter ($24.99/month, 500 applications a month) or Pro ($49/month, 1,000 a month; the default). The person opens it in a browser to pay; the account upgrades automatically…

• 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.

• 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.

• list_api_keys

  The active API keys on this account: prefix, label, created and last used. Never the key itself.

• create_api_key

  Mint an additional API key for this account, for another machine or assistant. Shown once. Five active keys maximum.

• 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.

• 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.

• 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.

• get_my_profile

  Use when the person asks what is on their profile or CV. Not needed before searching or applying: those tools read the saved CV themselves. The CV profile Keywordise holds for this account (name, contact, summary, skills, roles…

• upload_cv

  Use when the person shares or mentions their resume/CV ('here's my resume', 'use my CV'). Upload a CV file and turn it into the account's profile: the same parser the app uses reads the document into name, contact, summary, roles, skills…

• update_profile

  Change fields of the saved profile without re-uploading the CV. Send only the fields to change (full_name, contact_email, phone, location, city, address, postcode, professional_summary, skills, pinned_skills, languages, experience…

• 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.

• suggest_keywords

  Search keywords derived from the saved profile, useful as include_keywords in update_targeting.

• list_cv_designs

  The CV designs a tailored CV can be rendered in, with the account's current pick.

• set_cv_design

  Set the design every tailored CV is rendered in (a key from list_cv_designs).

• 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.

• 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…

• update_targeting

  Change targeting rules; send only the keys to change (remote_mode any|remote|hybrid|onsite, geo_scope worldwide|region|country, geo_countries [ISO-2], locations, include_keywords, exclude_keywords, title_allow, title_block, seniority…

• describe_what_i_want

  Use when the person says what they are looking for in their own words ('senior remote data roles in the US, no agencies'). Turn a plain sentence ('remote data roles in Germany or the Netherlands, senior, not agencies') plus the saved CV…

• 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.

• 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_matching_jobs

  Use when the person wants jobs or their best matches: 'find me jobs', 'my top matches', 'remote marketing jobs that fit my resume', 'what's new for me this week'. It already uses the saved CV, so there is no need to read the profile…

• 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.

• explain_job_match

  Use for 'is this job a good fit', 'why this match', 'what am I missing for this role'. 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…

• preview_tailored_cv

  Use for 'tailor my resume for this job' or 'what would you send for this one'. 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…

• 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.

• unhide_job

  Undo hide or dislike: the job returns to the feed and the negative signal is dropped.

• list_hidden_jobs

  The jobs this account hid or disliked, newest first, so one can be put back.

• 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. rebuild=true rebuilds the feed from scratch through the same…

• get_match_status

  Only for checking on a match or feed rebuild that is already running (after upload_cv, update_targeting or refresh_matches); to find or show jobs use list_matching_jobs. Live status of the latest match run (scanned, inserted, elapsed)…

• start_apply_run

  Use when the person says 'apply for me', 'apply to the best matches' or 'apply to this job' (pass job_id). Show them the jobs first. Start an application run: Keywordise takes up to `limit` of the matching jobs (same filters as…

• 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.

• stop_apply_run

  Use for 'stop applying', 'pause', 'hold off'. Ask the running application run to stop after the job it is on. Nothing is left half-done; applications already sent stay sent.

• list_my_applications

  Use for 'what did I apply to', 'any replies', 'status of 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…

• 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.

• 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…

• get_sent_cv_pdf

  The tailored CV PDF that went to the employer for one application, returned as a file.

• 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.

• 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.

• delete_saved_answer

  Remove one answer from the answer book (an answer_id from list_saved_answers).

• 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.

• get_tracker

  The tracker board: applications grouped by the stage the person set (saved, applied, interview, offer, rejected) with their own notes.

• move_tracker_card

  Set the tracker stage of one application: saved, applied, interview, offer or rejected.

• set_tracker_note

  Replace the person's own note on one tracked application (interview date, contact, next step).

• get_live_job_counts

  Use for 'how many jobs are there' or before quoting a number. The size of the live job pool Keywordise can apply to right now, from the same measurement the keywordise.com homepage prints: all live jobs, how many were found in the last 30…

• search_live_jobs

  Use for 'find remote data engineer jobs', 'nursing jobs in Germany', 'what is new in marketing this week'. Searches the WHOLE live job pool (about two million open jobs), not only the person's matches, and needs no CV. Words must all…

• get_live_job

  The full posting text of one live job from search_live_jobs (pool_job_id): title, employer, place, date and the description. For a job in the person's own matches use get_job_posting.

• get_public_job

  Use when the person gives a Keywordise job id (ten characters) or a keywordise.com/jobs link, for example 'tell me about job abcde23456'. Returns what the public page of that job shows: title, employer, place, date and a plain summary of…

• apply_to_public_job

  Use for 'Apply to Keywordise job abcde23456' or when the person asks to apply to a job from keywordise.com/jobs. Finds that job, puts it into the person's matches and starts the same application as the Apply button for that ONE job…

• apply_to_live_job

  Use after search_live_jobs when the person picks one of the results to apply to. The same as apply_to_public_job, for a pool_job_id: puts the job into the person's matches and starts the application for that ONE job, which SUBMITS in the…

• get_referrals

  Use for 'what is my referral code', 'how much did I earn from referrals', 'who signed up through me'. The person's referral code and link, the share they earn (and the discount a friend gets), their stats (signups, paying customers…

• set_referral_code

  Set or change the person's own referral code (letters, digits and dashes, shown in their referral link). Fails with the app's own sentence when the code is taken or not allowed.

• claim_referral_code

  Record that the person was referred by the owner of a referral code, for the discount and the friend's credit. Allowed once, before the first payment; fails with the app's own sentence otherwise.

• get_inbox_address

  The email address Keywordise uses on the person's applications (employers reply to it), whether replies are also forwarded to their own mailbox, and whether applying by email is active.

• list_inbox

  Use for 'any replies?', 'did anyone get back to me?'. The person's Inbox: one thread per application with the employer's results (interview invitations, rejections, requests), unread count, newest first. Read one with read_inbox_message.

Las primeras 60 de 69, en el orden del servidor.