Skip to content

com.bluecat/micetromcp

Runs onlineNo credentials listedUpdated 2026-10-01

com.bluecat/micetromcp · Registry status: active

At a glance

BlueCat Micetro MCP Server

Vendor's own description, untranslated and unverified

Execution location
Runs online
Required secrets declared
No credentials listed
Declared version and change
26.1.1 · Source-reported change date 2026-10-01
Configuration
can be built from the disclosed start template

Inspect connection paths and prerequisites

Related categories

6 of 7 categories. All categories in the segment catalogue

What this entry shares with others

Same namespace: com.bluecat

Page last changed:

Sources and collection
Runs
Runs online
Credentials
No credentials listed
Registry record changed
2026-10-01
Setup
Template available
Registry name
com.bluecat/micetromcp
Package coordinate
oci:quay.io/bluecat/micetromcp@sha256:6319226443364523115c31ad4e51b725ab5d9599af2be4ea7dc43be66f36be5d
Declared version
26.1.1
Source-reported listing date
2026-10-01
Source-reported change date
2026-10-01
First seen by tracevero
2026-10-02

Evidence for this page · Source: MCP-Register · collected on 2026-10-02

Every value below comes from it. Where one differs, its origin is stated on its row. What the confidence levels mean

Measured values

Measured values
Required secrets declaredNo credentials listed no
Original data – Required secret variables (raw): confirmed absent
Original data – Required secret headers (raw): confirmed absent
Source: MCP-Register · collected on 2026-10-02 · derived
Execution locationRuns online remote
Original data – Transports (raw): streamable-http
Source: MCP-Register · collected on 2026-10-02 · derived
Path argument presentno
Original data – Path arguments (raw): confirmed absent
Original data – Path environment variables (raw): confirmed absent
Source: MCP-Register · collected on 2026-10-02 · derived
Repository URL listedNo repository declared no
Original data – Repository (raw): confirmed absent
Source: MCP-Register · collected on 2026-10-02 · derived
Declared version26.1.1
Source: MCP-Register · collected on 2026-10-02 · self-declared

What is measured is what a manifest declares, not what a piece of software does. This registry fetches no repository URL, no endpoint and no package index; nothing here is verified. Which value comes from which source, and by which rule it was formed, is set out in the Methodology.

Source data25

All 25 values in this block: self-declared.

