# IA-QA Data & Dev — 36 tools (remote · www.ia-qa.com)

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

- Trust score: 82/100 (high trust)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.ia-qa.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/jcjamet-ia-qa-data/mcp-data.md), [page](https://verifymcp.io/servers/jcjamet-ia-qa-data/mcp-data)

## Channel facts

- Endpoint: `https://www.ia-qa.com/mcp/data`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 83/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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 90/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4764 tokens (~132/item across 36 items; 36 tools + 0 resources), over budget; trim descriptions and params.
  - Tools include usage examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 36 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 37 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the IA-QA Data & Dev — 36 tools MCP server?

IA-QA Data & Dev — 36 tools is a hosted endpoint at https://www.ia-qa.com/mcp/data, 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 jcjamet-ia-qa-data 'https://www.ia-qa.com/mcp/data'
```

### Cursor

```json
{
  "mcpServers": {
    "jcjamet-ia-qa-data": {
      "url": "https://www.ia-qa.com/mcp/data"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jcjamet-ia-qa-data": {
      "type": "http",
      "url": "https://www.ia-qa.com/mcp/data"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jcjamet-ia-qa-data]
url = "https://www.ia-qa.com/mcp/data"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jcjamet-ia-qa-data": {
      "type": "remote",
      "url": "https://www.ia-qa.com/mcp/data",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jcjamet-ia-qa-data --url 'https://www.ia-qa.com/mcp/data' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jcjamet-ia-qa-data:
    url: "https://www.ia-qa.com/mcp/data"
```

### Netclaw

```json
{
  "McpServers": {
    "jcjamet-ia-qa-data": {
      "Transport": "http",
      "Url": "https://www.ia-qa.com/mcp/data"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jcjamet-ia-qa-data -t streamable-http -u 'https://www.ia-qa.com/mcp/data'
```

### Other

```json
{
  "mcpServers": {
    "jcjamet-ia-qa-data": {
      "type": "http",
      "url": "https://www.ia-qa.com/mcp/data"
    }
  }
}
```

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-11-05 (score 82, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28

### 2026-11-04 (score 82, +1)

- [security] Tool “find_tool” rewrote its description, which is the text the model reads
- [security] Tool “rate_tool” rewrote its description, which is the text the model reads

### 2026-11-02 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Schema quality: fail → pass
- [cosmetic] “json_schema_generate” added an optional parameter “samples”
- [cosmetic] “json_schema_generate” reworded the description of “required_all”

### 2026-10-30 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 76, 0)

- [security] Tool “json_schema_validate” rewrote its description, which is the text the model reads
- [security] Tool “rate_tool” rewrote its description, which is the text the model reads

### 2026-10-27 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 75)

First indexed and scored.

## MCP tools (36)

### `find_tool` (~194 tokens)

Search available MCP tools by keyword or category before calling them. Returns matching tool names, descriptions, and optionally their inputSchemas. Queries are logged 90 days, screened for credentials and personal data. Categories: data, encoding, text, llm, qa, rag, dev, security, web.

Input parameters:

- `category` (string): Optional: filter by category — data | encoding | text | llm | qa | rag | dev | security | web
- `max_results` (number): 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.
- `query` (string, required): Keyword(s) to search in tool name and description (e.g. "cors", "token", "vector", "json")
- `with_schema` (boolean): Set true to include inputSchema in results (default: false)

Output parameters:

- `category`
- `count` (number)
- `hint`
- `query`
- `score`
- `tool`
- `tools` (array)
- `total_matches` (number)
- `truncated` (boolean)

### `diff_text` (~116 tokens)

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.

Input parameters:

- `a` (string, required): Original (before) text
- `b` (string, required): Modified (after) text
- `context` (number): Context lines around each change (0–20, default: 3)

Output parameters:

- `added` (number)
- `diff` (string)
- `removed` (number)
- `unchanged` (number)

### `rate_tool` (~308 tokens)

Give 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." })

Input parameters:

- `comment` (string): 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…
- `score` (number, required): Rating from 1 (poor) to 5 (excellent)
- `tool_name` (string, required): Name of the MCP tool to rate (e.g. "format_json", "shield_analyze")

Output parameters:

- `comment`
- `message` (string)
- `ok` (boolean)
- `rated_at` (string)
- `score`
- `stored_chars` (number)
- `tool_name`
- `truncated` (boolean)

### `validate_email` (~63 tokens)

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.

Input parameters:

- `email` (string, required): Email address to validate

Output parameters:

- `email`
- `reason` (string)
- `valid` (boolean)

### `decode_jwt` (~80 tokens)

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.

Input parameters:

- `token` (string, required): The JWT string to decode (header.payload.signature)

Output parameters:

- `expired`
- `expiresAt`
- `header`
- `note` (string)
- `payload`

### `timestamp_convert` (~90 tokens)

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.

Input parameters:

- `input`: Unix timestamp (number, seconds or ms) or ISO date string. Omit to get the current time.

Output parameters:

- `date` (string)
- `iso` (string)
- `time` (string)
- `unix_ms` (number)
- `unix_s` (number)
- `utc` (string)

### `cron_parse` (~63 tokens)

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

Input parameters:

- `expression` (string, required): Cron expression (e.g., "0 9 * * 1-5", "*/15 * * * *")

Output parameters:

- `expression`
- `fields` (object)
- `human_readable` (string)

### `count_code_lines` (~109 tokens)

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.

Input parameters:

- `input` (string, required): Source code to analyze
- `language` (string): Language hint: "js", "ts", "py", "java", "c", "rb", "go", "sh", "html", "css" (auto-detect if omitted)

Output parameters:

- `blank_lines`
- `code_lines`
- `code_to_comment_ratio` (string)
- `comment_density`
- `comment_lines`
- `language`
- `total_lines`

### `lint_commit_message` (~91 tokens)

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.

Input parameters:

- `message` (string, required): Git commit message to validate
- `strict` (boolean): Enforce strict rules: max 72-char subject, imperative mood check (default: false)

Output parameters:

- `checks`
- `has_body` (boolean)
- `is_breaking_change` (boolean)
- `scope`
- `score` (number)
- `subject`
- `type`
- `valid` (boolean)

### `env_parse` (~93 tokens)

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

Input parameters:

- `input` (string, required): .env file content to parse (e.g. the output of `cat .env`)

Output parameters:

- `count` (number)
- `vars`

### `openapi_validate` (~139 tokens)

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 before publishing an API spec or generating SDK code.

Input parameters:

- `input` (string|object|array, required): The OpenAPI 3.x spec — a JSON string, a YAML string, or the already-parsed spec object.

Output parameters:

- `errors`
- `score` (number)
- `stats` (object)
- `verdict`
- `warnings`

### `generate_slug` (~84 tokens)

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.

Input parameters:

- `input` (string, required): String to slugify
- `separator` (string): Separator character (default: "-")

Output parameters:

- `slug`

### `format_json` (~148 tokens)

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

Input parameters:

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

Output parameters:

- `formatted` (string)
- `valid` (boolean)

### `parse_csv` (~142 tokens)

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 where the source is CSV. Supports up to 200 KB.

Input parameters:

- `delimiter` (string): Field delimiter character (default: ",")
- `header` (boolean): Treat the first row as headers (default: true)
- `input` (string, required): CSV content to parse

Output parameters:

- `columns` (number)
- `headers` (array)
- `row_count` (number)
- `rows` (array)

### `extract_json_path` (~101 tokens)

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.

Input parameters:

- `input` (string|object|array, required): The JSON to traverse — a JSON string, or the object/array itself.
- `path` (string, required): Dot-notation path, e.g. "user.address.city" or "items.0.name"

Output parameters:

- `path`
- `type`
- `value`

### `json_schema_validate` (~192 tokens)

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/then, dependencies, a remote $ref…) is never reported valid: the keyword is named in `unevaluated_keywords`. Returns all validation errors with dot-notation paths.

Input parameters:

- `schema` (string|object|array, required): The JSON Schema — a JSON string, or the schema object itself.
- `value` (string|object|array, required): The JSON value to validate — a JSON string, or the value itself.

Output parameters:

- `error_count` (number)
- `errors` (array)
- `valid` (boolean)

### `flatten_json` (~112 tokens)

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.

Input parameters:

- `input` (string|object|array, required): The JSON to flatten or unflatten — a JSON string, or the object itself.
- `mode` (string): "flatten" (default) or "unflatten"
- `separator` (string): Key separator (default: ".")

Output parameters:

- `key_count` (number)
- `max_depth` (array)
- `result`

### `xml_to_json` (~108 tokens)

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

Input parameters:

- `attr_prefix` (string): Prefix for attribute keys (default: "@_")
- `ignore_attrs` (boolean): Ignore XML attributes (default: false)
- `input` (string, required): XML string to convert
- `parse_values` (boolean): Auto-parse numbers and booleans (default: true)

Output parameters:

- `key_count` (number)
- `result`

### `mock_from_schema` (~136 tokens)

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.

Input parameters:

- `count` (number): Number of mock objects to generate (default: 1, max: 20)
- `schema` (string|object|array, required): The JSON Schema to generate from — a JSON string, or the schema object itself.
- `seed` (string): Optional seed string for deterministic output (uses first char codes)

Output parameters:

- `count` (number)
- `results`

### `json_to_csv` (~90 tokens)

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

Input parameters:

- `delimiter` (string): Column delimiter (default: ",")
- `headers` (boolean): Include header row (default: true)
- `input` (string|object|array, required): The array of objects to convert — a JSON string, or the array itself.

Output parameters:

- `column_names`
- `columns` (number)
- `csv` (string)
- `rows` (number)

### `json_diff` (~187 tokens)

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, name…) is matched by that field, so paths read [id=42] and a moved record is not reported as N rewrites.

Input parameters:

- `after` (string|object|array, required): The modified JSON (after) — a JSON string, or the value itself.
- `before` (string|object|array, required): The original JSON (before) — a JSON string, or the value itself.
- `max_depth` (number): Max nesting depth to recurse (default: 10)

Output parameters:

- `added` (boolean)
- `changes` (array)
- `identical` (boolean)
- `modified` (boolean)
- `removed` (boolean)
- `total_changes` (number)

### `json_to_yaml` (~80 tokens)

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

Input parameters:

- `indent` (number): Indentation size in spaces (default: 2)
- `input` (string|object|array, required): The JSON to convert to YAML — a JSON string, or the value itself.

Output parameters:

- `lines` (number)
- `yaml`

### `yaml_to_json` (~102 tokens)

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.

Input parameters:

- `input` (string, required): YAML string to parse
- `multi` (boolean): If true, parse all documents in a multi-document stream and return an array (default: false)

Output parameters:

- `count` (number)
- `documents`
- `json`

### `json_schema_generate` (~182 tokens)

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.

Input parameters:

- `input` (string|object|array, required): The sample JSON value to infer the schema from — a JSON string, or the value itself.
- `required_all` (boolean): Mark fields present in every observed object as required (default: true)
- `samples` (array|string): More samples of the same shape, merged with input: a field seen as null and as a date becomes ["string","null"]; one missing somewhere is not required.

Output parameters:

- `schema` (object)
- `warnings` (array)

### `text_stats` (~119 tokens)

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 for validating form field lengths, evaluating LLM output verbosity, or content auditing.

Input parameters:

- `input` (string, required): The text to analyse

Output parameters:

- `chars`
- `chars_no_space`
- `lines`
- `paragraphs`
- `reading_time_minutes`
- `sentences`
- `words`

### `regex_test` (~183 tokens)

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 back as redos_detected:true — a real ReDoS verdict on your pattern — instead of hanging.

Input parameters:

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

Output parameters:

- `elapsed_ms` (number)
- `flags`
- `match_count` (number)
- `matched`
- `matches`
- `note`
- `pattern`
- `redos_detected` (boolean)
- `verdict`

### `lorem_ipsum` (~120 tokens)

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

Input parameters:

- `paragraphs` (number): Number of paragraphs to generate (1–10, default: 1)
- `sentences_per_paragraph` (number): Sentences per paragraph (1–20, default: 5)
- `words_per_sentence` (number): Approximate words per sentence (3–30, default: 10)

Output parameters:

- `paragraph_count` (number)
- `paragraphs`

### `case_convert` (~106 tokens)

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.

Input parameters:

- `input` (string, required): String to convert (e.g., "myVariableName", "my-css-class")
- `to` (string, required): Target case: "camel", "pascal", "snake", "kebab", "upper_snake", "dot", "title"

Output parameters:

- `from_words`
- `result`
- `target_case`

### `generate_uuid` (~80 tokens)

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.

Input parameters:

- `count` (number): Number of UUIDs to generate (1–100, default: 1)

Output parameters:

- `count` (number)
- `uuids`

### `hash_text` (~102 tokens)

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.

Input parameters:

- `algorithm` (string): Hash algorithm: sha256 (default), sha512, sha1, md5
- `input` (string, required): Text to hash

Output parameters:

- `algorithm`
- `hash`
- `input_length` (number)

### `base64_encode` (~58 tokens)

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.

Input parameters:

- `input` (string, required): Text to encode

Output parameters:

- `encoded` (string)

### `base64_decode` (~55 tokens)

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.

Input parameters:

- `input` (string, required): Base64 string to decode

Output parameters:

- `decoded`

### `url_encode` (~76 tokens)

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.

Input parameters:

- `input` (string, required): String to URL-encode
- `mode` (string): "component" (default) or "full" for encodeURI behavior

Output parameters:

- `encoded`

### `url_decode` (~49 tokens)

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.

Input parameters:

- `input` (string, required): URL-encoded string to decode

Output parameters:

- `decoded`

### `color_convert` (~109 tokens)

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

Input parameters:

- `input` (string, required): Color value to convert, e.g. "#ff6b6b", "rgb(255,107,107)", "hsl(0,100%,71%)"

Output parameters:

- `b`
- `g`
- `hex`
- `hsl` (string)
- `input`
- `r`
- `rgb` (string)

### `number_base_convert` (~123 tokens)

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

Input parameters:

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

Output parameters:

- `binary` (string)
- `decimal`
- `from_base`
- `hexadecimal` (string)
- `octal` (string)
- `result` (string)
- `to_base`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jcjamet-ia-qa-data/mcp-data#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75

## Common questions

### What is the IA-QA Data & Dev — 36 tools MCP server?

IA-QA Data & Dev — 36 tools is an MCP server listed in the public MCP registry as io.github.JcJamet/ia-qa-data. Dev utilities for agents: JSON/YAML/CSV, schema validation, encoding, text & time. Free, no key. This page covers its hosted endpoint (https://www.ia-qa.com/mcp/data).

### Is the IA-QA Data & Dev — 36 tools MCP server safe to use?

IA-QA Data & Dev — 36 tools scores 82 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 IA-QA Data & Dev — 36 tools MCP server expose?

IA-QA Data & Dev — 36 tools exposes 36 tools: find_tool, diff_text, rate_tool, validate_email, decode_jwt, and 31 more. Their descriptions and schemas cost roughly 4,190 tokens of context every time the server is loaded.

### Does the IA-QA Data & Dev — 36 tools MCP server require authentication?

No. We connected to IA-QA Data & Dev — 36 tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the IA-QA Data & Dev — 36 tools MCP server still maintained?

IA-QA Data & Dev — 36 tools is still listed as active in the MCP registry. We last reached this channel on 5 November 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://www.ia-qa.com/mcp/data
- Repository: https://github.com/ia-qa-com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/jcjamet-ia-qa-data/mcp-data.xml
- Changelog JSON feed: https://verifymcp.io/servers/jcjamet-ia-qa-data/mcp-data.json
- HTML version of this page: https://verifymcp.io/servers/jcjamet-ia-qa-data/mcp-data