Skip to main content
Glama
vivekanjana76

azure-compliance-mcp

by vivekanjana76
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_complianceA

Evaluate named security/governance controls and report where each verdict came from.

Honest about provenance: every finding carries a source (arg | azure_policy | defender), and controls whose signal is not in the available data report not_evaluable rather than guessing. Most controls read the Azure Resource Graph resources row directly (no policy assignment required); guest_config_extension reads guest-config compliance from the ARG policyresources table and is not_evaluable when no policy is assigned. disk_encryption is partial — it confirms encryption-at-host from ARG but cannot see disk-level/ADE encryption, so a missing host-encryption signal is not_evaluable, not fail.

query_resourcesA

Look up resources with structured, read-only filters.

All filters are combined with AND. Returns an ARG-shaped projection.

get_patch_statusA

Report per-VM patch/update posture from Azure Resource Graph patch assessments.

Honest about provenance: every finding carries source="arg" — verdicts come from the ARG patchassessmentresources table (Azure Update Manager assessment data), never inferred from resource properties alone. A VM whose posture cannot be trusted is not_evaluable — a deallocated/stopped VM (Azure cannot assess a stopped VM) or a VM with no assessment data — with pendingUpdateCount null (unknown, not zero), never a fake "current".

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: check_compliance evaluates specific security controls, get_patch_status reports VM patch posture, and query_resources performs generic read-only queries. No overlap in functionality.

Naming Consistency5/5

All tool names use lowercase with underscores and follow a clear verb_noun pattern (check_compliance, get_patch_status, query_resources), providing a predictable and consistent naming scheme.

Tool Count4/5

With only 3 tools, the server is tightly focused on Azure compliance and resource queries. While the count is somewhat minimal, each tool is well-justified and covers the core use cases without being overloaded.

Completeness4/5

The tool set covers compliance evaluation, patch status, and generic resource queries, which together address a broad range of compliance workflows. The generic query tool compensates for potential gaps, though some specialized compliance checks might be missing.

Maintenance

ActivityStale
ResponsivenessUnresponsive

Resources