@uarlouski/testrail-mcp-server

MCPattested
v3.0.0io.github.uarlouskiApache-2.0Updated 1d agonpmGitHub

Connect AI assistants to TestRail: manage test cases, suites, runs, results, and attachments.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
1kDownloads/wk
37GitHub stars
5Forks
1d agoLast update
Needs 1 credential before it runs
  • TESTRAIL_API_KEYAPI keyrequired

    API key for authenticating with the TestRail API

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.uarlouski
LicenseApache-2.0
Version3.0.0
Sourcenpm+mcp-registry
npm@uarlouski/testrail-mcp-server
GitHubuarlouski/testrail-mcp-server
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · e16537e
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv2.3.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 18, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source1mo ago

Forge read 60 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Connect AI assistants to TestRail: manage test cases, suites, runs, results, and attachments.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.