Name: IA-QA Data & Dev — 36 tools
Author: JcJamet

IA-QA Data & Dev — 36 tools MCP

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

Tool-list grade A Remote · Streamable HTTP No auth needed 36 tools v1.0.1 MIT

No reviews yet by JcJametGitHub The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

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

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http ia-qa-data-dev-36-tools-mcp https://www.ia-qa.com/mcp/data

# 2 — ask your agent for something these tools do
#   find_tool, diff_text, rate_tool and 33 more

IA-QA Data & Dev — 36 tools costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

JcJamet4 servers

3 categories

All 4 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Search available MCP tools by keyword or category before calling them. Returns matching tool names, descriptions, and optionally their inputSchemas. Call this when you are unsure which tool to use or want to explore the catalogue. Categories: data, encoding, text, llm, qa, rag, dev, security, web.

Parameter	Type	Required	Notes
query	string	yes	Keyword(s) to search in tool name and description (e.g. "cors", "token", "vector", "json")
category	string	no	Optional: filter by category — data \| encoding \| text \| llm \| qa \| rag \| dev \| security \| web
with_schema	boolean	no	Set true to include inputSchema in results (default: false)
max_results	number	no	Maximum tools to return (default 10, max 50). Results are ranked by IDF-weighted relevance, so common words like "test" do not inflate the list.

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

Parameter	Type	Required	Notes
a	string	yes	Original (before) text
b	string	yes	Modified (after) text
context	number	no	Context lines around each change (0–20, default: 3)

Give honest usage feedback on an IA-QA MCP tool. Provide 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. Ratings are 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 d

Parameter	Type	Required	Notes
tool_name	string	yes	Name of the MCP tool to rate (e.g. "format_json", "shield_analyze")
score	number	yes	Rating from 1 (poor) to 5 (excellent)
comment	string	no	Strongly encouraged — explain what you were trying to do and whether the tool got you there. Be specific about what was missing, wrong, or a poor fit. This is the most valuable part of the rating. Up

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

Parameter	Type	Required	Notes
email	string	yes	Email address to validate

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

Parameter	Type	Required	Notes
token	string	yes	The JWT string to decode (header.payload.signature)

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

Parameter	Type	Required	Notes
input		no	Unix timestamp (number, seconds or ms) or ISO date string. Omit to get the current time.

Parse a cron expression into a human-readable schedule description. Supports standard 5-field cron (minute hour day month weekday).

Parameter	Type	Required	Notes
expression	string	yes	Cron expression (e.g., "0 9 * * 1-5", "/15 * * *")

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

Parameter	Type	Required	Notes
input	string	yes	Source code to analyze
language	string	no	Language hint: "js", "ts", "py", "java", "c", "rb", "go", "sh", "html", "css" (auto-detect if omitted)

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

Parameter	Type	Required	Notes
message	string	yes	Git commit message to validate
strict	boolean	no	Enforce strict rules: max 72-char subject, imperative mood check (default: false)

Parse a .env file content into a JSON object. Handles quoted values (single and double), inline comments, export prefix, and escaped sequences ( , inside double quotes). Returns all key-value pairs. Use in CI/CD pipelines, agent config loaders, or when processing dotenv files programmatically.

Parameter	Type	Required	Notes
input	string	yes	.env file content to parse (e.g. the output of cat .env)

Validate 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

Parameter	Type	Required	Notes
input	string/object/array	yes	The OpenAPI 3.x spec — a JSON string, a YAML string, or the already-parsed spec object.

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

Parameter	Type	Required	Notes
input	string	yes	String to slugify
separator	string	no	Separator character (default: "-")

Validate 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

Parameter	Type	Required	Notes
input	string	yes	A raw JSON string, e.g. '{"key":"value"}'. Must already parse as JSON — plain text or truncated JSON is rejected, not repaired.
indent	number	no	Indent size (default: 2)

Parse 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

Parameter	Type	Required	Notes
input	string	yes	CSV content to parse
delimiter	string	no	Field delimiter character (default: ",")
header	boolean	no	Treat the first row as headers (default: true)

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

Parameter	Type	Required	Notes
input	string/object/array	yes	The JSON to traverse — a JSON string, or the object/array itself.
path	string	yes	Dot-notation path, e.g. "user.address.city" or "items.0.name"

Validate 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/th

Parameter	Type	Required	Notes
value	string/object/array	yes	The JSON value to validate — a JSON string, or the value itself.
schema	string/object/array	yes	The JSON Schema — a JSON string, or the schema object itself.

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

Parameter	Type	Required	Notes
input	string/object/array	yes	The JSON to flatten or unflatten — a JSON string, or the object itself.
mode	string	no	"flatten" (default) or "unflatten"
separator	string	no	Key separator (default: ".")

Convert an XML string to a JSON object. Supports attributes, nested elements, arrays, CDATA, and namespaces. Options: parse numbers, parse booleans, ignore attributes.

Parameter	Type	Required	Notes
input	string	yes	XML string to convert
parse_values	boolean	no	Auto-parse numbers and booleans (default: true)
ignore_attrs	boolean	no	Ignore XML attributes (default: false)
attr_prefix	string	no	Prefix for attribute keys (default: "@_")

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

Parameter	Type	Required	Notes
schema	string/object/array	yes	The JSON Schema to generate from — a JSON string, or the schema object itself.
count	number	no	Number of mock objects to generate (default: 1, max: 20)
seed	string	no	Optional seed string for deterministic output (uses first char codes)

