CanopiiCanopiiAll serversEnterprise →
Tiberriver256/mcp-server-azure-devops

Tiberriver256/mcp-server-azure-devops vmain@c43b97c

Security Trust Score
Grade F · Serious issues
Tier 1 · Public sourceHigh confidence · 98%
Declared MCP capabilities
ResourcesPrompts

This server scored F. Run it behind runtime policy enforcement so one bad tool call can't become an incident.

1 issue capping this score
  • criticalNo command-injection sinks — 1 occurrence
Reputation382stars125forks38open issues32d agolast commit1yage

Security controls

Deterministic, evidence-backed. Score earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

  • Warn
    Strict JSON Schema Enforcementschemas not strict

    Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.

    Fix: Set additionalProperties:false and require explicit parameters on every tool.

  • Pass
    Indirect Prompt Injection (IPI) Defensesguardno injection markers

    Tool/prompt/resource text is free of hidden instructions that could hijack the agent.

  • Pass
    User-in-the-Loop / Approval Scopeguardno destructive tool scope

    No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.

  • N/A
    Tool Definition Integrityguardno prior version to diff

    Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

Application Security Checks

  • Fail
    No command-injection sinksguard1 occurrence

    Untrusted tool input reaching a shell yields remote code execution. How many servers fail this?

    .pi/extensions/test-watch.ts:478

    Fix: Never pass tool arguments to a shell; use argv arrays with shell disabled.

  • Warn
    No path traversalguard7 occurrences

    Naive path checks let tools read/write outside intended directories (EscapeRoute-class).

    .pi/extensions/test-watch.ts:152.pi/extensions/test-watch.ts:413.pi/extensions/test-watch.ts:792.pi/extensions/test-watch.ts:905

    Fix: Resolve to a canonical path and verify containment; reject ../ and symlinks.

  • Warn
    No SSRF sinksguard4 occurrences

    Fetching tool-supplied URLs can pivot into internal networks and metadata services.

    src/clients/azure-devops.ts:98src/clients/azure-devops.ts:262src/features/organizations/list-organizations/feature.ts:84src/features/users/get-me/feature.ts:46

    Fix: Allow-list destinations; reject arbitrary/loopback/link-local URLs.

  • Warn
    No known-vulnerable dependencies15 of 160 runtime deps vulnerable; worst high

    Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.

    @modelcontextprotocol/[email protected] — GHSA-8r9q-7v3j-jr4g@modelcontextprotocol/[email protected] — GHSA-w48q-cv73-mx4w[email protected] — GHSA-35jp-ww65-95wh[email protected] — GHSA-3g43-6gmg-66jw

    Fix: Upgrade the flagged dependencies past their fixed versions.

  • Warn
    Has a security policyno security policy

    A SECURITY.md gives a private path to report vulnerabilities.

    Fix: Add SECURITY.md with a disclosure contact and process.

  • Pass
    No dynamic code executionguardno sinks found

    eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.

  • Pass
    No unsafe deserializationguardno sinks found

    pickle/yaml.load/etc. on untrusted data can execute code.

  • Pass
    No committed secretsguardno secrets found

    Hardcoded keys/tokens in published source are live credentials an attacker can use.

  • Pass
    Credentials sourced from environmentreads credentials from environment

    Reading secrets from env/secret stores avoids hardcoding them.

  • Pass
    Dependencies pinned (lockfile)lockfile present

    A lockfile makes installs reproducible and resistant to silent dependency swaps.

  • Pass
    Actively maintainedrecent commits

    Unmaintained servers don't receive security fixes.

  • Pass
    Repository not archivedguardactive

    Archived repositories will never be patched.

  • Pass
    Declares a licenseMIT

    A clear license is required for legal enterprise use.

  • Pass
    Adoption & popularityestablished adoption

    A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.

  • Not checked
    Signed releasesnot evaluated

    Signed releases let consumers verify artifacts weren't tampered with.

  • N/A
    No install/post-install scriptsguardno published package

    install hooks run arbitrary code on every consumer at install time.

  • N/A
    Package name not typosquattingguardno published package

    Names mimicking popular packages are a common malware delivery vector.

  • N/A
    Published with provenanceno published package

    Build provenance attests the artifact was built from the claimed source by CI.

  • N/A
    Established maintainerno published package

    Brand-new / single anonymous maintainers raise takeover and malware risk.

Transport & Trust Model

  • Warn
    Execution Sandboxingruns natively (no container image)

    A container/sandbox image limits blast radius; a server that runs natively has full host access.

    Fix: Ship a Dockerfile/Containerfile (or document a sandboxed run) so the server runs isolated.

  • Pass
    Network Exposureno bind-all detected

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

  • N/A
    Transport Encryption (TLS)guardno remote endpoints

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • N/A
    IAM / Authentication Scopingno remote endpoints

    OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.

  • N/A
    Live Endpoint Reachablenot dynamically scanned

    A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.

  • N/A
    Authentication Enforced (live)not dynamically scanned

    If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Tools (55)

BugAgileTeam 1Team 2get_meget_wikisUser StoryTag Contentcreate_wikiget_projectsearch_codesearch_wikiTest Projectget_pipelinelist_commitscreate_branchget_wiki_pageget_work_itemlist_projectsBranch ContentCommit Contentget_repositorylist_pipelineslist_wiki_pageslist_work_itemscreate_wiki_pagecreate_work_itemget_file_contentget_pipeline_logget_pipeline_runget_pull_requesttrigger_pipelineupdate_wiki_pageupdate_work_itemlist_repositoriespipeline_timelinesearch_work_itemsRepository Contentlist_organizationslist_pipeline_runslist_pull_requestscreate_pull_requestget_project_detailsget_repository_treeupdate_pull_requestPull Request Contentmanage_work_item_linkget_repository_detailsget_work_item_commentsadd_pull_request_commentget_pull_request_changesget_all_repositories_treeget_pull_request_commentsdownload_pipeline_artifactupdate_pull_request_thread_status