Teamcity MCP

Model Context Protocol (MCP) server for JetBrains TeamCity: control builds, tests, agents and configs from AI coding assistants.

MCP Servers TypeScript Listed MIT

Is Teamcity MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.2 / 10
Provenance Attested
Signed commits 100%
Last push 26d ago
Compare Teamcity MCP
Suggest a correction

In detail: Teamcity MCP scores 76.2/100 (Grade B), ranked #199 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.2/10; 100% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

How Teamcity MCP compares in MCP Servers

  1. #111 iOS Simulator MCP 76.4 +0.2
  2. #112 Bright Data MCP 76.4 +0.2
  3. #113 Teamcity MCP 76.2 this agent
  4. #114 MCP Gsheets 76.2 ±0
  5. #115 Codex Tldraw MCP 76.2 ±0

Bars show each HVTrust score; the tick marks Teamcity MCP’s 76.2.

Where the 76.2 comes from

HVTrust dimensions vs the MCP Servers average

76.2 / 100 · 100.0% confidence

Teamcity MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.2 / 25
9.9 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.8 / 17
1.6 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
12.2 / 20
in line with avg 12.1
AdoptionLog-scaled stars · package downloads
7.0 / 20
in line with avg 7.2

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.2/10. Tighten the weakest checks to improve public safety evidence.
42.6
Activity sub-score · out of 100
#113

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 26 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
30
Forks
21
Last Push
2026-08-31
26 days ago
Commits (4 wk)
2
Downloads (7d)
359
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #199

Analysis

Activity Inputs

42.6 / 100
StarsRepository reach
8.9 / 30
FreshnessLast push recency
21.4 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
6.2 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
6.2 / 10
OpenSSF Scorecard · scanned Sep 26, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 2
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 7
Packaging 10
Pinned-Dependencies 3
SAST 10
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 7

Common questions about Teamcity MCP

Public supply-chain signals for Teamcity MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Teamcity MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Teamcity MCP publish package provenance?
Yes. Teamcity MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Teamcity MCP have an OpenSSF Scorecard?
Teamcity MCP has an OpenSSF Scorecard score of 6.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Teamcity MCP actively maintained?
Maintained. Last push was 26 days ago.
What license does Teamcity MCP use?
Teamcity MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Teamcity MCP's commits signed?
100% of the last 100 commits to Teamcity MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Teamcity MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Teamcity MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Teamcity MCP?

For maintainers

HVTrust scores Teamcity MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 13HVTrust 3Grade 3Listed 2Score 2Scorecard 1Delisted 1Provenance 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 715 spots (#902 → #187)
2026-09-23
HVTrust Changed
HVTrust up 50.0pts (26.8 → 76.8)
2026-09-22
Newly Listed
First tracked at rank #902
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank rose 10 spots (#175 → #165)
2026-09-07
Rank Moved
Rank dropped 19 spots (#152 → #171)
2026-09-05
Rank Moved
Rank dropped 15 spots (#138 → #153)
2026-09-02
Grade Changed
Trust grade C → B
2026-09-02
Rank Moved
Rank rose 534 spots (#659 → #125)
2026-09-02
HVTrust Changed
HVTrust up 25.9pts (50.6 → 76.5)
2026-09-01
Rank Moved
Rank dropped 25 spots (#634 → #659)
2026-08-31
Grade Changed
Trust grade D → C
2026-08-31
Activity Score Changed
Activity score up 6pts (40 → 46)
2026-08-30
Rank Moved
Rank rose 41 spots (#669 → #628)
2026-08-30
Activity Score Changed
Activity score up 8pts (32 → 40)
2026-08-29
Rank Moved
Rank dropped 44 spots (#625 → #669)
2026-08-28
Rank Moved
Rank dropped 21 spots (#604 → #625)
2026-08-27
Scorecard Added
OSSF Scorecard: 5.8/10
2026-08-27
Rank Moved
Rank rose 157 spots (#761 → #604)
2026-08-27
HVTrust Changed
HVTrust up 8.1pts (38.8 → 46.9)
2026-08-26
Rank Moved
Rank dropped 103 spots (#658 → #761)
2026-08-16
Rank Moved
Rank dropped 15 spots (#639 → #654)
2026-08-10
Rank Moved
Rank dropped 22 spots (#607 → #629)
2026-08-08
Newly Listed
First tracked at rank #607

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 76.2 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/teamcity-mcp.svg)](https://hvtracker.net/agents/teamcity-mcp)
HTML:
<a href="https://hvtracker.net/agents/teamcity-mcp"><img src="https://hvtracker.net/badge/teamcity-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON