mcp-server-circleci (CircleCI-Public/mcp-server-circleci) is an MCP server listed on the M8ven Trust Index. It scores 43 out of 100, grade D. It declares 13 tools. No publisher has claimed this listing.

Caution

43/100

mcp-server-circleci

Item: mcp-server-circleci
Rating: 43
Author: M8ven

A specialized server implementation for the Model Context Protocol (MCP) designed to integrate with CircleCI's development workflow. This project serves as a bridge between CircleCI's infrastructure and the Model Context Protocol, enabling enhanced AI-powered development experiences.

→ CircleCI-Public/mcp-server-circleci· npm: @circleci/mcp-server-circleci· listed on npm

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

CircleCI-Public

Source: npm · also listed on PulseMCP, github_topic

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

npmscored separately PulseMCPnot scored here GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings

🚨

Known vulnerabilities in dependencies: 1 critical, 3 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

🔐

You'll be asked for 1 credential: REQUIRE_REQUEST_TOKEN

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// known CVEs in dependencies1 critical3 high1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3.1.1GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.15.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.15.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.15.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

lowexpress@4.19.2GHSA-qw6h-vgh9-j6wx

express vulnerable to XSS via response.redirect()

Depend on this server? Get alerted when its CVEs change.Watch this server free →

// environment variables

To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.

configDISABLE_TELEMETRYtrue Opt out of usage metrics export

configFILE_OUTPUT_DIRECTORYFile (requires env var): Creates a directory with flaky test details

configMAX_MCP_OUTPUT_LENGTH"": "50000"

configMCP_ALLOWED_HOSTSe =my-mcp.example.com \

configMCP_ALLOWED_ORIGINS

configMCP_ALLOW_UNAUTHENTICATED_NETWORK_ACCESS

configMCP_BIND_HOSTNetwork interface to bind to (default: 0.0.0.0). Set to 127.0.0.1 to restrict to loopback only (not compatible with Docker -p port mapping).

configMCP_FILE_OUTPUT_ROOTS

configProgramData

configProgramFiles

configProgramFiles(x86)

🔐 secretREQUIRE_REQUEST_TOKENPer-user tokens (recommended) Teams with SSO-backed Personal API Tokens =true, no server PAT Each dev forwards their PAT Per developer

configSystemRoot

Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.

deployport

// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

13/13 tools missing one or more hints — config_helper (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); download_usage_api_data (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); find_underused_resource_classes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 0/13 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.15.1 (high), @modelcontextprotocol/sdk@1.15.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail

The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.

// improvement guidance — verified publishers only

We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Verified](https://m8ven.ai/badge/mcp/circleci-public/mcp-server-circleci?variant=verified)](https://m8ven.ai/mcp/circleci-public/mcp-server-circleci)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: c47ce3fa6f6f490fbf9a116bb450c7a8505cc7e7

code hash: cb08ac82cc3895f5194a42062ce58ffe562a7f9b5d2d8f2c081305b24551397c

view raw JSON →

Check MCPs from inside your assistant

Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check

check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern

How to add it →Free · no account needed · works in any MCP client