EGA V9 MCP
REMOTE · LCM3-EGA-V9-MCP.HF.SPACE
MCP access path for EGA V9 execution governance
Available components
Last scanned (2 hours ago)
Scores higher than 26% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Sept 26 0
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Transport: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 29 Sept 26 0
- Endpoint reachability: behind authorisation → not serving MCP ▼ security
- Transport: unverified → fail ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: pass security
- Tool coverage: 83 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 19 Sept 26 0
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 1.30.0 ▼ security
- Tool “ega_govern_execution” was removed ▼ security
- The server changed its declared name: EGA V9 — Execution Governance → Gradio security
- Tool coverage: 100% → 83% ▼ functional
- Schema quality: 72 → 40 ▲ functional
- Schema quality: fair → good functional
- New tool “ega_v9_mcp__check_login_status” functional
- New tool “ega_v9_mcp_activate_confirmation” functional
- New tool “ega_v9_mcp_build_activation_confirmation” functional
- New tool “ega_v9_mcp_cancel_confirmation” functional
- New tool “ega_v9_mcp_ega_govern_execution” functional
- New tool “ega_v9_mcp_oauth_identity” functional
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://lcm3-ega-v9-mcp.hf.space/gradio_api/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hf.space | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 27 Sept 2026 | 12 Apr 2027 | RSA 2048 | SHA256-RSA | f51719dcdf7239b73ac39d3e38d8e9d |
| SANs: hf.space, *.hf.space | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lcm3-ega-v9-mcp.hf.space. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| space. | present | 51168 | 13 | Verified |
| hf.space. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://lcm3-ega-v9-mcp.hf.space/.well-known/oauth-protected-resource"
Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://lcm3-ega-v9-mcp.hf.space/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| www-authenticate | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://lcm3-ega-v9-mcp.hf.space/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://lcm3-ega-v9-mcp.hf.space/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://lcm3-ega-v9-mcp.hf.space/gradio_api/mcp/ |
| Authorisation server | https://huggingface.co |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lcm3-ega-v9-mcp.hf.space/gradio_api/mcp/ | Auth required | 401 | |
| http (plaintext) | http://lcm3-ega-v9-mcp.hf.space/gradio_api/mcp/ | HTTPS enforced | 301 | https://lcm3-ega-v9-mcp.hf.space:443/gradio_api/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ega_v9_mcp__check_login_status ~12
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ega_v9_mcp_activate_confirmation ~41
Handle explicit Activate click. Authorization remains separate from activation. After explicit authorization, hand off the verified OAuth identity to the existing JS activation path.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ega_v9_mcp_build_activation_confirmation ~38
Build the activation confirmation from a verified Hugging Face identity. This function does not authorize or perform EGA License Activation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ega_v9_mcp_cancel_confirmation ~35
Handle an explicit Cancel click using the injected OAuth profile. This never authorizes or performs EGA License Activation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ega_v9_mcp_ega_govern_execution ~78
Govern an AI workflow through the canonical EGA V9 execution path. Returns: The governance decision and evidence produced by EGA V9.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_replay_root | string | yes | Optional expected replay root. |
| workflow_json | string | – | JSON array containing workflow steps to submit to EGA V9. |
No output schema declared.
No examples provided.
ega_v9_mcp_oauth_identity ~37
Build the minimum verified identity from Hugging Face OAuth. OAuth authentication does not authorize or perform EGA License Activation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the EGA V9 MCP server?
EGA V9 MCP is a hosted endpoint at https://lcm3-ega-v9-mcp.hf.space/gradio_api/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · lcm3-ega-v9-mcp.hf.space
claude mcp add --transport http paibyun9-ega-v9-mcp 'https://lcm3-ega-v9-mcp.hf.space/gradio_api/mcp/'
What is the EGA V9 MCP server?
EGA V9 MCP is listed in the public MCP registry as io.github.paibyun9/ega-v9-mcp. MCP access path for EGA V9 execution governance. This page covers its hosted endpoint (https://lcm3-ega-v9-mcp.hf.space/gradio_api/mcp/).
Is the EGA V9 MCP server safe to use?
EGA V9 MCP scores 37 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EGA V9 MCP server expose?
EGA V9 MCP exposes 6 tools: ega_v9_mcp_oauth_identity, ega_v9_mcp_build_activation_confirmation, ega_v9_mcp_activate_confirmation, ega_v9_mcp_cancel_confirmation, ega_v9_mcp_ega_govern_execution, ega_v9_mcp__check_login_status. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.
Does the EGA V9 MCP server require authentication?
Yes. EGA V9 MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the EGA V9 MCP server still maintained?
EGA V9 MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.