Convert a JSON array of objects to CSV format. Automatically detects columns from all object keys. Handles quoting and escaping per RFC 4180.

Parameter	Type	Required	Notes
input	string/object/array	yes	The array of objects to convert — a JSON string, or the array itself.
delimiter	string	no	Column delimiter (default: ",")
headers	boolean	no	Include header row (default: true)

Compute 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,

Parameter	Type	Required	Notes
before	string/object/array	yes	The original JSON (before) — a JSON string, or the value itself.
after	string/object/array	yes	The modified JSON (after) — a JSON string, or the value itself.
max_depth	number	no	Max nesting depth to recurse (default: 10)

Convert a JSON object to clean, human-readable YAML. Handles nested objects, arrays, multiline strings, and special characters. No external dependencies.

Parameter	Type	Required	Notes
input	string/object/array	yes	The JSON to convert to YAML — a JSON string, or the value itself.
indent	number	no	Indentation size in spaces (default: 2)

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

Parameter	Type	Required	Notes
input	string	yes	YAML string to parse
multi	boolean	no	If true, parse all documents in a multi-document stream and return an array (default: false)

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

Parameter	Type	Required	Notes
input	string/object/array	yes	The sample JSON value to infer the schema from — a JSON string, or the value itself.
required_all	boolean	no	Mark all detected object properties as required (default: true)

Compute 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

Parameter	Type	Required	Notes
input	string	yes	The text to analyse

Test 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 ba

Parameter	Type	Required	Notes
pattern	string	yes	Regular expression pattern (without delimiters)
input	string	yes	The string to test against (max 50 KB)
flags	string	no	Regex flags: g (global), i (case-insensitive), m (multiline), s (dotAll) — default: ""

Generate 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).

Parameter	Type	Required	Notes
paragraphs	number	no	Number of paragraphs to generate (1–10, default: 1)
sentences_per_paragraph	number	no	Sentences per paragraph (1–20, default: 5)
words_per_sentence	number	no	Approximate words per sentence (3–30, default: 10)

Convert a string between naming conventions: camelCase, PascalCase, snake_case, kebab-case, UPPER_SNAKE_CASE, dot.case, Title Case. Essential for code generation and refactoring.

Parameter	Type	Required	Notes
input	string	yes	String to convert (e.g., "myVariableName", "my-css-class")
to	string	yes	Target case: "camel", "pascal", "snake", "kebab", "upper_snake", "dot", "title"

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

Parameter	Type	Required	Notes
count	number	no	Number of UUIDs to generate (1–100, default: 1)

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

Parameter	Type	Required	Notes
input	string	yes	Text to hash
algorithm	string	no	Hash algorithm: sha256 (default), sha512, sha1, md5

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

Parameter	Type	Required	Notes
input	string	yes	Text to encode

Decode a Base64 string back to UTF-8 text. Use for inspecting Base64-encoded API responses, JWT payload claims, config file values, or attachment data.

Parameter	Type	Required	Notes
input	string	yes	Base64 string to decode

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

Parameter	Type	Required	Notes
input	string	yes	String to URL-encode
mode	string	no	"component" (default) or "full" for encodeURI behavior

Decode a percent-encoded URL string back to plain text. Use when parsing query parameters from raw URLs or when displaying encoded values to users.

Parameter	Type	Required	Notes
input	string	yes	URL-encoded string to decode

Convert 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%).

Parameter	Type	Required	Notes
input	string	yes	Color value to convert, e.g. "#ff6b6b", "rgb(255,107,107)", "hsl(0,100%,71%)"

Convert numbers between bases: decimal, binary, octal, hexadecimal, or any base 2–36. Auto-detects 0x, 0b, 0o prefixes.

Parameter	Type	Required	Notes
input	string	yes	Number to convert (e.g., "255", "0xFF", "0b1010", "0o77")
from_base	number	no	Source base 2–36 (auto-detects prefix if omitted)
to_base	number	no	Target base 2–36 (omit to get all common bases)

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

Nothing here is billable: mcprush charges nothing to install IA-QA Data & Dev — 36 tools or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.0.1 · 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 score93

Findings0 threat · 0 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digest67f488dd52ae9e1f7a945037789790e14fd6a60b0d90bbfe7bf5bc2fbc131fee

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
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. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
find_tool	no tags
diff_text	no tags
rate_tool	state-write	state-write: declares readOnlyHint: false
validate_email	no tags
decode_jwt	no tags
timestamp_convert	no tags
cron_parse	no tags
count_code_lines	no tags
lint_commit_message	no tags
env_parse	no tags
openapi_validate	no tags
generate_slug	no tags
format_json	no tags
parse_csv	no tags
extract_json_path	no tags
json_schema_validate	no tags
flatten_json	no tags
xml_to_json	no tags
mock_from_schema	no tags
json_to_csv	no tags
json_diff	no tags
json_to_yaml	no tags
yaml_to_json	no tags
json_schema_generate	no tags
text_stats	no tags
regex_test	no tags
lorem_ipsum	no tags
case_convert	no tags
generate_uuid	no tags
hash_text	no tags
base64_encode	no tags
base64_decode	no tags
url_encode	no tags
url_decode	no tags
color_convert	no tags
number_base_convert	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 digest67f488dd52ae9e1f

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.

Where are you running it?

Tool surface

Release history

IA-QA Data & Dev — 36 tools MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also