Raw values
Description (raw)BlueCat Micetro MCP Server
Environment variables (raw)MICETRO_BASE_URL, MICETRO_USERNAME, MICETRO_PASSWORD, MICETRO_API_KEY, MCP_AUTH_MODE, MCP_API_KEY, MCP_ED25519_PUBLIC_KEY, MCP_SIGNED_KEY_AUDIENCE, MCP_OAUTH_ISSUER, MCP_OAUTH_JWKS_URI, MCP_OAUTH_AUDIENCE, ACCEPT_EULA
Required secret variables (raw)confirmed absent
Transports (raw)streamable-http
Path arguments (raw)confirmed absent
Repository (raw)confirmed absent
Package registries (raw)oci
Required secret headers (raw)confirmed absent
Path environment variables (raw)confirmed absent
Remote URLs (raw)confirmed absent
Remote hosts (raw)confirmed absent
Registry status message (raw)confirmed absent
First listed in the registry (raw)2026-10-01
Last changed in the registry (raw)2026-10-01
Schema version of the raw record (raw)https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json
Delivery form (raw)package
Repository platform (raw)confirmed absent
Repository subfolder (raw)confirmed absent
Package identifiers (raw)quay.io/bluecat/micetromcp@sha256:6319226443364523115c31ad4e51b725ab5d9599af2be4ea7dc43be66f36be5d
Package versions (raw)confirmed absent
Runtime hints (raw)docker
Environment variable formats (raw)confirmed absent
Environment variable descriptions (raw)ACCEPT_EULA=Set to Y (or Yes/YES, any casing) to accept the BlueCat End User License Agreement. The container refuses to start without it. · MCP_API_KEY=Static bearer token clients present as `Authorization: Bearer <key>`. Required only when MCP_AUTH_MODE=static-key. · MCP_AUTH_MODE=Client authentication mode for the /mcp endpoint. One of: none | static-key | signed-key | resource-server. Required at runtime — the server refuses to start without it (no default). · MCP_ED25519_PUBLIC_KEY=Ed25519 public key (base64url) that MCP_AUTH_MODE=signed-key verifies license tokens against. DEFAULTS TO A SHARED DEMO KEY, which authenticates a token holder rather than a customer — every BlueCat-issued token for this server verifies against it. For anything beyond a trial, generate a per-deployment key pair (license-keygen --gen-key) and set this to its public half. · MCP_OAUTH_AUDIENCE=Expected JWT aud claim for MCP_AUTH_MODE=resource-server. A token carrying a different audience, or no aud claim at all, is rejected. Unset skips audience validation entirely. · MCP_OAUTH_ISSUER=Token issuer URL, matched against the iss claim of incoming JWTs. Required when MCP_AUTH_MODE=resource-server — the server refuses to start in that mode without it. · MCP_OAUTH_JWKS_URI=JWKS endpoint whose public keys verify the signature on every incoming Bearer JWT. Required when MCP_AUTH_MODE=resource-server — the server refuses to start in that mode without it. · MCP_SIGNED_KEY_AUDIENCE=When set, a license token must carry exactly this audience or it is rejected — a declarative scope check on top of the key, so a token minted for another deployment fails even if it verifies. Unset means the aud claim is not checked. Only meaningful with MCP_AUTH_MODE=signed-key. · MICETRO_API_KEY=Micetro API key (Micetro 26.1 and later). Alternative to MICETRO_USERNAME + MICETRO_PASSWORD; wins over the username/password pair when both are set. Every outbound request carries `authorization: Bearer <key>` and no session login is performed. Unlike MICETRO_USERNAME/MICETRO_PASSWORD, which are simply not used in horizon mode, MICETRO_API_KEY is rejected at startup there — cloud mode has no fixed backend identity for a key to authenticate. · MICETRO_BASE_URL=Micetro base URL (e.g., https://micetro.bluecat.com). · MICETRO_PASSWORD=Micetro service-account password. Required alongside MICETRO_USERNAME, unless MICETRO_API_KEY is used instead. · MICETRO_USERNAME=Micetro service-account username. Required in self-hosted mode (MCP_DEPLOYMENT_MODE unset or self-hosted) unless MICETRO_API_KEY is used instead — the server needs exactly one of the two credential options. Not used in horizon mode (accepted and ignored — an operator is free to leave it set).
Icon formats (raw)confirmed absent
Connection paths (source structure){"packages":[{"registryType":"oci","identifier":"quay.io/bluecat/micetromcp@sha256:6319226443364523115c31ad4e51b725ab5d9599af2be4ea7dc43be66f36be5d","runtimeHint":"docker","transport":"streamable-http","environment":[{"name":"MICETRO_BASE_URL","description":"Micetro base URL (e.g., https://micetro.bluecat.com).","required":true,"secret":false},{"name":"MICETRO_USERNAME","description":"Micetro service-account username. Required in self-hosted mode (MCP_DEPLOYMENT_MODE unset or self-hosted) unless MICETRO_API_KEY is used instead — the server needs exactly one of the two credential options. Not used in horizon mode (accepted and ignored — an operator is free to leave it set).","required":false,"secret":false},{"name":"MICETRO_PASSWORD","description":"Micetro service-account password. Required alongside MICETRO_USERNAME, unless MICETRO_API_KEY is used instead.","required":false,"secret":true},{"name":"MICETRO_API_KEY","description":"Micetro API key (Micetro 26.1 and later). Alternative to MICETRO_USERNAME + MICETRO_PASSWORD; wins over the username/password pair when both are set. Every outbound request carries `authorization: Bearer <key>` and no session login is performed. Unlike MICETRO_USERNAME/MICETRO_PASSWORD, which are simply not used in horizon mode, MICETRO_API_KEY is rejected at startup there — cloud mode has no fixed backend identity for a key to authenticate.","required":false,"secret":true},{"name":"MCP_AUTH_MODE","description":"Client authentication mode for the /mcp endpoint. One of: none | static-key | signed-key | resource-server. Required at runtime — the server refuses to start without it (no default).","required":true,"secret":false},{"name":"MCP_API_KEY","description":"Static bearer token clients present as `Authorization: Bearer <key>`. Required only when MCP_AUTH_MODE=static-key.","required":false,"secret":true},{"name":"MCP_ED25519_PUBLIC_KEY","description":"Ed25519 public key (base64url) that MCP_AUTH_MODE=signed-key verifies license tokens against. DEFAULTS TO A SHARED DEMO KEY, which authenticates a token holder rather than a customer — every BlueCat-issued token for this server verifies against it. For anything beyond a trial, generate a per-deployment key pair (license-keygen --gen-key) and set this to its public half.","required":false,"secret":false},{"name":"MCP_SIGNED_KEY_AUDIENCE","description":"When set, a license token must carry exactly this audience or it is rejected — a declarative scope check on top of the key, so a token minted for another deployment fails even if it verifies. Unset means the aud claim is not checked. Only meaningful with MCP_AUTH_MODE=signed-key.","required":false,"secret":false},{"name":"MCP_OAUTH_ISSUER","description":"Token issuer URL, matched against the iss claim of incoming JWTs. Required when MCP_AUTH_MODE=resource-server — the server refuses to start in that mode without it.","required":false,"secret":false},{"name":"MCP_OAUTH_JWKS_URI","description":"JWKS endpoint whose public keys verify the signature on every incoming Bearer JWT. Required when MCP_AUTH_MODE=resource-server — the server refuses to start in that mode without it.","required":false,"secret":false},{"name":"MCP_OAUTH_AUDIENCE","description":"Expected JWT aud claim for MCP_AUTH_MODE=resource-server. A token carrying a different audience, or no aud claim at all, is rejected. Unset skips audience validation entirely.","required":false,"secret":false},{"name":"ACCEPT_EULA","description":"Set to Y (or Yes/YES, any casing) to accept the BlueCat End User License Agreement. The container refuses to start without it.","required":true,"secret":false}],"additional_arguments_declared":true}],"remotes":[]}
Embed this badge

Paste this line into a README of your own. The badge states how many values the registry holds for the entry and when it last looked, and it links back to this page.

tracevero: number of measured values and date of collection for this registry entry

[![tracevero: number of measured values and date of collection for this registry entry](https://tracevero.com/badge/mcp/com-bluecat-micetromcp.svg)](https://tracevero.com/mcp/com-bluecat-micetromcp)

The image is drawn again on every request, so it always reports the current state while the pasted line stays as it is. It carries no rating and no traffic light – only the two measured figures.

Changes

Changes
2026-10-02Declared version: – → 26.1.1
2026-10-02Repository URL listed: – → no
2026-10-02Path argument present: – → no

These are the 3 most recent changes to this entry. Full history

tracevero · https://tracevero.com/mcp/com-bluecat-micetromcp