# 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.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `diogenes-micro-gateway.corinth.workers.dev`: 62/100 (this document), [markdown](https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-dev-utilities-mcp/mcp-dev-utilities.md), [page](https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-dev-utilities-mcp/mcp-dev-utilities)

## Channel facts

- Endpoint: `https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 3 days we've observed: 10 tool removals, 0 breaking changes, 0 auth/transport breaks, 14 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http stand-out-of-my-sun-diogenes-dev-utilities-mcp 'https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities'
```

### Cursor

```json
{
  "mcpServers": {
    "stand-out-of-my-sun-diogenes-dev-utilities-mcp": {
      "url": "https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "stand-out-of-my-sun-diogenes-dev-utilities-mcp": {
      "type": "http",
      "url": "https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities"
    }
  }
}
```

### Codex

```toml
[mcp_servers.stand-out-of-my-sun-diogenes-dev-utilities-mcp]
url = "https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stand-out-of-my-sun-diogenes-dev-utilities-mcp": {
      "type": "remote",
      "url": "https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add stand-out-of-my-sun-diogenes-dev-utilities-mcp --url 'https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  stand-out-of-my-sun-diogenes-dev-utilities-mcp:
    url: "https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities"
```

### Netclaw

```json
{
  "McpServers": {
    "stand-out-of-my-sun-diogenes-dev-utilities-mcp": {
      "Transport": "http",
      "Url": "https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities"
    }
  }
}
```

### Vellum

```bash
assistant mcp add stand-out-of-my-sun-diogenes-dev-utilities-mcp -t streamable-http -u 'https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities'
```

### Other

