Home / MCP registry index / io.github.JcJamet/ia-qa-data
IA-QA Data & Dev — 36 tools
io.github.JcJamet/ia-qa-data in the official MCP registry.
Endpoint https://www.ia-qa.com/mcp/data. Source: github.com/ia-qa-com/mcp.
The registry describes it as: Dev utilities for agents: JSON/YAML/CSV, schema validation, encoding, text & time. Free, no key.
We read its 36 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
find_tool diff_text rate_tool validate_email decode_jwt timestamp_convert cron_parse count_code_lines lint_commit_message env_parse openapi_validate generate_slug format_json parse_csv extract_json_path json_schema_validate flatten_json xml_to_json mock_from_schema json_to_csv json_diff json_to_yaml yaml_to_json json_schema_generate text_stats regex_test lorem_ipsum case_convert generate_uuid hash_text base64_encode base64_decode url_encode url_decode color_convert number_base_convert
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-jcjamet-ia-qa-data)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.