Skip to main content
Glama
Sign In

EGA V9 MCP

by io.github.paibyun9
OverviewDiscussionsAdmin

Server Details

MCP access path for EGA V9 execution governance

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
10.0% over 44 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

TDQS

C2.8/5.0

Scored across 6 tools

Disambiguation4/5

Tools are mostly distinct: activation, cancellation, identity building, and governance each have clear purposes. Some ambiguity exists between build_activation_confirmation and activate_confirmation, but descriptions clarify the separation. The empty description for check_login_status weakens clarity.

Naming Consistency3/5

All tools share the ega_v9_mcp_ prefix, which is consistent, but the action portion mixes patterns: verb_noun (activate_confirmation, cancel_confirmation), a double underscore in ega_v9_mcp__check_login_status, and a noun-only name (oauth_identity). This inconsistency reduces predictability.

Tool Count5/5

Six tools is well-scoped for a specialized server handling activation confirmation and governance. Each tool has a distinct role and the count feels neither sparse nor bloated.

Completeness4/5

The server covers the main activation flow (build confirmation, activate, cancel) plus identity, login status, and governance execution. Minor gaps exist, such as no explicit authorization tool, but the descriptions indicate that is intentionally separate. The empty description for check_login_status is a notable omission.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • Removedega_v9_mcp__lambda_
    • Removedega_v9_mcp__lambda__1
    • Addedega_v9_mcp_activate_confirmation
    • Addedega_v9_mcp_cancel_confirmation
  2. 7 tool updates
    • Removedega_govern_execution
    • Addedega_v9_mcp__check_login_status
    • Addedega_v9_mcp__lambda_
    • Addedega_v9_mcp__lambda__1
    • Addedega_v9_mcp_build_activation_confirmation
    • Addedega_v9_mcp_ega_govern_execution
    • Addedega_v9_mcp_oauth_identity
  3. 1 tool update
    • First observedega_govern_execution

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources