Greenlake Reporting MCP server

by HewlettPackard·io.github.HewlettPackard/greenlake-reporting-mcp·v1.1.2·9 stars

No reviews yet

HPE GreenLake reporting MCP Server

B83/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B83/100

full report

Adoption

Growing

9 stars35 downloads/wk

Reviews

Write one

Nobody has reviewed Greenlake Reporting yet.

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

Greenlake Reporting tools (9, 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 reporting API endpoint including parameters, request/response models, and validation rules
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.
getreportingstatusbyid
Retrieve the status of a specific report by passing the report status ID.
getreportingstatuses
This API is designed to fetch the status of all reports for a specific workspace. Only reports belonging to the workspace ID and username are returned. This API supports pagination, allowing you to use offset and limit parameters.
invoke_dynamic_toolwrite action
Executes any reporting API endpoint dynamically with parameter validation and schema support
list_endpoints
Lists all available reporting 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_reporting_items

Public scan report

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

no findings

Code scan28 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.Rubric Appeal a finding JSON

How Greenlake Reporting 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: 9; the typical server has 7
Tools that change things: 11%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 9; more than 87% of 28,688 servers
Downloads a week: 35; more than 25% of 12,191 servers with a package

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

Install Greenlake Reporting in Claude Code, Cursor or VS Code

claude mcp add greenlake-reporting-mcp -- uvx greenlake-reporting-mcp

Add to Cursor

What the publisher says

From the Greenlake Reporting 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.

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 Reporting: common questions

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