Home / MCP registry index / io.github.dreamworkhq/dreamwork
Dreamwork
io.github.dreamworkhq/dreamwork in the official MCP registry.
Endpoint https://mcp.dreamworkhq.com/mcp. Source: github.com/dreamworkhq/mcp.
The registry describes it as: Job search, application materials, and application tracking for AI assistants.
We read its 71 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
list_matches get_job save_job dismiss_match restore_match list_dismissed_matches get_pipeline move_pipeline mark_applied_offsite import_job cancel_apply generate_pack prepare_applications get_pack_status edit_cover_letter edit_resume format_resume edit_answer strengthen_application restore_material get_application_documents replace_application_document get_preferences update_preferences get_application_readiness save_application_answers parse_preferences_text get_career_record remember_hypothesis confirm_hypothesis forget_hypothesis get_resume_download_link get_resume_work_history get_communication_preferences update_communication_preferences get_autopilot_settings update_autopilot_settings get_autopilot_status set_autopilot get_application_status get_inbox get_unread_reminders mark_messages_read get_usage get_task list_tasks undo_last get_updates_since apply reply_to_recruiter start_checkout get_platform_context add_jobs get_application_materials update_application_materials reopen_application_materials generate_resume get_generated_resumes add_contact list_contacts and 11 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-dreamworkhq-dreamwork)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.