Home / MCP registry index / io.github.stand-out-of-my-sun/diogenes-gateway
Diogenes Autonomous Microservice Gateway
io.github.stand-out-of-my-sun/diogenes-gateway in the official MCP registry.
Endpoint https://diogenes-micro-gateway.corinth.workers.dev/mcp. Source: github.com/stand-out-of-my-sun/diogenes-micro-gateway.
The registry describes it as: Autonomous AI microservices: 55 dynamic guardrails, contract audits & oracles via L402/x402/MPP.
We read its 71 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
verify_agent_command_safety validate_sql_query_ast execute_python_sandbox audit_mcp_server_manifest detect_mcp_schema_rugpull validate_mcp_sampling_request sanitize_tool_output_stream redact_sensitive_pii detect_agent_action_loop verify_a2a_agent_card audit_outbound_egress_url audit_response_factuality audit_smart_contract_code scan_solana_cpi_reentrancy evaluate_solana_token_risk inspect_solana_token_liquidity track_solana_whale_flows estimate_solana_priority_fees decode_eip712_permit_signature simulate_evm_transaction_calldata evaluate_dex_mev_risk detect_address_poisoning_scam verify_http402_payment_challenge estimate_bitcoin_mempool_fees plan_bitcoin_utxo_consolidation calculate_spot_swap_rate compare_crosschain_bridge_routes generate_gemini_completion execute_antigravity_agent conduct_deep_research_investigation operate_computer_use_agent search_gemini_grounded_web search_gemini_grounded_maps compile_mpp_research_dossier generate_gemini_embeddings analyze_omni_multimodal_input plan_robotics_spatial_trajectory generate_nano_banana_image generate_veo_cinematic_video compose_lyria_music_track synthesize_gemini_speech_audio process_live_audio_dialogue prune_context_skeleton plan_context_token_budget rerank_hybrid_rag_chunks apply_fuzzy_code_patch analyze_ast_symbol_graph audit_module_dependency_cycles isolate_stacktrace_root_cause compile_polyglot_type_schemas evaluate_deterministic_math schedule_critical_path_tasks evaluate_ab_statistical_significance detect_openapi_breaking_changes generate_boundary_test_vectors simulate_monte_carlo_risk diff_agent_memory_checkpoint heal_malformed_json enforce_json_schema_types extract_structured_json_entities and 11 more
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-gateway)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.