Diogenes Dev & Data Utilities MCP
REMOTE · DIOGENES-MICRO-GATEWAY.CORINTH.WORKERS.DEV
JSON healing, O(n) ReDoS defense, XML prompt compilation, and schema verification tools.
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2549 tokens (~182/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 3 days we've observed: 10 tool removals, 0 breaking changes, 0 auth/transport breaks, 14 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +4
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 2.5.0 ▼ security
- Tool “agent_context_compaction_verifier” was removed ▼ security
- Tool “agent_hallucination_auditor” was removed ▼ security
- Tool “agent_mcp_router” was removed ▼ security
- Tool “agent_prompt_compiler” was removed ▼ security
- Tool “agent_schema_enforcer” was removed ▼ security
- Tool “clean_data” was removed ▼ security
- Tool “json_repair” was removed ▼ security
- Tool “mpp_agent_escrow_arbiter” was removed ▼ security
- Tool “regex_oracle” was removed ▼ security
- Tool “web_brief” was removed ▼ security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 44% → 100% ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: fair → excellent functional
- New tool “arbitrate_agent_deliverable_escrow” functional
- New tool “clean_tabular_dataset” functional
- New tool “compile_xml_agent_prompt” functional
- New tool “enforce_json_schema_types” functional
- New tool “extract_structured_json_entities” functional
- New tool “generate_x402_vector_embeddings” functional
- New tool “heal_malformed_json” functional
- New tool “infer_mpp_streaming_session” functional
- New tool “route_mcp_workflow_plan” functional
- New tool “summarize_technical_document” functional
- New tool “synthesize_python_automation_code” functional
- New tool “synthesize_safe_regex” functional
- New tool “synthesize_web_intelligence_brief” functional
- New tool “verify_context_compaction_fidelity” functional
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 58
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=corinth.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 633c3321385182b27c585c86398dc860724 |
| SANs: *.corinth.workers.dev, corinth.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of diogenes-micro-gateway.corinth.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities | Verified | 200 | |
| http (plaintext) | http://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
arbitrate_agent_deliverable_escrow Multi-Agent Task Deliverable & Contract Fulfillment Escrow Arbiter ~212
Evaluates a worker agent's submitted task deliverable against agreed contract acceptance criteria to issue a deterministic escrow settlement verdict ('RELEASE_FUNDS_TO_WORKER_AGENT', 'REQUEST_REVISION', or 'REFUND_CLIENT'). Use when settling multi-agent bounties or verifying subcontractor deliverables before releasing MPP/L402 escrow funds; for checking syntactic JSON Schema property types without evaluating semantic contract terms, use enforce_json_schema_types instead. Read-only call (32 KB, 60 RPM): accepts 'deliverable' (with enum defaults), uses '?demo=true' or MPP (150 sats); HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| arbitration_standard | string | – | Strictness of contract verification; defaults to 'strict_all_criteria' when omitted. |
| deliverable | string | yes | JSON string or text deliverable submitted by the worker agent. |
| terms | string | – | Contract acceptance criteria that the deliverable must satisfy; defaults to 'Complete verified JSON deliverable' when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| arbitration_notes | string | yes | Detailed justification citing satisfied or missing contract clauses. |
| contract_satisfied | boolean | yes | True when the deliverable fulfills all stated contract terms. |
| escrow_action | string | yes | Settlement command ('RELEASE_FUNDS_TO_WORKER_AGENT', 'REQUEST_REVISION', or 'REFUND_CLIENT'). |
| quality_score | integer | yes | Deliverable quality score from 0 to 100. |
No examples provided.
clean_tabular_dataset Tabular Dataset & Text Deduplication, Whitespace & Normalization Engine ~175
Deduplicates repetitive lines or records, normalizes Unicode whitespace, strips HTML/control noise, and canonicalizes tabular text or JSON arrays. Use when cleaning noisy scraped lists, CSV rows, or duplicate log lines before indexing or analysis; for extracting typed JSON fields from free-form prose paragraphs, use extract_structured_json_entities instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'data' ('normalization_mode' defaults to 'exact_match'), supports '?demo=true' or L402 (100 sats), and returns HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | Raw newline-delimited text, CSV rows, or JSON array string to deduplicate and normalize. |
| normalization_mode | string | – | Deduplication key sensitivity; defaults to 'case_insensitive_trim' when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| cleaned_count | integer | yes | Unique non-empty record count after cleanup. |
| cleaned_data | array | yes | Deduplicated, whitespace-normalized records. |
| duplicates_removed | integer | yes | Number of duplicate records eliminated. |
| original_count | integer | yes | Line or record count prior to deduplication. |
No examples provided.
compile_xml_agent_prompt Production XML-Structured System Prompt & Guardrail Compiler ~180
Compiles a raw task description into a structured XML system prompt (<role>, <context>, <objective>, <constraints>, <workflow>, <output_format>) engineered to prevent instruction drift. Use when authoring or upgrading a system prompt for an autonomous agent or sub-agent workflow; for mapping a task objective to a concrete sequence of MCP tool calls, use route_mcp_workflow_plan instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'task' ('prompt_style' defaults to 'anthropic_xml_tags'), supports '?demo=true' or L402 (100 sats), and returns HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt_style | string | – | Structural formatting template; defaults to 'anthropic_xml_tags' when omitted. |
| task | string | yes | Raw task instructions, persona goal, and operational constraints to compile. |
| Name | Type | Req | Description |
|---|---|---|---|
| compiled_prompt | string | yes | Complete production-grade XML-structured system prompt. |
| estimated_tokens | integer | yes | Estimated BPE token length of the compiled prompt. |
| key_enhancements | array | yes | Specific guardrails and output contract rules injected. |
| optimization_score | integer | yes | Prompt clarity and constraint-completeness score from 0 to 100. |
No examples provided.
enforce_json_schema_types Strict JSON Schema Validator, Type Coercer & Field Pruner ~191
Validates a raw LLM output object against a target JSON Schema, automatically coercing mismatched scalar types (e.g. string '42' to integer 42), injecting schema defaults, and pruning undeclared hallucinated fields. Use when enforcing schema compliance and type safety on structured LLM outputs before passing them to typed APIs; for healing unparseable raw JSON text with broken quotes or trailing commas, use heal_malformed_json instead. Read-only edge call (32 KB, 60 RPM): accepts 'raw_output' (with enum defaults), uses '?demo=true' or L402 (75 sats); HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| coercion_policy | string | – | Policy for handling extra undeclared properties; defaults to 'prune_undeclared_and_coerce' when omitted. |
| raw_output | string | yes | JSON string or object produced by an LLM to validate and coerce. |
| Name | Type | Req | Description |
|---|---|---|---|
| coercions_applied | array | yes | List of type conversions and default injections performed. |
| enforced_object | object | yes | Clean, schema-compliant JSON object. |
| unrecognized_fields_pruned | array | yes | Hallucinated property keys removed during enforcement. |
| valid | boolean | yes | True when the resulting enforced_object satisfies the schema. |
No examples provided.
extract_structured_json_entities Unstructured Text to Typed JSON Entity & Record Extractor ~174
Extracts structured JSON records, named entities, dates, and financial figures from unstructured prose, emails, or HTML/Markdown dumps. Use when converting unstructured natural-language text into a structured JSON array of entities; for validating and coercing an existing JSON payload against a formal JSON Schema, use enforce_json_schema_types instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'text' ('extraction_target' defaults to 'general_entities_and_metrics'), supports '?demo=true' or L402 (150 sats), and returns HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| extraction_target | string | – | Primary entity domain to extract; defaults to 'general_entities_and_metrics' when omitted. |
| text | string | yes | Unstructured document, email body, or webpage text to extract structured entities from. |
| Name | Type | Req | Description |
|---|---|---|---|
| extracted_data | object | yes | Structured JSON object or array containing the extracted entities. |
| model | string | yes | Extraction model executed ('gemini-3.8-flash'). |
| records_count | integer | yes | Number of distinct entity records extracted. |
| success | boolean | yes | True when entity extraction succeeded. |
No examples provided.
generate_x402_vector_embeddings Solana x402 USDC-Settled Semantic Vector Embedding Generator ~164
Generates normalized high-dimensional semantic vector embeddings settled via Solana SPL USDC ('x402' protocol headers) for decentralized RAG pipelines. Use when computing text embeddings paid via Solana USDC x402 signatures rather than Bitcoin Lightning; for extracting discrete JSON entities from unstructured text, use extract_structured_json_entities instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'text' ('encoding_format' defaults to 'float_array'), supports '?demo=true' or x402 (100 sats), and returns HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| encoding_format | string | – | Vector serialization format; defaults to 'float_array' when omitted. |
| text | string | yes | Input text string or document chunk to convert into a normalized embedding vector. |
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | integer | yes | Number of float dimensions in the returned vector. |
| embedding | array | yes | Normalized floating-point vector array. |
| model | string | yes | Embedding model executed ('gemini-embedding-2'). |
| normalized | boolean | yes | Always true; vectors are L2-normalized to unit length. |
No examples provided.
heal_malformed_json Deterministic Malformed JSON Syntax & Truncation Healer ~170
Deterministic JSON syntax repair: normalizes quotes, unclosed brackets, and boolean literals into compliant RFC 8259 JSON structure without data deletion. Use when fixing syntax-broken JSON strings that fail JSON.parse(); for coercing field types and verifying properties on already-parseable JSON objects against a target JSON Schema, use enforce_json_schema_types instead. Read-only edge call (32 KB, 60 RPM): accepts 'malformed_json' (with enum defaults), uses '?demo=true' or L402 (50 sats); HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| malformed_json | string | yes | Raw broken, truncated, or markdown-wrapped JSON string to repair. |
| repair_mode | string | – | Bracket-closing and literal-normalization strategy; defaults to 'heuristic_fast' when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| fixes_applied | array | yes | List of lexical repairs performed. |
| parsed_object | object | yes | Deserialized JSON object produced from the repaired string. |
| repaired_json | string | yes | Valid RFC 8259 JSON string after syntax healing. |
| status | string | yes | Repair outcome ('repaired' or 'valid_as_is'). |
No examples provided.
infer_mpp_streaming_session Base EVM Machine Payments Protocol (MPP) Streaming Session Planner ~195
Initializes a Base USDC Machine Payments Protocol (MPP) metered inference session, allocating a streaming token quota and returning a step-by-step execution plan. Use when running session-metered agent planning settled via Base EVM MPP 'Payment-Challenge' headers; for mapping a task goal to L402 MCP tool calls without opening an MPP streaming session, use route_mcp_workflow_plan instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'task' ('token_quota_tier' defaults to 'compact_1024'), supports '?demo=true' or MPP (500 sats), and returns HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | Agent workflow task to execute within the metered MPP session. |
| token_quota_tier | string | – | Allocated streaming token ceiling for the session; defaults to 'standard_4096' when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| plan | array | yes | Ordered execution steps generated for the task. |
| session_id | string | yes | Unique MPP streaming session identifier. |
| session_status | string | yes | Session lifecycle state ('ACTIVE_STREAMING'). |
| streaming_tokens_allocated | integer | yes | Token budget reserved for the session. |
No examples provided.
route_mcp_workflow_plan Autonomous Goal-to-MCP Tool Sequence Router & Cost Planner ~191
Maps a natural-language agent goal to an ordered sequence of Diogenes MCP tool calls with exact endpoint paths, JSON-RPC 2.0 payloads, and cumulative satoshi cost estimates. Use when planning which MCP tools to chain together to solve a multi-step objective within a satoshi budget; for compiling a static XML system prompt rather than an executable MCP tool call sequence, use compile_xml_agent_prompt instead. Read-only edge call (32 KB, 60 RPM): accepts 'objective' ('budget_preference' defaults to 'lowest_sats_deterministic'), uses '?demo=true' or L402 (100 sats); HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_preference | string | – | Cost vs depth routing trade-off; defaults to 'lowest_sats_deterministic' when omitted. |
| objective | string | yes | Natural-language description of the workflow goal to route across MCP tools. |
| Name | Type | Req | Description |
|---|---|---|---|
| deterministic_confidence | number | yes | Router confidence score from 0.80 to 1.0. |
| estimated_total_sats | integer | yes | Cumulative satoshi cost of the planned tool sequence. |
| objective | string | yes | Evaluated workflow objective. |
| recommended_sequence | array | yes | Ordered tool execution steps with tool name, endpoint, and cost_sats. |
No examples provided.
summarize_technical_document High-Density Technical Document & RFC Executive Summarizer ~166
Condenses long technical specifications, RFCs, research papers, or meeting transcripts into high-density executive bullet points preserving exact figures and decisions. Use when producing a human-readable executive summary of a single provided document; for researching a topic across the live web with Google Search citations, use synthesize_web_intelligence_brief instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'text' ('summary_format' defaults to 'executive_bullets'), supports '?demo=true' or L402 (100 sats), and returns HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| summary_format | string | – | Output presentation structure; defaults to 'executive_bullets' when omitted. |
| text | string | yes | Full document text, RFC, or transcript to summarize. |
| Name | Type | Req | Description |
|---|---|---|---|
| compression_achieved | boolean | yes | True when output length is <25% of input length. |
| model | string | yes | Summarization model executed ('gemini-3.8-flash'). |
| success | boolean | yes | True when summarization completed. |
| summary | string | yes | High-density technical summary text. |
No examples provided.
synthesize_python_automation_code Self-Contained Python Script, CLI & Parser Code Synthesizer ~176
Synthesizes PEP 8 compliant, self-contained Python 3 scripts, data parsers, and CLI utilities complete with type hints, docstrings, and inline assertion tests. Use when generating a standalone Python automation script or parser from a functional specification; for summarizing existing documentation or codebases into executive bullet points, use summarize_technical_document instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'prompt' ('dependency_policy' defaults to 'stdlib_only'), supports '?demo=true' or L402 (300 sats), and returns HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| dependency_policy | string | – | Allowed library dependencies in generated code; defaults to 'stdlib_only' when omitted. |
| prompt | string | yes | Functional specification, input/output formats, and edge cases for the Python script. |
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | Code synthesis model executed ('gemini-4-argon'). |
| output | string | yes | Complete Python 3 source code with inline verification assertions. |
| stdlib_only | boolean | yes | True if the generated script requires zero third-party pip packages. |
| success | boolean | yes | True when code synthesis succeeded. |
No examples provided.
synthesize_safe_regex Linear-Time O(n) ReDoS-Safe Regular Expression Synthesizer & Tester ~181
Synthesizes linear-time O(n) regular expressions free of catastrophic backtracking (ReDoS) and validates them against positive and negative test strings. Use when generating and verifying a regular expression pattern for input validation or lexical parsing; for repairing broken JSON syntax directly without writing custom regexes, use heal_malformed_json instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'description' ('flavor' defaults to 'ecmascript_js'), supports '?demo=true' or L402 (50 sats), and returns HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Natural-language specification of the text pattern to match (e.g. 'RFC 5322 email addresses excluding plus-aliases'). |
| flavor | string | – | Target regular expression engine syntax; defaults to 'ecmascript_js' when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | yes | Synthesized regular expression pattern string (without slash delimiters). |
| redos_safe | boolean | yes | True when static star-height analysis confirms zero exponential backtracking. |
| test_results | array | yes | Pass/fail verification results across positive and negative test cases. |
| time_complexity | string | yes | Worst-case matching complexity ('O(n)'). |
No examples provided.
synthesize_web_intelligence_brief Real-Time Google Search Grounded JSON Market Intelligence Brief ~183
Synthesizes a real-time market or technical intelligence brief grounded in live Google Search, returning strict JSON ('executive_summary', 'key_developments', 'sentiment', 'sources'). Use when fetching a structured JSON market/news brief with live web citations and sentiment classification; for summarizing caller-supplied text offline without live web search, use summarize_technical_document instead. Read-only edge call (32 KB, 60 RPM): accepts 'topic' ('focus' defaults to 'technical_and_market_catalysts'), supports '?demo=true' or L402 (200 sats), and returns HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | string | – | Analytical angle applied to the brief; defaults to 'technical_and_market_catalysts' when omitted. |
| topic | string | yes | Company, protocol, market sector, or technical topic to brief. |
| Name | Type | Req | Description |
|---|---|---|---|
| executive_summary | string | yes | Concise synthesis of current developments. |
| key_developments | array | yes | Dated factual developments grounded in search results. |
| sentiment | string | yes | Directional sentiment classification ('BULLISH', 'BEARISH', or 'NEUTRAL'). |
| sources | array | yes | Verified web source titles and URLs. |
| topic | string | yes | Researched intelligence topic. |
No examples provided.
verify_context_compaction_fidelity Pre/Post Context Compaction Information Retention Verifier ~191
Audits a compacted conversation summary against the original full context to detect dropped user constraints, lost file paths, altered numbers, or missing pending tasks. Use when verifying that an LLM context-compaction summary retained all task-critical facts before truncating history; for generating a new executive summary from a raw technical document, use summarize_technical_document instead. Read-only edge call (32 KB, 60 RPM): accepts 'original_context' ('compacted_summary' defaults to 'standard'), supports '?demo=true' or L402 (90 sats), and returns HTTP 400 if invalid.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_focus | string | – | Entity class prioritized during retention scoring; defaults to 'constraints_paths_and_numbers' when omitted. |
| compacted_summary | string | yes | Candidate compacted summary to audit for dropped constraints or entities. |
| original_context | string | yes | Full pre-compaction conversation history or task log. |
| Name | Type | Req | Description |
|---|---|---|---|
| missing_critical_entities | array | yes | Important entities or constraints dropped during compaction. |
| preserved_entities | array | yes | Critical constraints, paths, and numbers verified present in the summary. |
| retention_score | number | yes | Information preservation score from 0.0 to 1.0. |
| safe_to_resume | boolean | yes | True when retention_score >= 0.90 and zero critical constraints were lost. |
No examples provided.
How do I install the Diogenes Dev & Data Utilities MCP server?
Diogenes Dev & Data Utilities MCP is a hosted endpoint at https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · diogenes-micro-gateway.corinth.workers.dev
claude mcp add --transport http stand-out-of-my-sun-diogenes-dev-utilities-mcp 'https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities'
What is the Diogenes Dev & Data Utilities MCP server?
Diogenes Dev & Data Utilities MCP is listed in the public MCP registry as io.github.stand-out-of-my-sun/diogenes-dev-utilities-mcp. JSON healing, O(n) ReDoS defense, XML prompt compilation, and schema verification tools. This page covers its hosted endpoint (https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities).
Is the Diogenes Dev & Data Utilities MCP server safe to use?
Diogenes Dev & Data Utilities MCP scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Diogenes Dev & Data Utilities MCP server expose?
Diogenes Dev & Data Utilities MCP exposes 14 tools: heal_malformed_json, enforce_json_schema_types, extract_structured_json_entities, clean_tabular_dataset, synthesize_safe_regex, and 9 more. Their descriptions and schemas cost roughly 2,549 tokens of context every time the server is loaded.
Does the Diogenes Dev & Data Utilities MCP server require authentication?
No. We connected to Diogenes Dev & Data Utilities MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Diogenes Dev & Data Utilities MCP server still maintained?
Diogenes Dev & Data Utilities MCP is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.