MCP.Market

Greenlake Service Catalog MCP server

by HewlettPackard·io.github.HewlettPackard/greenlake-service-catalog-mcp·v1.0.3·9 stars

HPE GreenLake service-catalog MCP Server

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
New

9 stars

Reviews

Write one

Nobody has reviewed Greenlake Service Catalog yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Greenlake Service Catalog tools (19, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_endpoint_schema

    Retrieves detailed schema information for a specific service-catalog API endpoint including parameters, request/response models, and validation rules

  • get_service_manager_provision_v1

    Retrieve details for a specific service manager provision entry using the ID for the entry.

  • get_service_manager_provisions_v1

    Retrieve a list of all service manager provision entries.

  • get_service_manager_v1

    Retrieve details for a specific service manager by passing the service manager ID.

  • get_service_managers_v1

    Get a list of available service managers.

  • get_static_tools

    Trigger static tool registrations (one tool per endpoint).

  • get_tool_classes

    Import tool modules so that ``@mcp.tool()`` decorators fire.

  • get_tools

    Return registered tools as MCP protocol Tool objects.

  • getserviceoffer

    Retrieve detailed information about a specific service offer by supplying its unique identifier in the request path. To obtain valid service offer IDs, use the `Get service offers` endpoint to list available offers.

  • getserviceofferregion

    Retrieve detailed information about a specific service offer region by providing its unique identifier in the request path. To obtain valid service offer region IDs, use the `Get service offer regions` endpoint to list available regions.

  • getserviceofferregions

    Retrieve a list of service offer regions by applying filters. Each service offer region represents a service offer provisioned in a specific region. <br><br>**Pagination:** This API supports cursor-based pagination. Provide the cursor in the `next` query parameter to retrieve the next page.

  • getserviceoffers

    Retrieve a list of service offers by applying filters. A service offer provides a distinct set of functionality that can be independently identified and assigned access. <br><br>**Pagination:** This API supports cursor-based pagination. Provide the cursor in the `next` query parameter to retrieve the next page.

  • getserviceprovision

    Fetch service provision details for an ID.

  • getserviceprovisions

    Retrieve a list of service provisions by applying filters. A service offer provides a distinct set of functionalities that can be independently identified and assigned access. Service offers are typically associated with roles and permissions, commerce, metering, quote-to-cash, and trial evaluations. A service provision occurs when a service offer is provisioned (added) to a workspace. <br><br>**P

  • invoke_dynamic_toolwrite action

    Executes any service-catalog API endpoint dynamically with parameter validation and schema support

  • list_endpoints

    Lists all available service-catalog API endpoints with metadata (method:path, operation name, type) for fast discovery and selection. Each endpoint includes a 'type' field: 'list' for collection endpoints, 'detail' for single-resource endpoints that require path parameters.

  • list_service_catalog_items
  • per_region_service_managers_v1

    Retrieve a list of available service managers categorized by region.

  • service_managers_for_a_region_v1

    Retrieve a list of service managers deployed to a particular region.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan38 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 124 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Greenlake Service Catalog compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Tools
19
the typical server has 7
Tools that change things
5%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
9
more than 87% of 28,688 servers

What its tools let an agent do: 18 read · 1 run or deploy

Install Greenlake Service Catalog in Claude Code, Cursor or VS Code

claude mcp add greenlake-service-catalog-mcp -- uvx greenlake-service-catalog-mcp
Add to Cursor

What the publisher says

From the Greenlake Service Catalog repository's README, as published. We do not edit it. Read it on GitHub

HPE GreenLake MCP Servers

A collection of Model Context Protocol (MCP) servers that enable AI assistants to interact with HPE GreenLake platform services.

Table of Contents

  • What is the Model Context Protocol?
  • What's in this Repository?
  • Available MCP Servers
  • Quick Start
  • MCP Client Configuration
  • Tool Modes
  • Architecture Overview
  • Security Considerations
  • Troubleshooting
  • Getting Help
  • Resources
  • License

What is the Model Context Protocol?

The Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you're building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need.

What's in this Repository?

This repository contains production-ready MCP servers for HPE GreenLake platform services. Each server provides AI assistants with secure, read-only access to specific GreenLake APIs, enabling natural language interactions with your HPE infrastructure.

Key Features

  • Standardized Architecture: All servers follow consistent patterns for authentication, configuration, and error handling
  • OAuth2 Authentication: Secure access using HPE GreenLake workspace credentials with automatic token management
  • Dual Tool Modes: Each server supports both static (individual tools per endpoint) and dynamic (meta-tools) operation modes
  • Type-Safe: Built with Pydantic models for runtime validation and type safety
  • Production Ready: Comprehensive logging, error handling, and Docker support
  • Well Tested: Extensive unit and integration test coverage

Available MCP Servers

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Greenlake Service Catalog: common questions

Is Greenlake Service Catalog MCP server safe?
Mostly: it is graded B (83/100). Read the Greenlake Service Catalog safety report
How do I install Greenlake Service Catalog?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Greenlake Service Catalog need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Greenlake Service Catalog maintained?
The last commit was 162 days ago (2026-05-26). The latest release is v1.0.3.
How does Greenlake Service Catalog compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 19 (the typical server has 7); tools that change things 5% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from HewlettPackard →