Home / MCP registry index / co.asksteps/asksteps
asksteps
co.asksteps/asksteps in the official MCP registry.
Endpoint https://mcp.asksteps.co/mcp.
The registry describes it as: Turn a fillable PDF into an online form, build funnels, read submissions.
We read its 24 tools on 2026-10-22. 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
asksteps_get_subscription asksteps_create_from_template asksteps_list_templates asksteps_assign_site asksteps_publish_form asksteps_import_pdf asksteps_list_forms asksteps_create_draft asksteps_get_capabilities asksteps_start_checkout asksteps_update_publication asksteps_delete_form asksteps_create_form asksteps_get_form asksteps_update_funnel asksteps_change_plan asksteps_list_themes asksteps_get_funnel asksteps_list_leads asksteps_search_docs asksteps_update_form asksteps_analyze_pdf asksteps_create_funnel asksteps_get_form_stats
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/co-asksteps-asksteps)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.