Robin Saige we check the tools AI agents call

IA-QA — 130+ QA & Dev Tools for AI Agents

io.github.JcJamet/ia-qa-toolbox

130+ QA & dev tools for AI agents: prompt injection, RAG testing, VLM eval, guardrails. Free.

— the operator's own registry description reported

Publisher io.github.JcJamet · first seen 2026-08-12 · endpoint https://www.ia-qa.com/mcp

allow
verdict
rich-solo
cluster
ok_tools
answers
150
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V3 has answer key ◐
allow — because answers ●, 150 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

Cluster rich-solo · distinctiveness 0.468 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency323 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools150
vs populationhigh
capabilities1
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_1073fdeec167ef262070f33f · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 2 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V3 has answer key ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public84serves public factstruth-checkable against a public source — the V-ladder applies in full
generative32creates contentno answer key exists; disclosure + stability checks, never truth verdicts
computational29deterministic transformsself-checkable by re-computation and known-answer tests
action3changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
orchestration1routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)
unclassified1not classifiable from its textTier-1 only until its tools describe themselves

Tools last seen observed

ab_test_report analyze_diff_bugs analyze_responses base64_decode base64_encode bias_detect bm25_score build_rag_prompt calculate_readability case_convert check_contrast_ratio color_convert compare_models compare_responses consistency_check context_window_check conversation_analyze cookie_security_audit cors_checker cors_test cot_analyzer count_code_lines count_tokens create_confluence_page cron_parse cron_validator decode_jwt detect_language detect_secrets diff_mappings diff_text embedding_similarity env_parse escape_html estimate_llm_cost extract_json_from_text extract_json_path extract_links extract_todos fetch_confluence_page fetch_jira_issue fetch_veille_feed few_shot_formatter find_tool fix_gherkin flatten_json format_bytes format_json format_table function_call_validate generate_ci_workflow generate_curl generate_eval_yaml generate_hmac generate_html_report generate_json_ld generate_password generate_slug generate_test_cases generate_uuid get_testing_guidelines guardrail_test hallucination_check hash_text html_to_markdown http_status_lookup identify_caller jira_to_test_suite json_diff json_schema_generate json_schema_validate json_to_csv json_to_yaml latency_benchmark levenshtein_distance lint_commit_message list_llm_models list_local_tests llm_fit_finder llm_format_check llm_generate llm_json_schema_check llm_output_validator lorem_ipsum mcp_schema_lint mcp_server_evaluate mcp_server_health_check merge_json minify_js mock_from_schema model_info multimodal_eval_guide needle_haystack_generate normalize_vector normalize_whitespace number_base_convert openapi_validate optimize_prompt_tokens parse_csv parse_http_headers post_jira_comment pr_gatekeeper prompt_injection_scan prompt_template_fill prompt_test_suite rag_relevance_rank rate_tool redact_pii regex_test rerank_evaluate response_quality_score run_eval_contract run_pr_gate_pipeline run_semantic_tests run_vlm_test_suite run_vlm_test_suite_batch score_geo_signals search_jira_issues secret_scan security_headers_check shield_analyze similarity_score sort_lines split_chunks ssl_certificate_check strip_markdown system_prompt_builder test_skill text_stats timestamp_convert token_budget_calculator toxicity_scan transform_json_array truncate_to_tokens unescape_html url_decode url_encode validate_agent_trajectory validate_email validate_mcp_response validate_url vector_quantize vector_similarity vector_stats web_security_audit webhook_endpoint_create webhook_endpoint_requests word_frequency xml_to_json yaml_to_json

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific150/150
has a description150/150
description is substantive150/150
parameters are typed148/150148/150
parameters are described150/150

150 of 150 tools graded · 150 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
1.0.0
server version ia-qa-toolbox

Capabilities: tools

Drift observed

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:59:04Zok_tools2003232025-06-18
2026-08-12T05:34:19Zok_tools2003182025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.JcJamet/ia-qa-toolbox.svg)](https://robinsaige.com/s/io.github.JcJamet/ia-qa-toolbox)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview