Home / MCP registry index / io.github.snowbikemike/tascan-mcp
TaScan
io.github.snowbikemike/tascan-mcp in the official MCP registry.
Endpoint https://app.tascan.io/mcp. Source: github.com/snowbikemike/tascan-mcp.
The registry describes it as: 36 MCP tools for projects, tasks, workers, QR/NFC tags, and AI remediation. Task. Scan. Done.
We read its 142 tools on 2026-10-27. 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
tascan_list_projects tascan_create_project tascan_get_project tascan_update_project tascan_delete_project tascan_create_event tascan_list_events tascan_get_event tascan_update_event tascan_delete_event tascan_add_tasks tascan_get_signature_bundle tascan_dispatch_to_agent tascan_list_agents tascan_register_agent tascan_list_tasks tascan_get_task tascan_get_receipt tascan_update_task tascan_reply_with_list tascan_add_subtasks tascan_list_subtasks tascan_update_subtask tascan_complete_subtask tascan_delete_subtask tascan_delete_task tascan_complete_task tascan_list_workers tascan_create_worker tascan_update_worker tascan_generate_qr tascan_share_list tascan_apply_template tascan_list_templates tascan_get_report tascan_query_responses tascan_list_issues tascan_analyze_issue tascan_recommend_fix tascan_dispatch_instruction tascan_auto_resolve tascan_send_sms tascan_schedule_sms tascan_list_scheduled_sms tascan_cancel_scheduled_sms tascan_get_sms_status tascan_send_task_email tascan_register_tag tascan_list_tags tascan_get_scan_history tascan_search_marketplace tascan_invite_worker tascan_list_invites tascan_create_zone tascan_list_zones tascan_update_zone tascan_zone_compliance tascan_register_asset tascan_assess_condition tascan_condition_history and 82 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-snowbikemike-tascan-mcp)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.