Home / MCP registry index / io.github.alexeibespalov/trident
io.github.alexeibespalov/trident
io.github.alexeibespalov/trident in the official MCP registry.
Endpoint https://mcp.tridentchart.com/mcp. Source: github.com/alexeibespalov/tridentpublic.
The registry describes it as: Create and edit collaborative architecture diagrams with any AI assistant using the Trident 2D DSL.
We read its 23 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
get_trident_spec get_generator_guide get_comprehensive_example validate_trident get_quick_start open_document get_document_summary get_recent_changes add_node update_node delete_node add_container update_container delete_container add_connection delete_connection get_document_png add_annotation update_annotation delete_annotation update_canvas_graphic make_suggestion explain
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-alexeibespalov-trident)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.