LeashIndex Get the report

Index / other

IA-QA Security — 30 tools

io-github-jcjamet-ia-qa-security declares 30 capabilities across 30 tools, with 2 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

52/100 exposureElevated

Manifest recorded 2026-11-08 from tools/list on https://www.ia-qa.com/mcp/security, published in the official MCP registry as io.github.JcJamet/ia-qa-security 1.0.1. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 30 tools

30 of 30 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · destructive-uncapped · 1 of 30 tools

1 tool is annotated by the server as destructive (destructiveHint) and declares no limit. In MCP that annotation marks a tool that may make destructive changes rather than only additive ones; it does not say the change cannot be undone.

high · no-expiry · All 30 tools

30 of 30 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 30 tools

30 of 30 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

low · uncapped-read · 29 of 30 tools

29 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
find_toolread declared
prompt_injection_scanread declared
guardrail_testread declared
redact_piiread declared
secret_scanread declared
validate_agent_trajectoryread declared
validate_mcp_responseread declared
mcp_server_health_checkread declared
mcp_server_evaluateread declared
toxicity_scanread declared
function_call_validateread declared
mcp_schema_lintread declared
bias_detectread declared
shield_analyzeread declared
security_headers_checkread declared
ssl_certificate_checkread declared
cors_testread declared
cors_checkerread declared
cookie_security_auditread declared
web_security_auditread declared
rate_tooldestructive declared
decode_jwtread declared
validate_urlread declared
http_status_lookupread declared
parse_http_headersread declared
detect_secretsread declared
latency_benchmarkread declared
hash_textread declared
generate_passwordread declared
generate_hmacread declared

Record history

Earlier records for this server. A correction is added here, never written over the record it corrects.

RecordedExposureSource
2026-10-2845 tools/list on https://www.ia-qa.com/mcp/security, published in the official MCP registry as io.github.JcJamet/ia-qa-security 1.0.1
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.