IA-QA — 130+ QA & Dev Tools for AI Agents
REMOTE · WWW.IA-QA.COM · SCANNED SEP 20
130+ QA & dev tools for AI agents: prompt injection, RAG testing, VLM eval, guardrails. Free.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 23161 tokens (~152/item across 152 items; 152 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "truncate_to_tokens" implies "truncate" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 153 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the IA-QA — 130+ QA & Dev Tools for AI Agents MCP server?
IA-QA — 130+ QA & Dev Tools for AI Agents is a hosted endpoint at https://www.ia-qa.com/mcp, 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.
remote · www.ia-qa.com
claude mcp add --transport http jcjamet-ia-qa-toolbox 'https://www.ia-qa.com/mcp'
{
"mcpServers": {
"jcjamet-ia-qa-toolbox": {
"url": "https://www.ia-qa.com/mcp"
}
}
} {
"servers": {
"jcjamet-ia-qa-toolbox": {
"type": "http",
"url": "https://www.ia-qa.com/mcp"
}
}
} [mcp_servers.jcjamet-ia-qa-toolbox] url = "https://www.ia-qa.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jcjamet-ia-qa-toolbox": {
"type": "remote",
"url": "https://www.ia-qa.com/mcp",
"enabled": true
}
}
} openclaw mcp add jcjamet-ia-qa-toolbox --url 'https://www.ia-qa.com/mcp' --transport streamable-http
mcp_servers:
jcjamet-ia-qa-toolbox:
url: "https://www.ia-qa.com/mcp" {
"McpServers": {
"jcjamet-ia-qa-toolbox": {
"Transport": "http",
"Url": "https://www.ia-qa.com/mcp"
}
}
} assistant mcp add jcjamet-ia-qa-toolbox -t streamable-http -u 'https://www.ia-qa.com/mcp'
{
"mcpServers": {
"jcjamet-ia-qa-toolbox": {
"type": "http",
"url": "https://www.ia-qa.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Sept 26 +1
- Stability: fail → pass ▲ security
- 14 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_testing_guidelines” rewrote its description, which is the text the model reads security
- Tool “response_quality_score” rewrote its description, which is the text the model reads security
- “get_testing_guidelines” reworded the description of “topic” cosmetic
- “response_quality_score” reworded the description of “expected_keywords” cosmetic
- “response_quality_score” reworded the description of “max_length” cosmetic
- 12 Sept 26 0
- “mcp_server_evaluate” reworded the description of “url” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 31 Aug 26 0
- New tool “sandbox_scenario” functional
- “generate_ci_workflow” added an optional parameter “app_base_url” cosmetic
- “generate_ci_workflow” added an optional parameter “app_start_command” cosmetic
- “generate_ci_workflow” reworded the description of “gate” cosmetic
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 89 to 93.
- 21 Aug 26 0
- Tool “fetch_veille_feed” rewrote its description, which is the text the model reads security
- Tool “generate_eval_yaml” rewrote its description, which is the text the model reads security
- Tool “generate_test_cases” rewrote its description, which is the text the model reads security
- Tool “rerank_evaluate” rewrote its description, which is the text the model reads security
- Tool “run_pr_gate_pipeline” rewrote its description, which is the text the model reads security
- Tool “shield_analyze” rewrote its description, which is the text the model reads security
- Tool “validate_agent_trajectory” rewrote its description, which is the text the model reads security
- “normalize_whitespace” added an optional parameter “max_blank_lines” cosmetic
- “rerank_evaluate” added an optional parameter “api_key” cosmetic
- “generate_test_cases” reworded the description of “feature” cosmetic
- “generate_test_cases” reworded the description of “inputs” cosmetic
- “llm_generate” reworded the description of “model” cosmetic
- “normalize_whitespace” reworded the description of “collapse_blanks” cosmetic
- “shield_analyze” reworded the description of “model” cosmetic
- “shield_analyze” reworded the description of “prompt” cosmetic
- “test_skill” reworded the description of “model” cosmetic
- “web_security_audit” reworded the description of “model” cosmetic
- “webhook_endpoint_create” reworded the description of “base_url” cosmetic
- 20 Aug 26 0
- Tool “cookie_security_audit” rewrote its description, which is the text the model reads security
- Tool “cors_test” rewrote its description, which is the text the model reads security
- Tool “hallucination_check” rewrote its description, which is the text the model reads security
- Tool “http_status_lookup” rewrote its description, which is the text the model reads security
- Tool “json_diff” rewrote its description, which is the text the model reads security
- Tool “parse_csv” rewrote its description, which is the text the model reads security
- Tool “prompt_injection_scan” rewrote its description, which is the text the model reads security
- Tool “regex_test” rewrote its description, which is the text the model reads security
- Tool “text_stats” rewrote its description, which is the text the model reads security
- Tool “toxicity_scan” rewrote its description, which is the text the model reads security
- New tool “metamorphic_check” functional
- “secret_scan” reworded the description of “types” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://www.ia-qa.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.ia-qa.com | CN=YR2,O=Let's Encrypt,C=US | 10 Aug 2026 | 8 Nov 2026 | RSA 2048 | SHA256-RSA | 6099d020336eba6c7e01bad927d7a8b7389 |
| SANs: www.ia-qa.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.ia-qa.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ia-qa.com. | present | 52852 | 8 | Verified |
| www.ia-qa.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self';script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com;style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;img-src 'self' data: blob: https:;font-src 'self' https://fonts.gstatic.com data:;connect-src 'self' https: wss: http://localhost:11434 data:;media-src 'self' blob:;object-src 'none';frame-ancestors 'self';base-uri 'self';form-action 'self';script-src-attr 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), display-capture=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.ia-qa.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.ia-qa.com/mcp | HTTPS enforced | 301 | https://www.ia-qa.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
token_budget_calculator ~183
Plan token allocation across system prompt, user input, context/RAG chunks, and expected output. Warns if budget exceeds model context window. Supports 25+ models.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Actual context text (will estimate tokens) |
| context_tokens | number | – | Token count for RAG context / documents |
| expected_output_tokens | number | – | Expected max output tokens |
| model | string | yes | Model name (e.g. gpt-4o, claude-3.5-sonnet, gemini-2.0-flash) |
| system_prompt | string | – | Actual system prompt text (will estimate tokens) |
| system_prompt_tokens | number | – | Token count for system prompt |
| user_input | string | – | Actual user input text (will estimate tokens) |
| user_input_tokens | number | – | Token count for user message |
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | object | – | – |
| context_window | – | – | – |
| fits_in_window | – | – | – |
| model | – | – | – |
| remaining_tokens | – | – | – |
| utilization_percent | – | – | – |
| warnings | – | – | – |
No examples provided.
toxicity_scan ~112
Scan text for toxic language, hate speech, bias/stereotype framing, violence, sexual and self-harm content. Lexical + structural pattern matching (identity term + predicate), not a semantic classifier — returns per-category risk plus the named rules that fired, so every finding can be checked. Useful for LLM safety guardrail testing and triage; signal-only, not a calibrated CI gate.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Categories to check (default: all) |
| text | string | yes | Text to scan |
| Name | Type | Req | Description |
|---|---|---|---|
| categories_checked | number | – | – |
| method | string | – | – |
| overall_risk | – | – | – |
| results | – | – | – |
| text_length | number | – | – |
No examples provided.
transform_json_array ~312
Transform a JSON array using common operations: pluck (extract specific fields), filter (by field value), sort_by (field), group_by (field), count_by (field), uniq_by (field). Useful for processing MCP tool results and LLM structured outputs.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | Field to operate on (for sort_by, group_by, count_by, uniq_by, filter) |
| fields | string | – | Comma-separated field list for "pluck" (e.g. "id,name,email") |
| filter_op | string | – | For "filter": "==" | "!=" | ">" | ">=" | "<" | "<=" | "contains" | "exists" | "!exists" |
| filter_value | string | – | For "filter": value to compare against |
| input | string|object|array | yes | The JSON containing an array (or an object with an array at `path`) — a JSON string, or the value itself. |
| n | number | – | For first_n / last_n: number of items |
| operation | string | yes | Operation: "pluck", "filter", "sort_by", "group_by", "count_by", "uniq_by", "reverse", "first_n", "last_n", "flatten" |
| path | string | – | Optional dot-notation path to the array within the JSON object (e.g. "data.items") |
| sort_order | string | – | For sort_by: "asc" (default) or "desc" |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
| field | – | – | – |
| fields | – | – | – |
| group_count | number | – | – |
| operation | string | – | – |
| order | – | – | – |
| removed | number | – | – |
| removed_duplicates | number | – | – |
| result | – | – | – |
| total | number | – | – |
| unique_values | number | – | – |
No examples provided.
truncate_to_tokens ~115
Truncate text to at most N tokens (cl100k_base: ~4 chars/token) to avoid exceeding an LLM context window. Optionally keeps the end of the text instead of the start (useful for keeping recent conversation history). Reports whether truncation occurred and the estimated token count.
| Name | Type | Req | Description |
|---|---|---|---|
| from_end | boolean | – | Keep the end of the text instead of the start (default: false) |
| input | string | yes | Text to truncate |
| max_tokens | number | yes | Maximum number of tokens to keep |
| Name | Type | Req | Description |
|---|---|---|---|
| original_tokens_estimate | – | – | – |
| text | – | – | – |
| tokens_estimate | – | – | – |
| truncated | boolean | – | – |
No examples provided.
unescape_html ~81
Convert HTML entities (&, <, >, ", ', and numeric &#NNN;) back to plain characters. Use when processing HTML-encoded text from APIs, email content, or legacy database fields before passing to an LLM or displaying to users.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | HTML-encoded string to unescape |
| Name | Type | Req | Description |
|---|---|---|---|
| unescaped | – | – | – |
No examples provided.
url_decode ~49
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | URL-encoded string to decode |
| Name | Type | Req | Description |
|---|---|---|---|
| decoded | – | – | – |
No examples provided.
url_encode ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | String to URL-encode |
| mode | string | – | "component" (default) or "full" for encodeURI behavior |
| Name | Type | Req | Description |
|---|---|---|---|
| encoded | – | – | – |
No examples provided.
validate_agent_trajectory ~284
Run declarative assertions on an agent trace (OpenAI tool-call messages, Anthropic tool_use/tool_result blocks, LangChain run trees, or plain text ReAct logs). No LLM call — deterministic. Assertion types: order (tool A before B), must_call, must_not_call, max_calls, min_calls, no_error, recovery (agent completes a successful step after its last error). A step counts as errored when the trace says so — is_error/isError, status/state in {error,failed,exception,…}, an error field, a JSON body with error/success:false — or when its text payload STARTS with an error marker (Error:, Traceback, TypeError:). Model prose is never scanned for keywords, and every errored step reports error_signal naming what flagged it. Returns per-assertion PASS/FAIL, parsed steps, warnings (a trace parsing to 0 steps is flagged — assertions passing on emptiness prove nothing), and an overall verdict. Use this to gate CI/CD on agent behavior correctness.
| Name | Type | Req | Description |
|---|---|---|---|
| assertions | array | yes | List of assertions to validate against the trace. |
| format | string | – | Trace format. auto (default) detects automatically. |
| trace | – | yes | Agent execution trace as JSON (OpenAI messages array, LangChain run tree) or plain text log (Thought/Action/Observation format). |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | – | – |
| steps | array | – | – |
| summary | object | – | – |
| verdict | string | – | – |
| warnings | array | – | – |
No examples provided.
validate_email ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| – | – | – | |
| reason | string | – | – |
| valid | boolean | – | – |
No examples provided.
validate_mcp_response ~225
Validate that an MCP tool response conforms to expected format, schema, and content rules. Use this to QA-test any MCP server tool. Supply the tool's actual JSON result and a set of checks to perform.
| Name | Type | Req | Description |
|---|---|---|---|
| actual_latency | number | – | Actual measured latency in ms (from the call) |
| expected_type | string | – | Expected top-level type: "object", "array", "string", "number" |
| forbidden_keys | string | – | Comma-separated list of keys that MUST NOT exist (e.g. "password, secret, token") |
| max_response_ms | number | – | Maximum acceptable latency in ms (will be compared if provided) |
| max_size_bytes | number | – | Maximum acceptable response size in bytes |
| min_items | number | – | If response is an array, minimum number of items expected |
| required_keys | string | – | Comma-separated list of keys that MUST exist in the response (dot-notation for nested: "data.id, data.name") |
| response | string | yes | The MCP tool result as a JSON string to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | – | – | – |
| failed | number | – | – |
| passed | number | – | – |
| total | number | – | – |
| verdict | string | – | – |
No examples provided.
validate_url ~47
Parse and validate a URL. Returns decomposed components: protocol, hostname, port, path, query parameters, hash, and origin.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | URL to validate and parse |
| Name | Type | Req | Description |
|---|---|---|---|
| full | – | – | – |
| hash | – | – | – |
| hostname | – | – | – |
| origin | – | – | – |
| pathname | – | – | – |
| port | – | – | – |
| protocol | – | – | – |
| query_params | – | – | – |
| search | – | – | – |
| valid | boolean | – | – |
No examples provided.
vector_quantize ~105
Simulate int8 or int4 quantization of float32 embedding vectors. Reduces storage by 4x (int8) or 8x (int4). Returns quantized values, scale factor, and precision loss (MSE). Useful for understanding vector DB compression trade-offs.
| Name | Type | Req | Description |
|---|---|---|---|
| bits | number | – | Quantization bits: 8 (int8, default) or 4 (int4) |
| vector | array | yes | Float32 vector to quantize |
| Name | Type | Req | Description |
|---|---|---|---|
| bits | – | – | – |
| compression_ratio | string | – | – |
| dimension | number | – | – |
| mse | number | – | – |
| offset | number | – | – |
| quantized | – | – | – |
| scale_factor | number | – | – |
| storage_bytes_float32 | – | – | – |
| storage_bytes_quantized | number | – | – |
No examples provided.
vector_similarity ~86
Compute similarity/distance between two float vectors: cosine similarity, dot product, Euclidean and Manhattan distance. Essential for vector DB relevance scoring, embedding evaluation, and nearest-neighbor testing.
| Name | Type | Req | Description |
|---|---|---|---|
| metric | string | – | Distance metric (default: all) |
| vector_a | array | yes | First vector as array of floats |
| vector_b | array | yes | Second vector as array of floats |
| Name | Type | Req | Description |
|---|---|---|---|
| cosine_distance | – | – | – |
| cosine_similarity | – | – | – |
| dimension | – | – | – |
| dot_product | – | – | – |
| euclidean_distance | – | – | – |
| interpretation | – | – | – |
| manhattan_distance | – | – | – |
| norm_a | – | – | – |
| norm_b | – | – | – |
No examples provided.
vector_stats ~121
Compute statistics for a float vector or matrix of vectors: mean, std, L2 norm, min, max, sparsity, top-K indices. Useful for debugging embedding quality and analyzing vector distributions in a vector DB.
| Name | Type | Req | Description |
|---|---|---|---|
| matrix | array | – | Matrix of vectors (overrides vector). Returns per-vector + matrix-level stats. Required unless `vector` is given. |
| top_k | number | – | Return indices of top K absolute values (default: 5) |
| vector | array | – | Single vector to analyze. Required unless `matrix` is given. |
| Name | Type | Req | Description |
|---|---|---|---|
| dimension | – | – | – |
| l2_norm | number | – | – |
| matrix_shape | array | – | – |
| matrix_stats | object | – | – |
| max | number | – | – |
| mean | number | – | – |
| min | number | – | – |
| per_vector | – | – | – |
| sparsity | number | – | – |
| std | number | – | – |
| top_k_indices | – | – | – |
No examples provided.
web_security_audit ~202
Run a comprehensive web security audit combining headers, SSL, CORS, and cookies checks — then use an LLM to produce a prioritised remediation plan. Orchestrates security_headers_check + ssl_certificate_check + cors_test + cookie_security_audit in parallel, merges all findings, then asks an AI model to: (1) rank vulnerabilities by real-world exploitability, (2) generate a remediation roadmap, (3) produce fix code snippets for the detected stack. Returns both raw audit data and the AI analysis. Use this as a one-click security posture assessment.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your Groq or HuggingFace API key. Required to enable AI analysis. |
| model | string | – | LLM model for AI analysis (default: "openai/gpt-oss-20b"). Set to "none" to skip AI analysis. |
| url | string | yes | Full URL to audit (e.g. https://example.com) |
| Name | Type | Req | Description |
|---|---|---|---|
| cookies | array | – | – |
| cookies_found | number | – | – |
| details | – | – | – |
| fix | – | – | – |
| grade | – | – | – |
| header | – | – | – |
| headers_checked | number | – | – |
| httpOnly | – | – | – |
| issues | – | – | – |
| key | – | – | – |
| message | string | – | – |
| missing | – | – | – |
| missing_count | number | – | – |
| name | – | – | – |
| origins_tested | number | – | – |
| overall_grade | – | – | – |
| risk_level | – | – | – |
| sameSite | – | – | – |
| score | – | – | – |
| secure | – | – | – |
| tests | – | – | – |
| total_findings | number | – | – |
| url | – | – | – |
| value | – | – | – |
| weak | – | – | – |
| weak_count | number | – | – |
| weight | – | – | – |
No examples provided.
webhook_endpoint_create ~105
Create a temporary webhook endpoint that captures incoming HTTP requests for one hour. Returns the webhook id, public URL, expiration timestamp, and current request count. Use together with webhook_endpoint_requests to inspect captured payloads.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | Optional public base URL. Default: https://www.ia-qa.com/mcp/webhook (the apex ia-qa.com answers 301 and a redirected POST loses its body, so an apex base_url is normalized to www) |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_at | string | – | – |
| id | – | – | – |
| request_count | number | – | – |
| retention_minutes | number | – | – |
| url | string | – | – |
No examples provided.
webhook_endpoint_requests ~78
Fetch the requests captured by a webhook created with webhook_endpoint_create. Returns the newest requests first with method, headers, query params, body payload, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Webhook id returned by webhook_endpoint_create |
| limit | number | – | Maximum number of requests to return (1-100, default: 20) |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_at | string | – | – |
| id | string | – | – |
| request_count | number | – | – |
| requests | array | – | – |
No examples provided.
word_frequency ~111
Analyze word frequency in text. Returns top N words with counts and percentages. Supports English stopword filtering. Useful for content analysis, keyword extraction, and LLM output analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Text to analyze |
| min_length | number | – | Minimum word length to include (default: 3) |
| remove_stopwords | boolean | – | Remove common English stopwords (default: true) |
| top_n | number | – | Return top N words (default: 20, max: 200) |
| Name | Type | Req | Description |
|---|---|---|---|
| stopwords_removed | – | – | – |
| top_words | array | – | – |
| total_words | – | – | – |
| unique_words | number | – | – |
No examples provided.
xml_to_json ~108
Convert an XML string to a JSON object. Supports attributes, nested elements, arrays, CDATA, and namespaces. Options: parse numbers, parse booleans, ignore attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| attr_prefix | string | – | Prefix for attribute keys (default: "@_") |
| ignore_attrs | boolean | – | Ignore XML attributes (default: false) |
| input | string | yes | XML string to convert |
| parse_values | boolean | – | Auto-parse numbers and booleans (default: true) |
| Name | Type | Req | Description |
|---|---|---|---|
| key_count | number | – | – |
| result | – | – | – |
No examples provided.
yaml_to_json ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | YAML string to parse |
| multi | boolean | – | If true, parse all documents in a multi-document stream and return an array (default: false) |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
| documents | – | – | – |
| json | – | – | – |
No examples provided.
What is the IA-QA — 130+ QA & Dev Tools for AI Agents MCP server?
IA-QA — 130+ QA & Dev Tools for AI Agents is an MCP server listed in the public MCP registry as io.github.JcJamet/ia-qa-toolbox. 130+ QA & dev tools for AI agents: prompt injection, RAG testing, VLM eval, guardrails. Free. This page covers its hosted endpoint (https://www.ia-qa.com/mcp).
Is the IA-QA — 130+ QA & Dev Tools for AI Agents MCP server safe to use?
IA-QA — 130+ QA & Dev Tools for AI Agents scores 87 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 — 130+ QA & Dev Tools for AI Agents MCP server expose?
IA-QA — 130+ QA & Dev Tools for AI Agents exposes 152 tools: format_json, generate_uuid, hash_text, count_tokens, base64_encode, and 147 more. Their descriptions and schemas cost roughly 22,875 tokens of context every time the server is loaded.
Does the IA-QA — 130+ QA & Dev Tools for AI Agents MCP server require authentication?
No. We connected to IA-QA — 130+ QA & Dev Tools for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the IA-QA — 130+ QA & Dev Tools for AI Agents MCP server still maintained?
IA-QA — 130+ QA & Dev Tools for AI Agents is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.