Home / MCP registry index / io.github.stand-out-of-my-sun/diogenes-dev-utilities-mcp
Diogenes Dev & Data Utilities MCP
io.github.stand-out-of-my-sun/diogenes-dev-utilities-mcp in the official MCP registry.
Endpoint https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities. Source: github.com/stand-out-of-my-sun/diogenes-dev-utilities-mcp.
The registry describes it as: JSON healing, O(n) ReDoS defense, XML prompt compilation, and schema verification tools.
We read its 14 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
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
heal_malformed_json enforce_json_schema_types extract_structured_json_entities clean_tabular_dataset synthesize_safe_regex compile_xml_agent_prompt synthesize_python_automation_code summarize_technical_document synthesize_web_intelligence_brief verify_context_compaction_fidelity route_mcp_workflow_plan arbitrate_agent_deliverable_escrow infer_mpp_streaming_session generate_x402_vector_embeddings
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-stand-out-of-my-sun-diogenes-dev-utilities-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.