Home / MCP registry index / app.trickl/trickl
Trickl
app.trickl/trickl in the official MCP registry.
Endpoint https://api.trickl.app/mcp/dev.
The registry describes it as: Trickl for AI assistants: full docs, setup plans, and sandbox tools to test purchases end to end.
We read its 10 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
get_started search_docs read_doc check_api_key register_test_provider create_test_goal get_goal simulate_goal_event cancel_test_goal list_webhook_deliveries
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-trickl-trickl)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.