Home / MCP registry index / com.ortexo/mcp
Ortexo
com.ortexo/mcp in the official MCP registry.
Endpoint https://mcp.ortexo.com/mcp.
The registry describes it as: Romanian and EU legislation and case law, with exact article citations and point-in-time text.
We read its 30 tools on 2026-10-28. 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_semantic search_lexical lookup_article lookup_articles lookup_decision lookup_article_historical lookup_article_at_date get_related get_related_batch check_status search_amending_acts compare_article find_act describe_corpus verify_citations get_act_structure scan_act_for_terms search_eu_law lookup_eu_article search_eu_jurisprudence lookup_eu_decision get_eu_related eu_cited_in_romania lookup_eu_article_at_date lookup_eu_articles get_eu_act_structure eu_check_status compare_eu_article lookup_eu_article_historical eu_transposition
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-ortexo-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.