Integritymcp

com.bluecatPublished by bluecat.comv26.1.0Updated Oct 24, 2026

BlueCat Integrity MCP Server (formerly bammcp)

VerifiedSTDIODesktop onlyCloud & Infrastructure

Overview

AI-generated overview

A local Docker-run MCP server that connects an assistant to a BlueCat Integrity (BAM) deployment for IP address management tasks.

What you can do
Integritymcp is a BlueCat-published MCP server, formerly named bammcp, that exposes a BlueCat Integrity BAM deployment to an AI assistant. It runs as a local container over stdio or streamable HTTP and authenticates to BAM with a service-account or SSO credential pair. The manifest does not list individual tools, so the exact operations are not documented here; the server also supports approval-gated write tools whose request state is sealed with an HMAC key.
When to use it
Consider it when an assistant needs to work with a BlueCat Integrity environment, for example to look up or manage IP address management data. It is aimed at users who already run BlueCat Integrity and want assistant access to it rather than a general-purpose tool.
Requirements
Docker to run the published image, plus network access to the BAM base URL. Required settings include ACCEPT_EULA, BAM_BASE_URL, MCP_AUTH_MODE, and exactly one credential pair: BAM_USERNAME with BAM_PASSWORD, or BAM_SSO_USERNAME with BAM_SSO_PASSWORD. Depending on the auth mode, MCP_API_KEY, MCP_OAUTH_ISSUER, MCP_OAUTH_JWKS_URI, MCP_OAUTH_AUDIENCE, MCP_ED25519_PUBLIC_KEY, MCP_SIGNED_KEY_AUDIENCE, and the request-state keys may also be needed.
Before you install
The server handles BlueCat credentials (BAM_PASSWORD, BAM_SSO_PASSWORD) and client authentication secrets (MCP_API_KEY, MCP_REQUEST_STATE_KEY, MCP_REQUEST_STATE_KEY_PREVIOUS); store these as secrets. MCP_ED25519_PUBLIC_KEY defaults to a shared demo key that authenticates any token holder rather than a specific customer, so set your own. Setting MCP_AUTH_MODE=none leaves the endpoint unauthenticated, and unsetting MCP_OAUTH_AUDIENCE skips audience validation. The server includes write tools…

Installation

In SourceWeft

  1. Open Integritymcp 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. v26.1.0LatestSep 25, 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.