testrail-mcp-server@0.3.3
VERIFIED· not startedPublisher claims: "MCP server for TestRail — CRUD plus AI test-case generation from text, Jira tickets, and Confluence pages" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
CONFLUENCE_API_TOKENJIRA_API_TOKENTESTRAIL_API_KEYConfiguration, not credentials: CONFLUENCE_BASE_URL, CONFLUENCE_EMAIL, JIRA_BASE_URL, JIRA_USER, MCP_TRANSPORT, TESTRAIL_BASE_URL, TESTRAIL_PROJECT_ID, TESTRAIL_SUITE_ID, TESTRAIL_USER, TR_PRIORITY_ID, TR_TEMPLATE_ID, TR_TYPE_ID- Where it talks to
- no vendor host named in the code
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for CONFLUENCE_API_TOKEN, JIRA_API_TOKEN, TESTRAIL_API_KEY and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
"TESTRAIL_API_KEY in .env."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Jira not configured. Set JIRA_BASE_URL, JIRA_USER, JIRA_API_TOKEN in .env."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."CONFLUENCE_API_TOKEN in .env."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.raise ValueError("project_id required (or set TESTRAIL_PROJECT_ID in .env).")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.raise ValueError("project_id required (or set TESTRAIL_PROJECT_ID in .env).")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for testrail-mcp-server@0.3.3 as of 8 h ago. This is the package itself, not its dependencies.