Is com.keywordise/keywordise up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://keywordise.com/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://keywordise.com/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://keywordise.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 49 tools: answer_screening_question, cancel_subscription, create_account, create_api_key, delete_my_account, delete_saved_answer, describe_what_i_want, explain_job_match, export_my_data, get_account, get_apply_run_status, get_billing_portal_link, get_feed_reach, get_job_posting, get_match_status, get_my_cv_pdf, get_my_profile, get_profile_gaps, get_sent_cv_pdf, get_targeting, get_tracker, get_upgrade_link, list_api_keys, list_blocking_questions, list_countries_with_jobs, list_cv_designs, list_facts_to_provide, list_hidden_jobs, list_matching_jobs, list_my_applications, list_run_history, list_saved_answers, login, move_tracker_card, preview_tailored_cv, rate_job, refresh_matches, resend_verification_email, revoke_api_key, save_answer, set_cv_design, set_tracker_note, start_apply_run, stop_apply_run, suggest_keywords, unhide_job, update_profile, update_targeting, upload_cv.
Its tools changed between 2026-09 and 2026-10:
create_account: description changeddescribe_what_i_want: description changedexplain_job_match: description changedget_match_status: description changedget_my_profile: description changedget_upgrade_link: description, input schema changedlist_matching_jobs: description, input schema changedlist_my_applications: description changedpreview_tailored_cv: description changedrefresh_matches: description, input schema changedstart_apply_run: description changedstop_apply_run: description changedupload_cv: description changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.keywordise/keywordise |
|---|---|
| Endpoint | https://keywordise.com/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt