Home / MCP registry index / ca.bluecraneworks/forms
ca.bluecraneworks/forms
ca.bluecraneworks/forms in the official MCP registry.
Endpoint https://mcp.bluecraneworks.ca/mcp. Source: github.com/tstuckle/bluecrane-forms-mcp.
The registry describes it as: Canadian contractor forms + tax tools: 126 cited forms, sourced 2026 tax estimates by province.
We read its 8 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
search_forms get_form which_form_do_i_need list_categories estimate_contractor_tax required_hourly_rate hst_quick_method get_form_maker_pass
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ca-bluecraneworks-forms)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.