```json
{
  "mcpServers": {
    "stand-out-of-my-sun-diogenes-dev-utilities-mcp": {
      "type": "http",
      "url": "https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 62, +4)

- [security regression] Stability: 0.03 → fail
- [security regression] A breaking change shipped without a version bump: still 2.5.0
- [security regression] Tool “agent_context_compaction_verifier” was removed
- [security regression] Tool “agent_hallucination_auditor” was removed
- [security regression] Tool “agent_mcp_router” was removed
- [security regression] Tool “agent_prompt_compiler” was removed
- [security regression] Tool “agent_schema_enforcer” was removed
- [security regression] Tool “clean_data” was removed
- [security regression] Tool “json_repair” was removed
- [security regression] Tool “mpp_agent_escrow_arbiter” was removed
- [security regression] Tool “regex_oracle” was removed
- [security regression] Tool “web_brief” was removed
- [functional regression] Schema quality: pass → fail
- [functional improvement] 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”

### 2026-10-21 (score 58, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-20 (score 58)

First indexed and scored.

## MCP tools (14)

### `heal_malformed_json` (~170 tokens)

Deterministic Malformed JSON Syntax & Truncation Healer

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.

Input parameters:

- `malformed_json` (string, required): 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.

Output parameters:

- `fixes_applied` (array): List of lexical repairs performed.
- `parsed_object` (object): Deserialized JSON object produced from the repaired string.
- `repaired_json` (string): Valid RFC 8259 JSON string after syntax healing.
- `status` (string): Repair outcome ('repaired' or 'valid_as_is').

### `enforce_json_schema_types` (~191 tokens)

Strict JSON Schema Validator, Type Coercer & Field Pruner

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.

Input parameters:

- `coercion_policy` (string): Policy for handling extra undeclared properties; defaults to 'prune_undeclared_and_coerce' when omitted.
- `raw_output` (string, required): JSON string or object produced by an LLM to validate and coerce.

Output parameters:

- `coercions_applied` (array): List of type conversions and default injections performed.
- `enforced_object` (object): Clean, schema-compliant JSON object.
- `unrecognized_fields_pruned` (array): Hallucinated property keys removed during enforcement.
- `valid` (boolean): True when the resulting enforced_object satisfies the schema.

### `extract_structured_json_entities` (~174 tokens)

Unstructured Text to Typed JSON Entity & Record Extractor

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.

Input parameters:

- `extraction_target` (string): Primary entity domain to extract; defaults to 'general_entities_and_metrics' when omitted.
- `text` (string, required): Unstructured document, email body, or webpage text to extract structured entities from.

Output parameters:

- `extracted_data` (object): Structured JSON object or array containing the extracted entities.
- `model` (string): Extraction model executed ('gemini-3.8-flash').
- `records_count` (integer): Number of distinct entity records extracted.
- `success` (boolean): True when entity extraction succeeded.

### `clean_tabular_dataset` (~175 tokens)

Tabular Dataset & Text Deduplication, Whitespace & Normalization Engine

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.

Input parameters:

- `data` (string, required): 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.

Output parameters:

- `cleaned_count` (integer): Unique non-empty record count after cleanup.
- `cleaned_data` (array): Deduplicated, whitespace-normalized records.
- `duplicates_removed` (integer): Number of duplicate records eliminated.
- `original_count` (integer): Line or record count prior to deduplication.

### `synthesize_safe_regex` (~181 tokens)

Linear-Time O(n) ReDoS-Safe Regular Expression Synthesizer & Tester

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.

Input parameters:

- `description` (string, required): 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.

Output parameters:

- `pattern` (string): Synthesized regular expression pattern string (without slash delimiters).
- `redos_safe` (boolean): True when static star-height analysis confirms zero exponential backtracking.
- `test_results` (array): Pass/fail verification results across positive and negative test cases.
- `time_complexity` (string): Worst-case matching complexity ('O(n)').

### `compile_xml_agent_prompt` (~180 tokens)

Production XML-Structured System Prompt & Guardrail Compiler

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.

Input parameters:

- `prompt_style` (string): Structural formatting template; defaults to 'anthropic_xml_tags' when omitted.
- `task` (string, required): Raw task instructions, persona goal, and operational constraints to compile.

Output parameters:

- `compiled_prompt` (string): Complete production-grade XML-structured system prompt.
- `estimated_tokens` (integer): Estimated BPE token length of the compiled prompt.
- `key_enhancements` (array): Specific guardrails and output contract rules injected.
- `optimization_score` (integer): Prompt clarity and constraint-completeness score from 0 to 100.

### `synthesize_python_automation_code` (~176 tokens)

Self-Contained Python Script, CLI & Parser Code Synthesizer

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.

Input parameters:

- `dependency_policy` (string): Allowed library dependencies in generated code; defaults to 'stdlib_only' when omitted.
- `prompt` (string, required): Functional specification, input/output formats, and edge cases for the Python script.

Output parameters:

- `model` (string): Code synthesis model executed ('gemini-4-argon').
- `output` (string): Complete Python 3 source code with inline verification assertions.
- `stdlib_only` (boolean): True if the generated script requires zero third-party pip packages.
- `success` (boolean): True when code synthesis succeeded.

### `summarize_technical_document` (~166 tokens)

High-Density Technical Document & RFC Executive Summarizer

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.

Input parameters:

- `summary_format` (string): Output presentation structure; defaults to 'executive_bullets' when omitted.
- `text` (string, required): Full document text, RFC, or transcript to summarize.

Output parameters:

- `compression_achieved` (boolean): True when output length is <25% of input length.
- `model` (string): Summarization model executed ('gemini-3.8-flash').
- `success` (boolean): True when summarization completed.
- `summary` (string): High-density technical summary text.

### `synthesize_web_intelligence_brief` (~183 tokens)

Real-Time Google Search Grounded JSON Market Intelligence Brief

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.

Input parameters:

- `focus` (string): Analytical angle applied to the brief; defaults to 'technical_and_market_catalysts' when omitted.
- `topic` (string, required): Company, protocol, market sector, or technical topic to brief.

Output parameters:

- `executive_summary` (string): Concise synthesis of current developments.
- `key_developments` (array): Dated factual developments grounded in search results.
- `sentiment` (string): Directional sentiment classification ('BULLISH', 'BEARISH', or 'NEUTRAL').
- `sources` (array): Verified web source titles and URLs.
- `topic` (string): Researched intelligence topic.

### `verify_context_compaction_fidelity` (~191 tokens)

Pre/Post Context Compaction Information Retention Verifier

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.

Input parameters:

- `audit_focus` (string): Entity class prioritized during retention scoring; defaults to 'constraints_paths_and_numbers' when omitted.
- `compacted_summary` (string, required): Candidate compacted summary to audit for dropped constraints or entities.
- `original_context` (string, required): Full pre-compaction conversation history or task log.

Output parameters:

- `missing_critical_entities` (array): Important entities or constraints dropped during compaction.
- `preserved_entities` (array): Critical constraints, paths, and numbers verified present in the summary.
- `retention_score` (number): Information preservation score from 0.0 to 1.0.
- `safe_to_resume` (boolean): True when retention_score >= 0.90 and zero critical constraints were lost.

### `route_mcp_workflow_plan` (~191 tokens)

Autonomous Goal-to-MCP Tool Sequence Router & Cost Planner

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.

Input parameters:

- `budget_preference` (string): Cost vs depth routing trade-off; defaults to 'lowest_sats_deterministic' when omitted.
- `objective` (string, required): Natural-language description of the workflow goal to route across MCP tools.

Output parameters:

- `deterministic_confidence` (number): Router confidence score from 0.80 to 1.0.
- `estimated_total_sats` (integer): Cumulative satoshi cost of the planned tool sequence.
- `objective` (string): Evaluated workflow objective.
- `recommended_sequence` (array): Ordered tool execution steps with tool name, endpoint, and cost_sats.

### `arbitrate_agent_deliverable_escrow` (~212 tokens)

Multi-Agent Task Deliverable & Contract Fulfillment Escrow Arbiter

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.

Input parameters:

- `arbitration_standard` (string): Strictness of contract verification; defaults to 'strict_all_criteria' when omitted.
- `deliverable` (string, required): 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.

Output parameters:

- `arbitration_notes` (string): Detailed justification citing satisfied or missing contract clauses.
- `contract_satisfied` (boolean): True when the deliverable fulfills all stated contract terms.
- `escrow_action` (string): Settlement command ('RELEASE_FUNDS_TO_WORKER_AGENT', 'REQUEST_REVISION', or 'REFUND_CLIENT').
- `quality_score` (integer): Deliverable quality score from 0 to 100.

### `infer_mpp_streaming_session` (~195 tokens)

Base EVM Machine Payments Protocol (MPP) Streaming Session Planner

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.

Input parameters:

- `task` (string, required): 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.

Output parameters:

- `plan` (array): Ordered execution steps generated for the task.
- `session_id` (string): Unique MPP streaming session identifier.
- `session_status` (string): Session lifecycle state ('ACTIVE_STREAMING').
- `streaming_tokens_allocated` (integer): Token budget reserved for the session.

### `generate_x402_vector_embeddings` (~164 tokens)

Solana x402 USDC-Settled Semantic Vector Embedding Generator

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.

Input parameters:

- `encoding_format` (string): Vector serialization format; defaults to 'float_array' when omitted.
- `text` (string, required): Input text string or document chunk to convert into a normalized embedding vector.

Output parameters:

- `dimensions` (integer): Number of float dimensions in the returned vector.
- `embedding` (array): Normalized floating-point vector array.
- `model` (string): Embedding model executed ('gemini-embedding-2').
- `normalized` (boolean): Always true; vectors are L2-normalized to unit length.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-dev-utilities-mcp/mcp-dev-utilities#diagnostics

## Score history

- 2026-10-23: 62
- 2026-10-22: 62
- 2026-10-21: 58
- 2026-10-20: 58

## Common questions

### 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.

## Links

- Remote endpoint: https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities
- Repository: https://github.com/stand-out-of-my-sun/diogenes-dev-utilities-mcp
- Website: https://diogenes-micro-gateway.corinth.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-dev-utilities-mcp/mcp-dev-utilities.xml
- Changelog JSON feed: https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-dev-utilities-mcp/mcp-dev-utilities.json
- HTML version of this page: https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-dev-utilities-mcp/mcp-dev-utilities