soulberto/mcp-azure (soulberto/mcp-azure) is an MCP server listed on the M8ven Trust Index. It scores 70 out of 100, grade C. It declares 37 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
70/100

soulberto/mcp-azure

An MCP server for Azure DevOps that allows users to manage work items, sprints, iterations, and attachments. It supports custom WIQL queries and includes pre-defined prompts for common tasks like sprint planning, bug reporting, and daily standup generation.

→ soulberto/mcp-azure· listed on glama

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 pushwhy connect →

Who stands behind it

soulberto

Source: Glama

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

Glamanot scored here

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: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// tools this server exposes37 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

ado_configure

Configura la conexión a Azure DevOps con token de acceso personal (PAT).

ado_get_work_item

Obtiene un Work Item de Azure DevOps por su ID

ado_query_sprint

Consulta User Stories de un sprint específico en Azure DevOps

ado_query_area

Consulta User Stories de un área específica en Azure DevOps

ado_query_wiql

Ejecuta una consulta WIQL personalizada en Azure DevOps

ado_get_work_item_type_fields

Obtiene los campos disponibles y requeridos para un tipo de Work Item

ado_create_work_item

Crea un nuevo Work Item en Azure DevOps. Usa ado_get_work_item_type_fields para ver campos requeridos.

ado_update_work_item

Actualiza un Work Item existente en Azure DevOps

ado_delete_work_item

Elimina un Work Item en Azure DevOps. Por defecto realiza borrado lógico; usa destroy=true solo para eliminación permanente.

ado_list_iterations

Lista las iteraciones/sprints disponibles en el proyecto

ado_list_areas

Lista las áreas disponibles en el proyecto

ado_add_comment

Agrega un comentario/entrada de discusión a un Work Item. Soporta formato Markdown y menciones. Para mencionar usuarios, primero usa ado_search_users para obtener el ID de identidad (UUID), luego inclúyelo en el campo mentions. En el texto del comentario, escribe @{displayName} donde quieras la menc…

ado_get_comments

Obtiene los comentarios/historial de discusión de un Work Item. Incluye menciones resueltas.

ado_search_users

Busca usuarios en Azure DevOps por nombre o email. Devuelve el ID de identidad (UUID) necesario para menciones en comentarios (@{name}) y otras operaciones. Usa el resultado en ado_add_comment con el campo mentions.

ado_upload_attachment

Sube un archivo como adjunto a Azure DevOps y devuelve la URL del adjunto

ado_add_attachment

Agrega un adjunto a un Work Item existente. Maneja automáticamente concurrencia cuando múltiples adjuntos se agregan al mismo WI.

ado_delete_attachment

Elimina un adjunto de un Work Item removiendo su relación. Maneja automáticamente concurrencia cuando múltiples cambios afectan el mismo WI.

ado_get_attachments

Obtiene la lista de adjuntos de un Work Item

ado_list_repositories

Lista todos los repositorios Git del proyecto.

ado_get_repository

Obtiene detalles de un repositorio específico por nombre o ID.

ado_list_branches

Lista las ramas (branches) de un repositorio.

ado_list_pull_requests

Lista Pull Requests con filtros opcionales. Busca por repositorio o en todo el proyecto.

ado_get_pull_request

Obtiene detalles completos de un Pull Request.

ado_create_pull_request

Crea un nuevo Pull Request.

ado_update_pull_request

Actualiza propiedades de un Pull Request (título, descripción, estado de borrador).

ado_complete_pull_request

Completa (merge) un Pull Request.

ado_abandon_pull_request

Abandona un Pull Request (cambia estado a Abandoned).

ado_approve_pull_request

Aprueba un Pull Request (voto: 10).

ado_reject_pull_request

Rechaza un Pull Request (voto: -10).

ado_get_pull_request_reviewers

Obtiene todos los revisores y sus votos de un Pull Request.

ado_add_pull_request_reviewer

Agrega un revisor a un Pull Request.

ado_get_pull_request_threads

Obtiene todos los hilos de comentarios de un Pull Request.

ado_create_pull_request_thread

Crea un nuevo hilo de comentarios (comentario general o comentario de código).

ado_reply_to_pull_request_thread

Responde a un hilo de comentarios existente.

ado_get_pull_request_commits

Obtiene todos los commits de un Pull Request.

ado_get_pull_request_work_items

Obtiene los work items vinculados a un Pull Request.

ado_update_pull_request_thread_status

Actualiza el estado de un hilo de comentarios (ej: marcar como Fixed, WontFix, etc.).

// known CVEs in dependencies2 high

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

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

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

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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.
configADO_ORGAZURE_DEVOPS_ORG URL de la organización (ej: https://dev.azure.com/mi-org) Sí
configADO_PATAZURE_DEVOPS_PAT Personal Access Token Sí
configADO_PROJECTAZURE_DEVOPS_PROJECT Nombre del proyecto No
configAZURE_DEVOPS_ORGADO_ORG URL de la organización (ej: https://dev.azure.com/mi-org) Sí
configAZURE_DEVOPS_PATADO_PAT Personal Access Token Sí
configAZURE_DEVOPS_PROJECTADO_PROJECT Nombre del proyecto No
// 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

37/37 tools missing one or more hints — ado_configure (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ado_get_work_item (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ado_query_sprint (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +34 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 inputs are validated

33/37 tool handlers declare input schemas (89%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 2 high severity in production deps — @modelcontextprotocol/sdk@1.25.1 (high), @modelcontextprotocol/sdk@1.25.1 (high)

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

Domain consistency

npm scope @slorenzot doesn't match GitHub owner soulberto

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 6 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/soulberto/mcp-azure?variant=verified)](https://m8ven.ai/mcp/soulberto/mcp-azure)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b3338341f9efbb00ca0b081730e8cf846c724db2
code hash: 4c505aa6b13d574fe1ba3a019e5d2408b8364887d4d39f4491b71bb096132690
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