Skip to main content
Glama
shizhMSFT

ORAS MCP Server

by shizhMSFT

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
list_wellknown_registriesB

List well-known public registries with catalog support.

list_repositoriesC

List repositories of a container registry.

list_tagsC

List tags in a repository of a container registry.

list_referrersC

List referrers of a container image or an OCI artifact.

fetch_manifestC

Fetch manifest of a container image or an OCI artifact.

fetch_blobC

Fetch blob referenced by a digest in a manifest.

parse_referenceB

Parse a reference string into its components of registry, repository, tag, and digest.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: fetch_blob retrieves specific blobs, fetch_manifest gets manifests, list_referrers shows referrers, list_repositories lists repositories, list_tags lists tags, list_wellknown_registries lists registries, and parse_reference parses reference strings. The descriptions make it easy to differentiate between these operations.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern (e.g., fetch_blob, list_repositories, parse_reference) using snake_case throughout. This predictability makes it easy for agents to understand and select the right tool based on the action and resource.

Tool Count5/5

With 7 tools, this server is well-scoped for its purpose of interacting with container registries and OCI artifacts. Each tool serves a specific function, such as fetching, listing, or parsing, without redundancy, making the count appropriate and manageable.

Completeness4/5

The tool set covers core operations for registry interaction, including fetching, listing, and parsing, which supports common workflows. However, there are minor gaps, such as the lack of tools for pushing or deleting artifacts, which might require workarounds for full lifecycle management.

Maintenance

ActivityInactive
ResponsivenessNo issues