Testrail (Sergey-Bl) MCP Server

testrail-mcp-server PyPI v0.3.3

Published by sergey-bl — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for TestRail — CRUD plus AI test-case generation from text, Jira tickets, and Confluence pages

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 31

Each tool and what it can reach — statically extracted from the published source.

  • get_runingests untrusted input
  • get_test_caseingests untrusted input
  • add_bulk_resultsno sensitive capability
  • add_resultno sensitive capability
  • add_test_cases_bulkno sensitive capability
  • close_runno sensitive capability
  • create_runno sensitive capability
  • create_suiteno sensitive capability
  • create_test_caseno sensitive capability
  • dedupe_against_sectionno sensitive capability
Show 21 more tools ↓
  • find_populated_sectionno sensitive capability
  • flaky_test_detectorno sensitive capability
  • get_or_create_sectionno sensitive capability
  • get_results_for_runno sensitive capability
  • get_tests_in_runno sensitive capability
  • list_projectsno sensitive capability
  • list_runsno sensitive capability
  • list_sectionsno sensitive capability
  • list_suitesno sensitive capability
  • prepare_cases_from_confluenceno sensitive capability
  • prepare_cases_from_jirano sensitive capability
  • prepare_cases_from_textno sensitive capability
  • prepare_coverage_gapsno sensitive capability
  • prepare_feature_bootstrapno sensitive capability
  • prepare_lintno sensitive capability
  • prepare_run_summaryno sensitive capability
  • prepare_runs_diffno sensitive capability
  • preview_house_styleno sensitive capability
  • search_test_casesno sensitive capability
  • update_caseno sensitive capability
  • update_runno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.3.3 latest A 96/100 0 1.13.0 2026-09-04
v0.3.1 A 96/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/testrail-mcp-server-2/badge.svg)](https://mcptrustchecker.com/registry/testrail-mcp-server-2)
HTML
<a href="https://mcptrustchecker.com/registry/testrail-mcp-server-2"><img src="https://mcptrustchecker.com/registry/testrail-mcp-server-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/testrail-mcp-server-2/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan testrail-mcp-server --online --registry pypi

Use the free API → How scoring works

Other implementations of Testrail 8

Independent packages implementing the same tool, scanned with the same engine. Compare all 9 side by side →

More in Security & Testing