Skip to content
Official MCP RegistryListed

IA-QA Data & Dev — 36 tools

Part ofIA-QA Data & Dev — 36 toolsMCP server

Dev utilities for agents: JSON/YAML/CSV, schema validation, encoding, text & time. Free, no key.

First seen 26 Oct 2026. Evidence as of 5 Nov 2026.

36
Tools
From an anonymous probe
1
Source listings
Each with its own history
46
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
base64_decodeDecode a Base64 string back to UTF-8 text. Use for inspecting Base64-encoded API responses, JWT payload claims, config file values, or attachment data.Read-only
base64_encodeEncode a UTF-8 string to Base64. Use when you need to embed binary data, multi-line text, or special characters safely inside JSON fields, HTTP headers, or data URIs.Read-only
case_convertConvert a string between naming conventions: camelCase, PascalCase, snake_case, kebab-case, UPPER_SNAKE_CASE, dot.case, Title Case. Essential for code generation and refactoring.Read-only
color_convertConvert a color between HEX, RGB, and HSL formats. Use when translating design tokens between CSS notations, verifying color accessibility, or normalizing color values from user input. Accepts #rrggbb, #rgb, rgb(r,g,b), or hsl(h,s%,l%).Read-only
count_code_linesCount lines of code: total, code lines, comment lines, blank lines, and comment density. Supports JS/TS, Python, Java/C/C++, Ruby, Go, Shell, HTML/XML, and CSS.Read-only
cron_parseParse a cron expression into a human-readable schedule description. Supports standard 5-field cron (minute hour day month weekday).Read-only
decode_jwtDecode a JWT (JSON Web Token) and return its header and payload without verifying the signature. Also reports whether the token is expired and the exact expiry date. Use to inspect claims (sub, iss, exp, roles) during debugging or when integrating with an auth provider.Read-only
diff_textCompute a unified line-by-line diff between two text strings (LCS algorithm). Returns added/removed/unchanged line counts and formatted diff hunks with configurable context lines (0–20). Use to compare versions of prompts, configs, code snippets, or any text where you need to see exactly what changed.Read-only
env_parseParse a .env file content into a JSON object. Handles quoted values (single and double), inline comments, export prefix, and escaped sequences (\n, \t inside double quotes). Returns all key-value pairs. Use in CI/CD pipelines, agent config loaders, or when processing dotenv files programmatically.Read-only
extract_json_pathExtract a value from a JSON string using dot-notation path (e.g., "user.address.city", "items.0.name", "meta.tags"). Supports array index access via numeric path segments.Read-only
find_toolSearch available MCP tools by keyword or category before calling them. Returns names, descriptions and, on request, inputSchemas. Queries are logged 90 days, screened for credentials and personal data. Categories: data, dev, encoding, eval, integrations, llm, meta, qa, rag, security, text, web.Read-only
flatten_jsonFlatten a nested JSON object to single-level dot-notation keys (e.g. {"a":{"b":1}} → {"a.b":1}), or unflatten dot-notation keys back to a nested object. Supports custom separators.Read-only
format_jsonValidate and pretty-print a string that is ALREADY valid JSON. Strict by design — it is a validity gate: valid JSON comes back formatted, anything else is rejected with the exact parse error. It never repairs, completes, or guesses. NOT for: plain text or prose (will fail), JSON embedded in markdown/prose (use extract_json_from_text first), JS objects (JSON.stringify them first), YAML (use yaml_to_json).Read-only
generate_slugConvert any string into a URL-friendly slug: lowercase, ASCII-normalized (é→e), special characters removed, spaces replaced with hyphens. Use for generating SEO-friendly URL paths, file names, or identifier keys from user-provided titles or labels.Read-only
generate_uuidGenerate one or more cryptographically random UUID v4 identifiers. Use this when you need unique IDs for test fixtures, database records, session tokens, or any scenario requiring a guaranteed-unique string. Returns up to 100 UUIDs in one call.Read-only
hash_textCompute a cryptographic hash of a text string. Use when you need to verify data integrity, generate content fingerprints, hash passwords (prefer SHA-256+), or produce a fixed-length digest of any input. Supports SHA-256 (default), SHA-512, SHA-1, and MD5.Read-only
json_diffCompute a deep structural diff between two JSON values. Returns added, removed, and changed keys with dot-notation paths. Like git diff but for JSON objects — perfect for API response regression testing. Arrays are not compared blindly by position: the same elements in a different order collapse to a single "reordered" change, and an array of records sharing a stable identity field (id, uuid, key, name…) is matched by that field, so paths read [id=42] and a moved record is not reported as N rewrites.Read-only
json_schema_generateInfer a JSON Schema (draft-07) from a sample JSON value. Detects types, required fields, array item shapes, nested objects, and common string formats (email, uri, date, date-time, uuid). Returns a ready-to-use schema compatible with json_schema_validate. Use when you have a sample API response or LLM output and want to auto-generate a validation schema for CI/CD testing.Read-only
json_schema_validateValidate a JSON value against a JSON Schema (draft-07 subset). Supports type, required, properties, items, enum, const, pattern, format (email/uri/date/date-time/uuid), minimum/maximum, minLength/maxLength, minItems/maxItems, uniqueItems, additionalProperties, anyOf, allOf, oneOf, not, and local $ref (#/definitions/…, #/$defs/…). A schema using a keyword outside that list (patternProperties, if/then, dependencies, a remote $ref…) is never reported valid: the keyword is named in `unevaluated_keywords`. Returns all validation errors with dot-notation paths.Read-only
json_to_csvConvert a JSON array of objects to CSV format. Automatically detects columns from all object keys. Handles quoting and escaping per RFC 4180.Read-only
json_to_yamlConvert a JSON object to clean, human-readable YAML. Handles nested objects, arrays, multiline strings, and special characters. No external dependencies.Read-only
lint_commit_messageValidate a git commit message against the Conventional Commits spec (feat, fix, docs, style, refactor, test, chore, ci, perf, build). Returns compliance score, breaking change detection, and actionable suggestions.Read-only
lorem_ipsumGenerate Lorem Ipsum placeholder text for UI mockups, design prototypes, or test data population. Configurable paragraphs (1–10), sentences per paragraph (1–20), and approximate words per sentence (3–30).Read-only
mock_from_schemaGenerate realistic mock data from a JSON Schema. Supports all common types (string, number, integer, boolean, array, object, null), format hints (email, date, date-time, uri, uuid), enum, const, and nested schemas. Perfect for testing MCP tools with realistic data.Read-only
number_base_convertConvert numbers between bases: decimal, binary, octal, hexadecimal, or any base 2–36. Auto-detects 0x, 0b, 0o prefixes.Read-only
openapi_validateValidate the structure of an OpenAPI 3.x specification (JSON or YAML). Checks required top-level fields (openapi, info.title, info.version, paths), validates each operation (responses, operationId uniqueness), detects undeclared $ref components, and flags missing 2xx responses. Returns a PASS/FAIL verdict, a 0–100 compliance score, and a list of errors and warnings with JSON-pointer locations. Use before publishing an API spec or generating SDK code.Read-only
parse_csvParse a CSV string into a JSON array of objects (or raw arrays). Full RFC 4180: quoted fields may contain the delimiter, embedded newlines (the Excel/Sheets multi-line cell), and doubled quotes. Custom delimiters supported. An unterminated quote is rejected with its position rather than parsed into corrupted rows. Use when processing spreadsheet exports, data imports, or structured text pipelines where the source is CSV. Supports up to 200 KB.Read-only
rate_toolGive honest usage feedback on an IA-QA MCP tool. Give a score (1-5) and a comment. Rate low (1-2) if the tool was wrong, irrelevant, or a poor fit; rate high (4-5) only if it genuinely solved your need. Maintainers read ratings, one vote per agent and tool a month: comments and per-tool scores are not published, only the overall average and vote count. Comments are screened: one carrying a credential is not stored, personal data becomes placeholders — describe what happened, not what a model should do. Skip routine successes: signal, not praise. Example: rate_tool({ tool_name: "format_json", score: 2, comment: "Tried to pretty-print a JSON5 file, it rejected trailing commas — not usable for my case." })Changes data
regex_testTest a regular expression pattern against an input string and return all matches with their index positions and named capture groups. Use for validating user inputs, extracting structured data from text, or debugging regex patterns. Supports flags g, i, m, s, u, y. The match runs in an isolated thread with a 500 ms budget: a pattern that blows up (catastrophic backtracking, e.g. "(a+)+$") comes back as redos_detected:true — a real ReDoS verdict on your pattern — instead of hanging.Read-only
text_statsCompute comprehensive statistics for any text: character count (with and without spaces), word count, line count, sentence count, paragraph count, and estimated reading time in minutes. Sentence counting is abbreviation-aware — titles (Mr., Dr.), acronyms (U.S., i.e., p.m.), initials, decimals, URLs and emails do not end a sentence, and a text with no terminal punctuation still counts as one. Use for validating form field lengths, evaluating LLM output verbosity, or content auditing.Read-only
timestamp_convertConvert between Unix timestamps (seconds or milliseconds) and ISO-8601 / UTC date strings. Auto-detects epoch vs. millisecond format. Omit input to get the current time. Returns iso, unix_s, unix_ms, utc, date, and time fields.Read-only
url_decodeDecode a percent-encoded URL string back to plain text. Use when parsing query parameters from raw URLs or when displaying encoded values to users.Read-only
url_encodePercent-encode a string for safe use in URLs. Call this before programmatically building query strings, path segments, or form-encoded bodies to prevent injection and malformed URLs.Read-only
validate_emailValidate an email address against RFC 5322 syntax before storing it, sending a transactional email, or adding it to a mailing list. Returns { valid, email } — use this to avoid bounces and malformed data.Read-only
xml_to_jsonConvert an XML string to a JSON object. Supports attributes, nested elements, arrays, CDATA, and namespaces. Options: parse numbers, parse booleans, ignore attributes.Read-only
yaml_to_jsonParse a YAML string and return the equivalent JSON value. The reverse of json_to_yaml. Supports nested objects, arrays, anchors, aliases, multi-document streams, and all scalar types. Use when processing config files, CI/CD pipeline definitions, or OpenAPI specs authored in YAML.Read-only

Change history

  1. find_tool: input schema changed
  2. find_tool: description changed (+"descriptions and, on request," +"dev," +"eval, integrations,")
  3. server instructions changed (+"These tools" +"operated" +"Report a verdict as a careful tester would: gate review means it could not decide, so say that and never round it to a pass; relay what a result says it did not prove, and explain why it matters to the person you work for.")
  4. rate_tool: description changed (+"Give" +"Maintainers" +"ratings,")
  5. find_tool: description changed (+"Queries" +"logged 90 days, screened for credentials and personal data." -"Call this when you")
  6. yaml_to_json: input schema changed
  7. xml_to_json: input schema changed
  8. validate_email: input schema changed
  9. url_encode: input schema changed
  10. url_decode: input schema changed
  11. timestamp_convert: input schema changed
  12. text_stats: input schema changed
  13. regex_test: input schema changed
  14. rate_tool: input schema changed
  15. parse_csv: input schema changed
  16. openapi_validate: input schema changed
  17. number_base_convert: input schema changed
  18. mock_from_schema: input schema changed
  19. lorem_ipsum: input schema changed
  20. lint_commit_message: input schema changed
  21. json_to_yaml: input schema changed
  22. json_to_csv: input schema changed
  23. json_schema_validate: input schema changed
  24. json_schema_generate: input schema changed (+samples)
  25. json_diff: input schema changed
  26. hash_text: input schema changed
  27. generate_uuid: input schema changed
  28. generate_slug: input schema changed
  29. format_json: input schema changed
  30. flatten_json: input schema changed
  31. find_tool: input schema changed
  32. extract_json_path: input schema changed
  33. env_parse: input schema changed
  34. diff_text: input schema changed
  35. decode_jwt: input schema changed
  36. cron_parse: input schema changed
  37. count_code_lines: input schema changed
  38. color_convert: input schema changed
  39. case_convert: input schema changed
  40. base64_encode: input schema changed
  41. base64_decode: input schema changed
  42. server instructions changed (+"diff) — the testing tools also return gate: pass | review | fail, the one field to branch a CI step on;" +"https://www.ia-qa.com/devtools/pal/tutorial, and to the step-by-step method at" -"diff);")
  43. rate_tool: description changed (+"read by the IA-QA maintainers and are not published, one vote per agent and tool a month. Comments are screened before storing: one carrying a credential is not stored and personal data is replaced by placeholders — describe what happened rather than what" +"model should do." -"aggregated on")
  44. json_schema_validate: description changed (+"(email/uri/date/date-time/uuid)," +"oneOf, not, and local $ref (#/definitions/…, #/$defs/…). A schema using a keyword outside that list (patternProperties, if/then, dependencies, a remote $ref…) is never reported valid: the keyword is named in `unevaluated_keywords`." -"(email/uri/date),")
  45. Repository changed (registry)
  46. Listed (registry)
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registryio.github.JcJamet/ia-qa-data26 Oct 20265 Nov 20262
IA-QA Data & Dev — 36 tools on Official MCP Registry | InvokeRank