Home / MCP registry index / app.turnale/turnale
app.turnale/turnale
app.turnale/turnale in the official MCP registry.
Endpoint https://mcp.turnale.app/. Source: github.com/turnale-app/turnale.
The registry describes it as: Run racket-sport tournaments from your AI assistant: fair draws, scores, live standings.
We read its 30 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
ping create_tournament add_players update_player remove_player set_pairs update_settings promote_player generate_draw get_briefing list_players list_matches get_schedule get_standings get_results get_audit_log get_export get_pdf_link get_pdf record_results replace_player withdraw_player swap_partners reschedule end_tournament undo_last_change delete_tournament record_feedback suggest_format get_player_template
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-turnale-turnale)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.