Skip to content

MCP servers › io.github.JcJamet › ia-qa-security

MCP server · registry snapshot 2026-10-27 · last tested 2026-10-27

io.github.JcJamet/ia-qa-security

IA-QA Security — 30 tools — the publisher's title

by JcJamet · GitHub account (the registry's namespace rule)repository owner on GitHub: ia-qa-com (another account)Source ↗

Agent security: prompt injection, PII & secret scans, TLS/header/CORS audits, MCP checks. Free. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-27version 1.0.1streamable HTTP30 tools

Summary

io.github.JcJamet/ia-qa-security is a remote MCP server listed in the official MCP registry at version 1.0.1, under the namespace of the GitHub account JcJamet. Its linked repository, github.com/ia-qa-com/mcp, belongs to another GitHub account, ia-qa-com. On 2026-10-27 ProtocolProbe connected to it in read-only mode and read its inventory: 30 tools, 0 resources and 0 prompts.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not checked: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
30
Last tested
2026-10-27

Tool list size

11,273 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (30 tools). Counted with Anthropic's token counter on 2026-10-27, from the tool list we read on 2026-10-27. Median across 23,424 counted servers: 2,725 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-27 (www.ia-qa.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.1).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-27
Mode
read-only (no tool calls)
Latest version
1.0.1, published 2026-10-26 (registry, as of the 2026-10-27 snapshot)
First listed version
2026-10-26 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-10-26; 2 in the 90 days before the 2026-10-27 snapshot.
Most recent 2 versions
  • 1.0.1 · 2026-10-26
  • 1.0.0 · 2026-10-26
(versions still listed in the registry only)
Registry data
snapshot 2026-10-27
Package and repository
checked 2026-10-27
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-26, listed on 2026-10-27 with version 1.0.1 (published 2026-10-26).

Source: the official MCP Registry list on 2026-10-26 and on 2026-10-27.

What it is

What does this server offer?

Observed inventory
30tools
0resources
0prompts

None of its 30 tools are described as changing anything. For 30 the reading was uncertain, so no mark is shown.

  • “Search available MCP tools by keyword or category before calling them.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • querystringrequired“Keyword(s) to search in tool name and description (e.g.”
    • categorystring“Optional: filter by category — data | encoding | text | llm | qa | rag | dev | security | web”
    • with_schemaboolean“Set true to include inputSchema in results (default: false)”
    • max_resultsnumber“Maximum tools to return (default 10, max 50).”
  • prompt_injection_scanon 2 other servers

    “Scan user input or prompts for common prompt injection patterns.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • inputstringrequired“The user input or prompt to scan for injection patterns”
    • sensitivitystring“Detection sensitivity (default: medium)”
  • guardrail_teston 1 other server

    “Test an LLM response against a set of guardrail rules: must-include, must-not-include, max length, required format, language, forbidden patterns, and custom regex.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • responsestringrequired“The LLM response to test”
    • rulesarrayrequired“Array of guardrail rules to check”
  • “Automatically detect and redact Personally Identifiable Information (PII) from text.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • inputstringrequired“Text to redact PII from”
    • typesstring“Comma-separated types to redact (default: all).”
    • markerstring“Custom replacement marker (default: "REDACTED").”
  • “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…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • inputstringrequired“Text or code to scan for secrets”
    • typesstring“Comma-separated families to scan (default: all): aws, gcp, azure, openai, anthropic, huggingface, github, gitlab, stripe, slack, twilio, sendgrid, jwt, private…”
  • validate_agent_trajectoryon 1 other server

    “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).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • tracestring or object or arrayrequired“Agent execution trace as JSON (OpenAI messages array, LangChain run tree) or plain text log (Thought/Action/Observation format).”
    • assertionsarrayrequired“List of assertions to validate against the trace.”
    • formatstring“Trace format.”
  • validate_mcp_responseon 1 other server

    “Validate that an MCP tool response conforms to expected format, schema, and content rules.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    8 inputs, 1 required
    • responsestringrequired“The MCP tool result as a JSON string to validate”
    • expected_typestring“Expected top-level type: "object", "array", "string", "number"”
    • required_keysstring“Comma-separated list of keys that MUST exist in the response (dot-notation for nested: "data.id, data.name")”
    • forbidden_keysstring“Comma-separated list of keys that MUST NOT exist (e.g.”
    • max_response_msnumber“Maximum acceptable latency in ms (will be compared if provided)”
    • actual_latencynumber“Actual measured latency in ms (from the call)”
    • min_itemsnumber“If response is an array, minimum number of items expected”
    • max_size_bytesnumber“Maximum acceptable response size in bytes”
  • mcp_server_health_checkon 1 other server

    “Check an MCP server's tool definitions without contacting it — for a server not deployed yet, a stdio server, or a CI gate.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • manifeststringrequired“JSON text: the answer to tools/list (raw JSON-RPC or its result), an array of tools, one tool definition, or a manifest with name/description/tools.”
    • strictboolean“Also require documentation: every description ≥ 20 characters, every parameter with a description and a type.”
  • mcp_server_evaluateon 1 other server

    “Run a compliance evaluation against a live MCP server over Streamable HTTP, the way a client meets it.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 1 required
    • urlstringrequired“Public URL of the MCP endpoint (e.g.”
    • test_tool_namestring“Tool to call in the tools/call step.”
  • toxicity_scanon 1 other server

    “Scan text for toxic language, hate speech, bias/stereotype framing, violence, sexual and self-harm content.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • textstringrequired“Text to scan”
    • categoriesarray“Categories to check (default: all)”
  • function_call_validateon 1 other server

    “Validate an LLM function call / tool_use output: check that function name is in allowed list, arguments match expected schema, no extra/missing args.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • function_callobjectrequired“The function call object from LLM (e.g.”
    • allowed_functionsarrayrequired“List of allowed function definitions”
  • mcp_schema_linton 1 other server

    “Lint an MCP tool definition for best practices: naming conventions, description quality, schema completeness, required fields consistency, description length.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • tool_definitionobjectrequired“MCP tool definition object with name, description, inputSchema”
Show 18 more tools
  • “Analyse a set of LLM responses generated from the same prompt template but with different demographic variants (gender, origin, age, tone).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • responsesarrayrequired“Array of variant responses to compare for bias”
  • shield_analyzeon 1 other server

    “Run a comprehensive AI guardrail analysis on an LLM response.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    5 inputs, 1 required
    • responsestringrequired“The LLM-generated response to analyze”
    • sourcestring“Optional reference/source text for hallucination grounding check”
    • promptstring“Optional original prompt.”
    • rulesarray“Optional guardrail rules array (same format as guardrail_test tool)”
    • modelstring“LLM model for AI-powered deep analysis (default: "openai/gpt-oss-20b").”
  • security_headers_checkon 3 other servers

    “Analyse the HTTP security headers of a public URL OR of raw response headers you paste in.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs
    • urlstring“Optional.”
    • headers“Optional, and sufficient on its own (no url needed).”
  • ssl_certificate_checkon 1 other server

    “Analyse the SSL/TLS certificate of any HTTPS host.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 1 required
    • hoststringrequired“Hostname to check (e.g.”
    • portnumber“Port number (default: 443)”
  • “Test a URL for CORS misconfigurations.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 1 required
    • urlstringrequired“Full URL to test (e.g.”
    • originstring“Custom Origin header to test (default: tests multiple origins automatically)”
  • cors_checkeron 1 other server

    “Check the CORS configuration of a URL the same way a browser would.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • urlstringrequired“Full URL to test, e.g.”
    • originstring“Origin header to simulate (default: https://yourdomain.com)”
    • methodstring“HTTP method to simulate (default: GET)”
  • cookie_security_auditon 1 other server

    “Audit the security attributes of cookies set by any URL.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • urlstringrequired“Full URL to audit (e.g.”
  • web_security_auditon 1 other server

    “Run a comprehensive web security audit combining headers, SSL, CORS, and cookies checks — then use an LLM to produce a prioritised remediation plan.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • urlstringrequired“Full URL to audit (e.g.”
    • modelstring“LLM model for AI analysis (default: "openai/gpt-oss-20b").”
    • api_keystring“Your Groq or HuggingFace API key.”
  • “Give honest usage feedback on an IA-QA MCP tool.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 2 required
    • tool_namestringrequired“Name of the MCP tool to rate (e.g.”
    • scorenumberrequired“Rating from 1 (poor) to 5 (excellent)”
    • commentstring“Strongly encouraged — explain what you were trying to do and whether the tool got you there.”
  • “Decode a JWT (JSON Web Token) and return its header and payload without verifying the signature.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    1 input, 1 required
    • tokenstringrequired“The JWT string to decode (header.payload.signature)”
  • validate_urlon 3 other servers

    “Parse and validate a URL.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • inputstringrequired“URL to validate and parse”
  • http_status_lookupon 2 other servers

    “Look up detailed information about any HTTP status code: class, name, description, cacheability, typical causes, and handling best practices.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • codenumberrequired“HTTP status code (e.g.”
  • parse_http_headerson 1 other server

    “Parse a raw HTTP headers block into a structured JSON object.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • headersstringrequired“Raw HTTP headers (one "Name: Value" per line)”
    • analyze_securityboolean“Audit for missing security headers (default: true)”
  • detect_secretson 4 other servers

    “Scan code or config files for hardcoded secrets: AWS keys, GitHub tokens, OpenAI/Anthropic API keys, Stripe secrets, JWTs, database connection strings, and generic passwords.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • inputstringrequired“Code or config content to scan (max 500KB)”
    • filenamestring“Optional filename for context (e.g.”
  • latency_benchmarkon 2 other servers

    “Measure response time of one or more HTTP endpoints (GET/POST).”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 1 required
    • endpointsstring or arrayrequired“Endpoints to benchmark.”
    • iterationsnumber“Number of iterations per endpoint (default: 3, max: 10)”
  • “Compute a cryptographic hash of a text string.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • inputstringrequired“Text to hash”
    • algorithmstring“Hash algorithm: sha256 (default), sha512, sha1, md5”
  • generate_passwordon 15 other servers

    “Generate a cryptographically secure random password using crypto.randomBytes.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    4 inputs
    • lengthnumber“Password length (4–128, default: 16)”
    • uppercaseboolean“Include uppercase letters (default: true)”
    • numbersboolean“Include digits (default: true)”
    • symbolsboolean“Include symbols like !@#$ (default: false)”
  • generate_hmacon 1 other server

    “Compute an HMAC signature for a message using a secret key.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 2 required
    • messagestringrequired“Message to sign”
    • secretstringrequired“Secret key”
    • algorithmstring“Hash algorithm: sha256 (default), sha512, sha1, md5”
    • encodingstring“Output encoding (default: hex)”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-27.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 74
Tools with a description
100% of 30
Typical description length
421 characters

The tool set

Counted from the listing

Tools
30
Size of the list
about 9,851 tokens for an agent to load (characters ÷ 4)
Naming
30 of 30 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 30 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-27 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://www.ia-qa.com/mcp/security
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "ia-qa-security": {
      "url": "https://www.ia-qa.com/mcp/security"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "ia-qa-security": {
      "type": "http",
      "url": "https://www.ia-qa.com/mcp/security"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"ia-qa-security","type":"http","url":"https://www.ia-qa.com/mcp/security"}'
Claude Code
claude mcp add --transport http ia-qa-security https://www.ia-qa.com/mcp/security
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "ia-qa-security": {
      "type": "streamableHttp",
      "url": "https://www.ia-qa.com/mcp/security",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "ia-qa-security": {
      "httpUrl": "https://www.ia-qa.com/mcp/security"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.ia-qa-security]
url = "https://www.ia-qa.com/mcp/security"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "ia-qa-security": {
      "url": "https://www.ia-qa.com/mcp/security"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://www.ia-qa.com/mcp/security --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint www.ia-qa.com/mcp/securitySession openedmatchesour test · 2026-10-27
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-27
Repository github.com/ia-qa-com/mcpOpens publiclymatchesapi.github.com · 2026-10-27

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.JcJamet · 4 servers
GitHub owner
an organization (ia-qa-com)
Repository
github.com/ia-qa-com/mcp
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no

Source: the registry entry and api.github.com · 2026-10-27.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public. It belongs to the GitHub account "ia-qa-com", not "jcjamet" from this server's name; the registry does not check that a publisher owns the repository it links, so the repository checks below describe that repository.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-27. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.JcJamet/ia-qa-security

Answered from the data above

Who publishes io.github.JcJamet/ia-qa-security?

The registry ties the namespace io.github.JcJamet to the GitHub account JcJamet; only its owner can publish under it. Its linked repository, github.com/ia-qa-com/mcp, belongs to another GitHub account, ia-qa-com. These are facts from the registry and GitHub, not a rating.

Is io.github.JcJamet/ia-qa-security safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.JcJamet/ia-qa-security need an API key or sign-in?

It opened a session without any credential on 2026-10-27. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.JcJamet/ia-qa-security been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

Where is the source code of io.github.JcJamet/ia-qa-security?

In github.com/ia-qa-com/mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-27
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-27, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 339 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 30 tools, 0 resources, 0 prompts.
  4. 2,683 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-27; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
not stated
GitHub detects no source language in this repository (docs-only or empty)
Hosting type
registry · 2026-10-27
MCP capability
tools
our test · 2026-10-27
Transport
streamable HTTP
registry · 2026-10-27
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-27
Lifecycle status
registry · 2026-10-27
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-10-27
Maintenance
api.github.com · 2026-10-27
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.JcJamet/ia-qa-security: MCP server record.” Data checked 2026-10-27. https://protocolprobe.com/mcp/servers/io.github.JcJamet/ia-qa-security

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 4 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.JcJamet/ia-qa-security)](https://protocolprobe.com/mcp/servers/io.github.JcJamet/ia-qa-security)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology