mcp-registry/io.github.paibyun9/ega-v9-mcp · v1.30.0
As of 2026-10-26 16:10 UTC, the Paibyun9 Ega V9 MCP server is up (it requires sign-in) with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 12.9 hours.
MCP access path for EGA V9 execution governance
Point your MCP client at this streamable-http endpoint: https://lcm3-ega-v9-mcp.hf.space/gradio_api/mcp/
1 tool(s) have no description.
Describe what each tool does, when to use it and what it returns in one or two sentences. Models choose tools almost entirely from this text. How to fix →
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Reachable 98.6% of the time over the last 30 days; median recovery 775 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.paibyun9%2Fega-v9-mcp/fixes
{
"name": "ega_v9_mcp__check_login_status",
"description": "",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "ega_v9_mcp_cancel_confirmation",
"description": "Handle an explicit Cancel click using the injected OAuth profile. This never authorizes or performs EGA License Activation.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "ega_v9_mcp_ega_govern_execution",
"description": "Govern an AI workflow through the canonical EGA V9 execution path. Returns: The governance decision and evidence produced by EGA V9.",
"inputSchema": {
"type": "object",
"required": [
"expected_replay_root"
],
"properties": {
"workflow_json": {
"type": "string",
"default": "[{\"id\":\"example\",\"tool\":\"inventory.lookup\",\"action\":\"read\",\"resource\":\"product-123\",\"quantity\":1}]",
"description": "JSON array containing workflow steps to submit to EGA V9."
},
"expected_replay_root": {
"type": "string",
"description": "Optional expected replay root."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.paibyun9/ega-v9-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.paibyun9/ega-v9-mcp"}) over MCP.
ega_v9_mcp_ega_govern_execution ~167 tokensega_v9_mcp_activate_confirmation ~81 tokensega_v9_mcp_build_activation_confirmation ~72 tokensega_v9_mcp_oauth_identity ~66 tokensega_v9_mcp_cancel_confirmation ~64 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.paibyun9%2Fega-v9-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.paibyun9%2Fega-v9-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.paibyun9%2Fega-v9-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.paibyun9%2Fega-v9-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.paibyun9%2Fega-v9-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:786b8ef06c8bfadf…, first seen 2026-10-17, included at leaf 16506 of 74,170. Version history · verify what your client received.
Compare: most reliable security servers · most reliable other servers · most reliable ml servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 16:10 UTC, the Paibyun9 Ega V9 MCP server is up (it requires sign-in) with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 12.9 hours.
Paibyun9 Ega V9 MCP server advertises 6 tools, including ega_v9_mcp__check_login_status, ega_v9_mcp_activate_confirmation, ega_v9_mcp_build_activation_confirmation, ega_v9_mcp_cancel_confirmation, ega_v9_mcp_ega_govern_execution.
Point your MCP client at this streamable-http endpoint: https://lcm3-ega-v9-mcp.hf.space/gradio_api/mcp/
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.