# appveyor-mcp

CI pipeline monitoring for GitLab and GitHub - no API key.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.3
- **Author:** io.github.mrfentmen
- **License:** MIT
- **npm:** appveyor-mcp
- **Source:** https://github.com/mrfentmen/premium-mcps
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 2 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-03T06:28:13.785Z
- **Version scanned:** 1.0.3
- **CVEs:** none found by OSV at scan time

## Tools

9 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `project_pipelines` — List the most recent GitLab CI pipelines for a project, newest first, with status, branch, trigger, age and duration. No API key needed.
- `pipeline_detail` — Fetch one CI pipeline by id: status, branch, commit, trigger source, timings and URL.
- `pipeline_jobs` — Show every job in a pipeline grouped by stage, with status, duration and the failure reason, plus the first job you should look at when a build is red.
- `ci_stats` — Measure a project's pipeline health over its recent runs: success rate, average duration, the flakiest branches and a plain verdict.
- `latest_ci_status` — Check the newest pipeline of up to 10 projects at once and report a compact green or red build board with age and duration.
- `github_workflow_runs` — List recent GitHub Actions workflow runs for a public repository with conclusion, branch, trigger event and attempt number.
- `github_jobs` — Show the jobs of a GitHub Actions run and name the exact step that failed, so you can go straight to the cause.
- `project_releases` — List a GitLab project's published releases newest first, with tag, release date, author, commit, the headline of the changelog and how many source archives and 
- `repo_languages` — Show which languages a public GitHub repository is written in, with the size and share of each, so you can see the stack a project is built on before reading an

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"appveyor\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"appveyor-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/appveyor-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/appveyor-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/appveyor-mcp
- HTML page: https://forgeregistry.com/registry/appveyor-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.