Home / MCP registry index / io.usefulapi/wufoo
Wufoo MCP by usefulapi
io.usefulapi/wufoo in the official MCP registry.
Endpoint https://wufoo.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read forms, fields, entries, reports and comments by field title, and submit entries.
We read its 18 tools on 2026-10-21. 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
wufoo_list_forms wufoo_get_form wufoo_get_form_fields wufoo_list_form_entries wufoo_get_labeled_entries wufoo_count_form_entries wufoo_list_form_comments wufoo_count_form_comments wufoo_list_reports wufoo_get_report wufoo_get_report_fields wufoo_list_report_entries wufoo_count_report_entries wufoo_list_report_widgets wufoo_list_users wufoo_submit_entry wufoo_add_webhook wufoo_delete_webhook
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-wufoo)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.