Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Diogenes Dev & Data Utilities is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
JSON healing, O(n) ReDoS defense, XML prompt compilation, and schema verification tools.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http diogenes-dev-data-utilities-mcp https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilities
# 2 — ask your agent for something these tools do
# heal_malformed_json, enforce_json_schema_types, clean_tabular_dataset and 11 more
Diogenes Dev & Data Utilities costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SOAll 6 servers
stand-out-of-my-sun6 servers
4 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http diogenes-dev-data-utilities-mcp https://diogenes-micro-gateway.corinth.workers.dev/mcp/dev-utilitiesReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 K
| Parameter | Type | Required | Notes |
|---|---|---|---|
| malformed_json | string | yes | Raw broken, truncated, or markdown-wrapped JSON string to repair. |
| repair_mode | string | no | Bracket-closing and literal-normalization strategy; defaults to 'heuristic_fast' when omitted. |
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 c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| raw_output | string | yes | JSON string or object produced by an LLM to validate and coerce. |
| coercion_policy | string | no | Policy for handling extra undeclared properties; defaults to 'prune_undeclared_and_coerce' when omitted. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| data | string | yes | Raw newline-delimited text, CSV rows, or JSON array string to deduplicate and normalize. |
| normalization_mode | string | no | Deduplication key sensitivity; defaults to 'case_insensitive_trim' when omitted. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | Natural-language specification of the text pattern to match (e.g. 'RFC 5322 email addresses excluding plus-aliases'). |
| flavor | string | no | Target regular expression engine syntax; defaults to 'ecmascript_js' when omitted. |
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 r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | Raw task instructions, persona goal, and operational constraints to compile. |
| prompt_style | string | no | Structural formatting template; defaults to 'anthropic_xml_tags' when omitted. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| original_context | string | yes | Full pre-compaction conversation history or task log. |
| compacted_summary | string | yes | Candidate compacted summary to audit for dropped constraints or entities. |
| audit_focus | string | no | Entity class prioritized during retention scoring; defaults to 'constraints_paths_and_numbers' when omitted. |
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 an autonomous agent needs to plan 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, u
| Parameter | Type | Required | Notes |
|---|---|---|---|
| objective | string | yes | Natural-language description of the workflow goal to route across MCP tools. |
| budget_preference | string | no | Cost vs depth routing trade-off; defaults to 'lowest_sats_deterministic' when omitted. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deliverable | string | yes | JSON string or text deliverable submitted by the worker agent. |
| terms | string | no | Contract acceptance criteria that the deliverable must satisfy; defaults to 'Complete verified JSON deliverable' when omitted. |
| arbitration_standard | string | no | Strictness of contract verification; defaults to 'strict_all_criteria' when omitted. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | Unstructured document, email body, or webpage text to extract structured entities from. |
| extraction_target | string | no | Primary entity domain to extract; defaults to 'general_entities_and_metrics' when omitted. |
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-
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prompt | string | yes | Functional specification, input/output formats, and edge cases for the Python script. |
| dependency_policy | string | no | Allowed library dependencies in generated code; defaults to 'stdlib_only' when omitted. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | Full document text, RFC, or transcript to summarize. |
| summary_format | string | no | Output presentation structure; defaults to 'executive_bullets' when omitted. |
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 inste
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Company, protocol, market sector, or technical topic to brief. |
| focus | string | no | Analytical angle applied to the brief; defaults to 'technical_and_market_catalysts' when omitted. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | Agent workflow task to execute within the metered MPP session. |
| token_quota_tier | string | no | Allocated streaming token ceiling for the session; defaults to 'standard_4096' when omitted. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | Input text string or document chunk to convert into a normalized embedding vector. |
| encoding_format | string | no | Vector serialization format; defaults to 'float_array' when omitted. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Diogenes Dev & Data Utilities or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest8e0f5190b753a7a18a629ce1789ba6a6cd25a3292ccecd43adfac58239510803
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| heal_malformed_json | no tags | |
| enforce_json_schema_types | no tags | |
| clean_tabular_dataset | no tags | |
| synthesize_safe_regex | no tags | |
| compile_xml_agent_prompt | no tags | |
| verify_context_compaction_fidelity | no tags | |
| route_mcp_workflow_plan | no tags | |
| arbitrate_agent_deliverable_escrow | no tags | |
| extract_structured_json_entities | no tags | |
| synthesize_python_automation_code | no tags | |
| summarize_technical_document | no tags | |
| synthesize_web_intelligence_brief | untrusted-input | untrusted-input: keyword "web_search", declares openWorldHint: true (interacts with entities outside the server) |
| infer_mpp_streaming_session | no tags | |
| generate_x402_vector_embeddings | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest8e0f5190b753a7a1
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Diogenes Dev & Data Utilities can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.