Azure Verified Modules (AVM) MCP Server

io.github.stefanstrangerPublished by GitHub account stefanstrangerv0.1.5Updated Oct 24, 2026

Discover and explore Azure Verified Modules from the Bicep Public Registry

The publisher's own server: verified.fyi

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Lets an assistant discover and explore Azure Verified Modules published in the Bicep Public Registry, running locally over stdio.

What you can do
  • Discover and explore Azure Verified Modules from the Bicep Public Registry.
  • No individual tools are documented in the supplied manifest, description or README, so the exact operations are not described here.
When to use it
Useful when working with Bicep infrastructure-as-code and you want an assistant to look up Azure Verified Modules rather than searching the registry by hand.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package avm-mcp-server over stdio. No authentication, environment variables or headers are declared. Desktop-only; not executable in a web client. Network access to the Bicep Public Registry is implied by its purpose.
Before you install
No credentials, secrets or write actions are declared. The tool list is not published, so review what the server exposes before relying on it; module information comes from a public third-party registry.

Installation

In SourceWeft

  1. Open Azure Verified Modules (AVM) MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.5LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Verified integrations