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 →
multimodal_eval_guide ~409
Unified tool for multimodal AI evaluation: set action=guide for reference thresholds/interpretation (CLIP, FID, VQA), or set action=clip_score / fid_score / vqa_accuracy / pipeline to compute real metrics via HuggingFace Inference API and VLM BYOK calls. One tool for both reference and computation.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | guide (default) = reference thresholds/interpretation. clip_score/fid_score/vqa_accuracy = compute that metric. pipeline = run all three. |
| api_key | string | – | [vqa_accuracy] Your API key for the provider (BYOK). |
| clip | object | – | [pipeline] {image_url, text} for CLIP. |
| fid | object | – | [pipeline] {real_images, generated_images} for FID. |
| generated_images | array | – | [fid_score] Array of generated image URLs. |
| image_base64 | string | – | [clip_score/vqa_accuracy] Base64-encoded image data. |
| image_mime_type | string | – | [clip_score/vqa_accuracy] MIME type for base64 image. |
| image_url | string | – | [clip_score/vqa_accuracy] Public URL of the image. |
| metric | string | – | [guide only] Metric to explain. |
| model | string | – | [vqa_accuracy] VLM model ID (default: gpt-4o). |
| real_images | array | – | [fid_score] Array of real image URLs. |
| score | number | – | [guide only] Optional score value to interpret. |
| system_prompt | string | – | [vqa_accuracy] Optional system prompt. |
| test_cases | array | – | [vqa_accuracy] Array of {question, accepted_answers} objects. |
| text | string | – | [clip_score only] Text description to compare against the image. |
| vqa | object | – | [pipeline] VQA config object (same inputs as vqa_accuracy). |
| Name | Type | Req | Description |
|---|---|---|---|
| best_practices | array | – | – |
| comparison_table | array | – | – |
| errors | – | – | – |
| metrics | – | – | – |
| results | – | – | – |
| score_interpretation | – | – | – |
| web_tool | string | – | – |
No examples provided.
needle_haystack_generate ~171
Generate a "needle in a haystack" test: embeds a target fact into a large block of filler text at a specified position. Use this to test LLM context window retrieval accuracy. Returns the full haystack, the question to ask, and metadata. No API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| needle | string | yes | The fact to hide (e.g. "The secret code is ALPHA-42") |
| position | string | – | Where to insert the needle: "start", "middle", "end", "random" (default: "middle") |
| question | string | yes | The question to ask the LLM (e.g. "What is the secret code?") |
| tokens | integer | – | Target haystack size in tokens (default: 5000, max: 100000) |
| Name | Type | Req | Description |
|---|---|---|---|
| estimated_tokens | – | – | – |
| haystack | – | – | – |
| insert_block | – | – | – |
| needle | – | – | – |
| position | – | – | – |
| question | – | – | – |
| total_blocks | number | – | – |
No examples provided.
normalize_vector ~79
L2-normalize a float vector (produce a unit vector with norm=1). Required by many vector DBs (Pinecone, Qdrant cosine). Supports batch normalization of up to 1000 vectors.
| Name | Type | Req | Description |
|---|---|---|---|
| batch | array | – | Batch of vectors to normalize (overrides vector) |
| vector | array | – | Single vector to normalize |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
| dimension | number | – | – |
| index | – | – | – |
| mode | string | – | – |
| norm | number | – | – |
| norm_after | number | – | – |
| norm_before | number | – | – |
| normalized | – | – | – |
| results | – | – | – |
| vector | – | – | – |
No examples provided.
normalize_whitespace ~181
Normalize whitespace: trim trailing spaces, collapse blank lines, normalize line endings (LF/CRLF), convert tabs to spaces. Useful for cleaning code, configs, and text before processing.
| Name | Type | Req | Description |
|---|---|---|---|
| collapse_blanks | boolean | – | Collapse runs of blank lines down to max_blank_lines (default: true) |
| input | string | yes | Text to normalize |
| line_ending | string | – | "lf" (default), "crlf", or "cr" |
| max_blank_lines | number | – | Blank lines to keep when collapsing, 0-10 (default: 2) |
| tab_to_spaces | number | – | Convert tabs to N spaces (omit to keep tabs) |
| trim_file | boolean | – | Trim leading/trailing blank lines (default: true) |
| trim_lines | boolean | – | Trim trailing whitespace from each line (default: true) |
| Name | Type | Req | Description |
|---|---|---|---|
| line_ending | – | – | – |
| normalized_length | number | – | – |
| original_length | number | – | – |
| result | – | – | – |
No examples provided.
number_base_convert ~123
Convert numbers between bases: decimal, binary, octal, hexadecimal, or any base 2–36. Auto-detects 0x, 0b, 0o prefixes.
| Name | Type | Req | Description |
|---|---|---|---|
| from_base | number | – | Source base 2–36 (auto-detects prefix if omitted) |
| input | string | yes | Number to convert (e.g., "255", "0xFF", "0b1010", "0o77") |
| to_base | number | – | Target base 2–36 (omit to get all common bases) |
| Name | Type | Req | Description |
|---|---|---|---|
| binary | string | – | – |
| decimal | – | – | – |
| from_base | – | – | – |
| hexadecimal | string | – | – |
| octal | string | – | – |
| result | string | – | – |
| to_base | – | – | – |
No examples provided.
openapi_validate ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string|object|array | yes | The OpenAPI 3.x spec — a JSON string, a YAML string, or the already-parsed spec object. |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | – | – | – |
| score | number | – | – |
| stats | object | – | – |
| verdict | – | – | – |
| warnings | – | – | – |
No examples provided.
optimize_prompt_tokens ~74
Compress an LLM prompt by removing filler words, verbose phrases, duplicate sentences, and unnecessary whitespace. Returns optimized text with token savings breakdown. 100% deterministic, no API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| options | object | – | Toggle optimization steps (all true by default) |
| text | string | yes | The prompt text to optimize |
| Name | Type | Req | Description |
|---|---|---|---|
| optimized | – | – | – |
| percent_saved | string | – | – |
| steps | – | – | – |
| tokens_after | – | – | – |
| tokens_before | – | – | – |
| tokens_saved | – | – | – |
No examples provided.
parse_csv ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| delimiter | string | – | Field delimiter character (default: ",") |
| header | boolean | – | Treat the first row as headers (default: true) |
| input | string | yes | CSV content to parse |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | number | – | – |
| headers | array | – | – |
| row_count | number | – | – |
| rows | array | – | – |
No examples provided.
parse_http_headers ~88
Parse a raw HTTP headers block into a structured JSON object. Detects multi-value headers, masks Authorization values, and optionally audits for missing security headers (HSTS, CSP, X-Frame-Options, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| analyze_security | boolean | – | Audit for missing security headers (default: true) |
| headers | string | yes | Raw HTTP headers (one "Name: Value" per line) |
| Name | Type | Req | Description |
|---|---|---|---|
| header_count | number | – | – |
| parsed | object | – | – |
| security | object | – | – |
No examples provided.
post_jira_comment ~141
Post the output of jira_to_test_suite as a formatted comment on the source Jira ticket. Converts Gherkin, E2E steps, API tests, and ambiguities into Atlassian Document Format (ADF). STATEFUL — creates a comment on the issue.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_key | string | yes | Jira issue key, e.g. "PROJ-123" |
| jira_base_url | string | yes | Atlassian base URL |
| jira_email | string | yes | Atlassian account email |
| jira_token | string | yes | Atlassian API token |
| test_suite | object | yes | The test_suite object from jira_to_test_suite result |
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | – | – |
| comment_url | string | – | – |
| success | boolean | – | – |
No examples provided.
pr_gatekeeper ~162
Compound quality gate for pull requests. Runs three sequential checks: (1) secret detection — scans diff for API keys, tokens, passwords matching 16 regex patterns; (2) bug analysis — heuristic scan for eval(), innerHTML, empty catch, console.log, TODO/FIXME; (3) commit message linting against Conventional Commits spec. Returns gate verdict (PASS/WARN/BLOCK), blockers, and actionable warnings. Use before merging any code change.
| Name | Type | Req | Description |
|---|---|---|---|
| commit_message | string | yes | The commit message to lint (e.g. "feat(auth): add OAuth2 login") |
| context | string | – | Optional: PR title or description for richer bug analysis |
| diff | string | yes | Unified git diff (output of `git diff HEAD`) |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | object | – | – |
| flags | array | – | – |
| score | number | – | – |
| verdict | string | – | – |
No examples provided.
prompt_injection_scan ~206
Scan user input or prompts for common prompt injection patterns. Detects system prompt overrides, jailbreak attempts, role manipulation, encoding tricks, delimiter attacks (chat-template tags `<|im_start|>`/`[INST]`/`<<SYS>>` AND fake role headers imitating markdown or chat separators: "### System:", "--- SYSTEM ---", "---BEGIN SYSTEM OVERRIDE---", "--- SYSTEM:"), template/interpolation injection ({{...}}, ${...}), and context-exfiltration attempts ("repeat everything above"). A match inside quoted or fenced text (documentation citing a payload) is reported one severity level lower and marked `quoted` — never suppressed, since an LLM reading the document as data can still follow a quoted instruction. A quote preceded by a live imperative ("output the following: ...") keeps its full severity.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The user input or prompt to scan for injection patterns |
| sensitivity | string | – | Detection sensitivity (default: medium) |
| Name | Type | Req | Description |
|---|---|---|---|
| detections | – | – | – |
| detections_count | number | – | – |
| injection_detected | boolean | – | – |
| input_length | number | – | – |
| notes | – | – | – |
| quoted_detections | number | – | – |
| risk_level | – | – | – |
| sensitivity | – | – | – |
No examples provided.
prompt_template_fill ~103
Fill a prompt template with variables. Supports {{variable}} syntax and {{#if key}}...{{/if}} conditional blocks. Returns the filled prompt and lists unfilled variables.
| Name | Type | Req | Description |
|---|---|---|---|
| strict | boolean | – | Throw error if any variable is not provided (default: false) |
| template | string | yes | Prompt template with {{variable}} placeholders |
| variables | object | – | Key-value pairs to fill (e.g. {"name":"Alice","role":"engineer"}) |
| Name | Type | Req | Description |
|---|---|---|---|
| filled_variables | – | – | – |
| result | – | – | – |
| total_vars | – | – | – |
| unfilled_variables | – | – | – |
No examples provided.
prompt_test_suite ~201
Define a test suite for a prompt: provide the system prompt, user prompt, and expected output criteria. Returns a test plan with scored rubric — use this as input for manual or automated LLM evaluation.
| Name | Type | Req | Description |
|---|---|---|---|
| adversarial_prompts | boolean | – | Auto-generate adversarial test variants (jailbreak, injection, edge cases) |
| check_safety | boolean | – | Include safety/PII checks in the rubric |
| expected_behavior | string | – | Description of what the LLM should do (free text) |
| expected_format | string | – | Expected output format |
| max_tokens | number | – | Max token budget for the test |
| must_include | string | – | Required content (comma-separated) |
| must_not_include | string | – | Forbidden content (comma-separated) |
| system_prompt | string | yes | The system prompt under test |
| temperature | number | – | Temperature to use |
| user_prompt | string | yes | The user prompt to send |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | – |
| instructions | string | – | – |
| rubric | – | – | – |
| test_suite_name | string | – | – |
| total_tests | number | – | – |
No examples provided.
rag_relevance_rank ~81
Rank an array of text chunks by relevance to a query using TF-IDF scoring. Simulates retrieval ranking for RAG testing without needing embeddings or an API.
| Name | Type | Req | Description |
|---|---|---|---|
| chunks | array | yes | Array of text chunks to rank |
| query | string | yes | The user query |
| top_k | number | – | Return top K results (default: all) |
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_preview | – | – | – |
| index | – | – | – |
| keyword_overlap | – | – | – |
| query | – | – | – |
| rank | number | – | – |
| results | – | – | – |
| returned | number | – | – |
| score | string | – | – |
| total_chunks | number | – | – |
No examples provided.
rate_tool ~268
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 aggregated on a public dashboard at /devtools/mcp-ratings. Skip rating routine successes — we want 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." })
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Rating from 1 (poor) to 5 (excellent) |
| tool_name | string | yes | Name of the MCP tool to rate (e.g. "format_json", "shield_analyze") |
| Name | Type | Req | Description |
|---|---|---|---|
| comment | – | – | – |
| message | string | – | – |
| ok | boolean | – | – |
| rated_at | string | – | – |
| score | – | – | – |
| stored_chars | number | – | – |
| tool_name | – | – | – |
| truncated | boolean | – | – |
No examples provided.
redact_pii ~139
Automatically detect and redact Personally Identifiable Information (PII) from text. Replaces emails, phone numbers, SSNs, credit cards, IP addresses, and JWT tokens with [REDACTED_TYPE] placeholders. Safe to use before logging or sending to an LLM.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Text to redact PII from |
| marker | string | – | Custom replacement marker (default: "REDACTED"). Result: [REDACTED_EMAIL] |
| types | string | – | Comma-separated types to redact (default: all). Options: email, phone, ssn, credit_card, ip_address, jwt |
| Name | Type | Req | Description |
|---|---|---|---|
| clean | boolean | – | – |
| pii_found | – | – | – |
| redacted_text | – | – | – |
| replacements | – | – | – |
| total_redactions | – | – | – |
No examples provided.
regex_test ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| flags | string | – | Regex flags: g (global), i (case-insensitive), m (multiline), s (dotAll) — default: "" |
| input | string | yes | The string to test against (max 50 KB) |
| pattern | string | yes | Regular expression pattern (without delimiters) |
| Name | Type | Req | Description |
|---|---|---|---|
| elapsed_ms | number | – | – |
| flags | – | – | – |
| match_count | number | – | – |
| matched | – | – | – |
| matches | – | – | – |
| note | – | – | – |
| pattern | – | – | – |
| redos_detected | boolean | – | – |
| verdict | – | – | – |
No examples provided.
rerank_evaluate ~325
Evaluate RAG retrieval quality: rank passages against a query and compute Precision@k / Recall@k plus a PASS/FAIL CI verdict from ground-truth relevance labels. Three modes, all keyless except the last. (1) BYO scores — give each passage the `score` your own reranker produced (Cohere, Jina, a self-hosted NIM, a cross-encoder): deterministic, offline, and it evaluates YOUR reranker rather than someone else's. This is the mode to gate CI on. (2) Default, no scores and no key — ranks with local BM25, a lexical keyword baseline: it answers "does a keyword floor already surface my relevant passages?", never "is my neural reranker good". (3) Live NVIDIA reranker — supply `api_key` for an NVIDIA account that still has reranking entitlement; NVIDIA retired its hosted reranking endpoints on 2026-05-18, so this one is for accounts that were grandfathered in.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your NVIDIA API key (BYOK), used only when no passage carries a score. Transits RAM for the single call, never stored. |
| passages | array | yes | Array of passage objects to rank (min 2, max 20) |
| query | string | yes | The search query or question to rank against |
| threshold | number | – | Minimum Precision@k to PASS (0-1, default 0.5) |
| top_k | integer | – | k for Precision@k evaluation (default 3) |
| Name | Type | Req | Description |
|---|---|---|---|
| has_ground_truth | boolean | – | – |
| k | number | – | – |
| latency_ms | number | – | – |
| mode | string | – | – |
| model | string | – | – |
| precision_at_k | number | – | – |
| ranked | array | – | – |
| recall_at_k | number | – | – |
| threshold | number | – | – |
| total_passages | number | – | – |
| verdict | string | – | – |
No examples provided.
response_quality_score ~176
Score an LLM response against the criteria you pass: coverage of expected_keywords and compliance with max_length. Returns a 0-100 score over the criteria actually measured — or total_score null with the reason when none is given, because relevance and correctness cannot be read off word overlap (a correct one-word answer shares no words with its question). For meaning against a reference answer, use run_semantic_tests. Also returns unscored signals: question-term overlap, average sentence length, markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_keywords | array | – | Keywords a correct answer must contain (case-insensitive). Scored as coverage. |
| max_length | number | – | Maximum character length. Scored as a proportional penalty beyond it. |
| question | string | yes | The original question/prompt |
| response | string | yes | The LLM response to score |
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | object | – | – |
| grade | – | – | – |
| max_score | number | – | – |
| not_measured | array | – | – |
| reason | string | – | – |
| signals | object | – | – |
| stats | object | – | – |
| total_score | – | – | – |
No examples provided.
run_eval_contract ~202
Parse a .ia-eval.yaml LLM test suite, call the specified LLM model for each scenario, run all configured scorers, and return a structured JSON report with per-scenario Pass/Fail verdicts and a Markdown summary. Use list_local_tests to discover available test files.
| Name | Type | Req | Description |
|---|---|---|---|
| api_keys | object | – | API keys to use for LLM generation (all optional — falls back to server env vars) |
| contract_path | string | – | Absolute or relative path to a .ia-eval.yaml file (required unless inline_contract is provided) |
| inline_contract | object | – | Raw contract object (alternative to contract_path). Must contain top-level "metadata" ({name, version, model?, provider?}), "expectations" ({min_score?}), and "scenarios" ([{id, input, ground_truth?}… |
| overrides | object | – | Override contract defaults |
| Name | Type | Req | Description |
|---|---|---|---|
| contract_path | – | – | – |
| metadata | object | – | – |
| scenario_results | – | – | – |
| summary | object | – | – |
| warnings | – | – | – |
No examples provided.
run_pr_gate_pipeline ~183
Review triage for a pull request. Takes a unified git diff (`git diff HEAD`) and returns: diff-lint findings with the lines that produced them, regression impact areas, a risk score 0–100 with the factors that built it (churn, files touched, sensitive paths, whether any test file changed, lint severities, impacted risk areas), generated test cases, and a PASS / CONDITIONAL / BLOCK recommendation. Advisory: the score measures properties of the diff, not the correctness of the change — it does not read the code semantically and does not replace a reviewer or a static analyser. See notAnalysed in the response.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional PR title or description for richer analysis |
| git_diff | string | yes | Unified git diff (output of `git diff HEAD` or copied from GitHub diff view) |
| Name | Type | Req | Description |
|---|---|---|---|
| bugsFound | number | – | – |
| changedFiles | – | – | – |
| critical | – | – | – |
| disclaimer | string | – | – |
| high | – | – | – |
| impactAreas | array | – | – |
| inputFormat | string | – | – |
| mergeRecommendation | – | – | – |
| notAnalysed | array | – | – |
| riskFactors | array | – | – |
| riskLevel | – | – | – |
| riskScore | – | – | – |
| severityLevel | – | – | – |
| sla | – | – | – |
| testCasesGenerated | – | – | – |
| topBugs | array | – | – |
No examples provided.
run_semantic_tests ~216
Semantic assertion primitive: compare actual vs expected text pairs using cosine similarity + ROUGE-L. Two modes: tfidf (default, free, no API key) or embeddings (OpenAI text-embedding-3-small, BYOK, true semantic similarity). Returns per-case PASS/FAIL verdicts and an overall verdict. CI-ready: pipe the JSON verdict field to gate a build.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | OpenAI API key — required only when mode is embeddings. |
| cases | array | yes | Array of (actual, expected) pairs to evaluate. |
| mode | string | – | tfidf (default): fast, free, lexical. embeddings: OpenAI text-embedding-3-small, true semantic similarity, requires api_key. |
| require_all | boolean | – | If true (default), all cases must pass for overall PASS. If false, at least one case passing returns PASS. |
| thresholds | object | – | Pass/fail thresholds (defaults: cosine 0.75, rouge_l 0.5). |
| Name | Type | Req | Description |
|---|---|---|---|
| failed | number | – | – |
| mode | string | – | – |
| passed | number | – | – |
| results | array | – | – |
| total | number | – | – |
| verdict | string | – | – |
No examples provided.
run_vlm_test_suite ~301
Run a test suite against a Vision-Language Model (VLM) — send an image (URL or base64) + N test cases (each with a question + assertion) to GPT-4o, Claude 3.5, or Gemini. Returns per-case PASS/FAIL verdicts, a pass rate, an overall PASS/WARNING/FAIL verdict (customizable threshold), and latency stats. Assertion types: contains, not_contains, json_format, min_length, max_length, semantic_contains (TF-IDF cosine similarity ≥ 0.4). BYOK: requires your own API key for the target provider.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | API key for the model provider (OpenAI sk-, Anthropic sk-ant-, or Google AIzaSy...). |
| image_base64 | string | – | Base64-encoded image data (required unless image_url is provided). |
| image_mime_type | string | – | MIME type of the image if using image_base64 (default: image/jpeg). |
| image_url | string | – | Public URL of the image to evaluate (required unless image_base64 is provided). |
| model | string | yes | VLM model to use. |
| system_prompt | string | – | Optional system prompt sent to the VLM. |
| test_cases | array | yes | Array of test cases to run. |
| threshold | number | – | Pass rate threshold for overall verdict (default: 80, 0–100). |
| Name | Type | Req | Description |
|---|---|---|---|
| failed | number | – | – |
| model | string | – | – |
| passed | number | – | – |
| results | array | – | – |
| total | number | – | – |
| verdict | string | – | – |
No examples provided.
run_vlm_test_suite_batch ~285
Compare multiple VLMs on the same test suite in parallel — send an image (URL or base64) + N test cases to all models simultaneously. Returns per-model PASS/FAIL verdicts, pass rates, latency stats, and a comparison table. Assertion types: contains, not_contains, json_format, min_length, max_length, semantic_contains. BYOK: requires API keys for each provider.
| Name | Type | Req | Description |
|---|---|---|---|
| api_keys | object | yes | Map of model ID → API key. Example: { "gpt-4o": "sk-...", "claude-3-5-sonnet-20241022": "sk-ant-..." } |
| image_base64 | string | – | Base64-encoded image data (required unless image_url is provided). |
| image_mime_type | string | – | MIME type of the image if using image_base64 (default: image/jpeg). |
| image_url | string | – | Public URL of the image to evaluate (required unless image_base64 is provided). |
| models | array | yes | Array of model IDs to compare (runs in parallel). |
| system_prompt | string | – | Optional system prompt sent to every VLM. |
| test_cases | array | yes | Array of test cases to run against every model. |
| threshold | number | – | Pass rate threshold for overall verdict (default: 80, 0–100). |
| Name | Type | Req | Description |
|---|---|---|---|
| suites | array | – | – |
| total_failed | number | – | – |
| total_passed | number | – | – |
| verdict | string | – | – |
No examples provided.
sandbox_scenario ~301
Get a ready-made selector-drift test case with a known-correct answer, for testing this MCP server or an agent workflow end to end. Each scenario is a real DOM capture of a deliberately breakable app, taken before and after one specific UI change (a renamed label, two swapped buttons, a duplicated locator, an element moved behind a menu…), plus the verdict those two contracts MUST produce. Call with no arguments to list the scenarios; call with a scenario id to get "baseline" and "current" mappings. THE LOOP: pass baseline and current to diff_mappings, then compare its "verdict" and "counts" to this tool's "expected" — they must match exactly. A mismatch means this server's diff engine has drifted, not that your inputs are wrong. Deterministic and offline: the captures are committed fixtures, identical on every call. Try it live at https://www.ia-qa.com/devtools/sandbox
| Name | Type | Req | Description |
|---|---|---|---|
| include_html | boolean | – | Include the generated HTML of the mutated page (default false). Only useful if you want to render or re-capture it yourself; the loop does not need it. |
| scenario | string | – | Scenario id. Omit to list every available scenario with its expected verdict. Ids: no-change, swap-label, add-testid, duplicate-role-name, remove-element, insert-sibling, rename-label, counter-label,… |
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | object | – | – |
| blurb | – | – | – |
| count | number | – | – |
| current | object | – | – |
| expected | object | – | – |
| how_to_run_the_loop | – | – | – |
| html | – | – | – |
| mutations | array | – | – |
| page | – | – | – |
| scenario | – | – | – |
| scenarios | array | – | – |
| teaches | – | – | – |
| title | – | – | – |
No examples provided.
score_geo_signals ~89
Analyze a webpage <head> HTML (or full HTML) for GEO (Generative Engine Optimization) signals. Returns a score /60 with per-check results and improvement tips. GEO = optimizing pages for AI-powered search engines (ChatGPT Search, Perplexity, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| head_html | string | yes | Raw HTML of the <head> section (or full page HTML) to analyze |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | – | – | – |
| grade | – | – | – |
| max_score | number | – | – |
| passed | number | – | – |
| score | – | – | – |
| total_checks | number | – | – |
No examples provided.
search_jira_issues ~200
Search Jira using JQL (Jira Query Language). Returns matching issues with key fields. Ideal for finding open bugs, sprint tickets, or issues by label/assignee/component. BYOK — credentials transit in-memory only, never stored.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Fields per issue. Default: summary, status, assignee, priority, issuetype, labels, created, updated |
| jira_base_url | string | yes | Atlassian base URL, e.g. "https://mycompany.atlassian.net" |
| jira_email | string | yes | Atlassian account email |
| jira_token | string | yes | Atlassian API token |
| jql | string | yes | JQL query string, e.g. "project = PROJ AND status = Open AND assignee = currentUser() ORDER BY priority DESC" |
| max_results | number | – | Max issues to return (default: 10, max: 50) |
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | – | – |
| jql | string | – | – |
| returned | number | – | – |
| total | number | – | – |
No examples provided.
secret_scan ~239
Scan text or code for leaked secrets: API keys (AWS, GCP, Azure, OpenAI, Anthropic, Stripe, GitHub, GitLab, Slack, Twilio, SendGrid, HuggingFace), private keys (RSA/EC/PGP), JWTs, database connection strings, Bearer tokens, and Basic auth headers. Returns a list of findings with type, severity, line number, and a redacted preview. Use before committing code, sharing logs, or sending text to an LLM. 100% regex-based, zero network calls.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Text or code to scan for secrets |
| types | string | – | Comma-separated families to scan (default: all): aws, gcp, azure, openai, anthropic, huggingface, github, gitlab, stripe, slack, twilio, sendgrid, jwt, private_key, connection_string, bearer, basic_a… |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | – | – | – |
| findings_count | number | – | – |
| input_lines | number | – | – |
| risk_level | – | – | – |
| scanned_types | – | – | – |
| secrets_found | – | – | – |
| summary | string | – | – |
No examples provided.
security_headers_check ~265
Analyse the HTTP security headers of a public URL OR of raw response headers you paste in. Grades each header (A–F) for: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, X-XSS-Protection, Cross-Origin-Opener-Policy, Cross-Origin-Resource-Policy, and Cross-Origin-Embedder-Policy. Returns an overall score (0–100), per-header grades, missing headers, and fix snippets for Express, Nginx, and Apache. For localhost/private targets the remote server cannot reach, pass the `headers` parameter instead of `url`.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | – | – | Optional, and sufficient on its own (no url needed). The response headers to grade, either as an object {"strict-transport-security": "max-age=...", ...} or as the raw header block pasted as a string… |
| url | string | – | Optional. Full public URL to check (e.g. https://example.com). Omit it entirely when using `headers`. The server cannot reach localhost/private IPs. |
| Name | Type | Req | Description |
|---|---|---|---|
| details | – | – | – |
| fix | – | – | – |
| grade | – | – | – |
| header | – | – | – |
| headers_checked | number | – | – |
| key | – | – | – |
| missing | – | – | – |
| missing_count | number | – | – |
| overall_grade | – | – | – |
| score | – | – | – |
| source | – | – | – |
| url | – | – | – |
| value | – | – | – |
| weak | – | – | – |
| weak_count | number | – | – |
| weight | – | – | – |
No examples provided.
shield_analyze ~345
Run a comprehensive AI guardrail analysis on an LLM response. Orchestrates 7 deterministic safety checks plus an optional LLM-powered deep analysis in parallel: hallucination detection (grounding score), prompt injection scan on BOTH the response and the original prompt (reported separately as checks.injection / checks.injection_prompt, scored once at the worse of the two), toxicity scan, output validation (PII/safety), guardrail rules, response quality scoring, and AI verdict (via Qwen, Gemma, Llama, etc.). Returns a unified PASS/FIX/BLOCK verdict with a 0-100 safety score, per-check results, and actionable fix recommendations. PII gates the verdict: an SSN or credit card in the response forces BLOCK, an email forces FIX, phone/IP matches are flagged only (their regexes also match dates and version strings). Use this as a single-call safety gate before surfacing any LLM output to users.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | LLM model for AI-powered deep analysis (default: "openai/gpt-oss-20b"). Set to "none" to skip LLM check. Supports any model from list_llm_models. |
| prompt | string | – | Optional original prompt. Used for quality scoring AND scanned for prompt injection in its own right (checks.injection_prompt) — pass it whenever you have it, it is where the attack actually lands. |
| response | string | yes | The LLM-generated response to analyze |
| rules | array | – | Optional guardrail rules array (same format as guardrail_test tool) |
| source | string | – | Optional reference/source text for hallucination grounding check |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | object | – | – |
| flags | – | – | – |
| grade | – | – | – |
| score | – | – | – |
| verdict | – | – | – |
No examples provided.
similarity_score ~206
Compute text similarity between reference and hypothesis using multiple metrics: Cosine (BoW, TF-IDF), Jaccard, ROUGE-1, ROUGE-2, ROUGE-L, and BLEU. No API key needed. Ideal for LLM eval (expected vs actual), RAG quality checks, and NLG benchmarking. Supports batch mode.
| Name | Type | Req | Description |
|---|---|---|---|
| batch | array | – | Batch mode: array of {reference, hypothesis} pairs. |
| hypothesis | string | – | Hypothesis / actual text (LLM output) |
| metrics | array | – | Metrics to compute (default: all). Options: "cosine_bow", "cosine_tfidf", "jaccard", "rouge1", "rouge2", "rougeL", "bleu" |
| reference | string | – | Reference / expected text (ground truth) |
| threshold | number | – | Optional pass/fail threshold (0-1). Applies to ROUGE-L F1 score. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
| f1 | number | – | – |
| mode | string | – | – |
| precision | number | – | – |
| recall | number | – | – |
| results | – | – | – |
No examples provided.
sort_lines ~129
Sort, deduplicate, reverse, or filter lines of text. Useful for cleaning import lists, dependencies, log files, and config entries.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | For "filter": keep lines containing this substring (case-insensitive) |
| input | string | yes | Multi-line text to process |
| operation | string | – | "sort" (default), "sort_desc", "reverse", "deduplicate", "unique_sort", "filter" |
| remove_empty | boolean | – | Remove empty lines (default: true) |
| trim | boolean | – | Trim whitespace from each line (default: true) |
| Name | Type | Req | Description |
|---|---|---|---|
| line_count | number | – | – |
| original_count | number | – | – |
| removed | number | – | – |
| result | string | – | – |
No examples provided.
split_chunks ~85
Split text into chunks of at most N tokens (cl100k_base: ~4 chars/token) with optional overlap. Designed for RAG ingestion pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_tokens | number | yes | Maximum tokens per chunk (10–8000) |
| input | string | yes | Text to split into chunks |
| overlap | number | – | Token overlap between consecutive chunks (default: 0) |
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_count | number | – | – |
| chunks | array | – | – |
| overlap_tokens | – | – | – |
| tokens_per_chunk | – | – | – |
No examples provided.
ssl_certificate_check ~122
Analyse the SSL/TLS certificate of any HTTPS host. Returns certificate subject, issuer, validity dates, days until expiry, protocol version, cipher suite, key exchange info, and an overall grade (A+, A, B, C, F). Detects expired, self-signed, and weak certificates. Use this to audit TLS posture before production deployment or during security reviews.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname to check (e.g. example.com). Do not include https:// prefix. |
| port | number | – | Port number (default: 443) |
| Name | Type | Req | Description |
|---|---|---|---|
| cipher | object | – | – |
| days_until_expiry | number | – | – |
| grade | string | – | – |
| host | string | – | – |
| is_expired | boolean | – | – |
| is_self_signed | boolean | – | – |
| issuer | object | – | – |
| issues | array | – | – |
| protocol | string | – | – |
| subject | object | – | – |
| valid_from | string | – | – |
| valid_to | string | – | – |
No examples provided.
strip_markdown ~76
Strip all Markdown formatting (headers, bold, italic, code fences, links, lists) from text and return clean plain text. Run this before injecting scraped documentation, README files, or user content into an LLM prompt to eliminate redundant markup tokens and reduce cost.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Markdown text to convert to plain text |
| Name | Type | Req | Description |
|---|---|---|---|
| original_length | number | – | – |
| stripped_length | number | – | – |
| text | – | – | – |
No examples provided.
system_prompt_builder ~136
Build a structured system prompt from components: role, task, constraints, output format, tone, language, and examples. Generates a production-ready system prompt with token estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | – | Rules and constraints to follow |
| examples | string | – | Brief examples to include |
| language | string | – | Response language (e.g. "French") |
| output_format | string | – | Expected output format description |
| role | string | yes | Role/persona (e.g. "Senior QA Engineer", "JSON extraction assistant") |
| task | string | – | Main task or objective |
| tone | string | – | Communication tone |
| Name | Type | Req | Description |
|---|---|---|---|
| sections | object | – | – |
| system_prompt | – | – | – |
| token_estimate | number | – | – |
No examples provided.
test_skill ~254
Validate a SKILL.md definition (Cursor / GitHub Copilot / Windsurf) by auto-generating trigger-positive and trigger-negative scenarios, running each through the model with the skill injected as a system prompt, and scoring trigger accuracy + step adherence. Returns a PASS/FIX/BLOCK verdict with per-scenario breakdown. Uses Groq llama-3.3-70b by default (server key, no api_key needed). Pass api_key + model to use your own provider.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key for the chosen model provider. Not required when using the default Groq model. |
| model | string | – | LLM model ID to use for both scenario generation and testing (e.g. gpt-4o-mini, claude-3-5-haiku-20241022). Defaults to openai/gpt-oss-20b (Groq, server key). |
| scenario_count | number | – | Number of test scenarios to generate: half trigger-positive, half trigger-negative. Default: 6. |
| skill_md | string | yes | Full content of the SKILL.md file to test. Must include a name, a "Use when:" trigger description, and at least one step. |
| Name | Type | Req | Description |
|---|---|---|---|
| scenarios | array | – | – |
| score | number | – | – |
| step_adherence | number | – | – |
| trigger_accuracy | number | – | – |
| verdict | string | – | – |
No examples provided.
text_stats ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The text to analyse |
| Name | Type | Req | Description |
|---|---|---|---|
| chars | – | – | – |
| chars_no_space | – | – | – |
| lines | – | – | – |
| paragraphs | – | – | – |
| reading_time_minutes | – | – | – |
| sentences | – | – | – |
| words | – | – | – |
No examples provided.
timestamp_convert ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | – | – | Unix timestamp (number, seconds or ms) or ISO date string. Omit to get the current time. |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
| iso | string | – | – |
| time | string | – | – |
| unix_ms | number | – | – |
| unix_s | number | – | – |
| utc | string | – | – |
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.