io.github.frozo-ai/edgegate-mcp
NPM · EDGEGATE-MCP · SCANNED AUG 7
Regression-test AI models on real Snapdragon and Jetson hardware, with signed evidence for CI.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 6972 tokens (~120/item across 58 items; 58 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · edgegate-mcp
claude mcp add frozo-ai-edgegate-mcp -- npx -y edgegate-mcp
codex mcp add frozo-ai-edgegate-mcp -- npx -y edgegate-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"frozo-ai-edgegate-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"edgegate-mcp"
],
"enabled": true
}
}
} openclaw mcp add frozo-ai-edgegate-mcp --command npx --arg -y --arg edgegate-mcp
mcp_servers:
frozo-ai-edgegate-mcp:
command: "npx"
args: ["-y", "edgegate-mcp"] {
"mcpServers": {
"frozo-ai-edgegate-mcp": {
"command": "npx",
"args": [
"-y",
"edgegate-mcp"
]
}
}
} 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.
- 7 Aug 26 +4
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.86 functional
- 6 Aug 26 +25
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 43 functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- 5 Aug 26 35
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 7 Aug 2026 · Analysed npm/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
edgegate_run_device_benchmark ~146
Dispatch an ONNX benchmark to one of the customer's connected devices (Jetson, Snapdragon host, gateway) by name/id. The on-device agent picks it up within ~30s and reports latency/memory results. Multi-silicon: works for any vendor the customer has connected. Requires admin role.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device to run on: DB UUID, agent device_id, or the exact display name from edgegate_list_device_targets. |
| model_artifact_id | string | yes | ONNX model artifact in this workspace. |
| model_name | string | – | Label for the result; defaults to the artifact filename. |
| workspace_id | string | yes | – |
No output schema declared.
No examples provided.
edgegate_run_gate ~58
Trigger an EdgeGate run against a pipeline. Returns a run_id you can poll with edgegate_check_status.
| Name | Type | Req | Description |
|---|---|---|---|
| model_artifact_id | string | – | – |
| pipeline_id | string | yes | – |
| workspace_id | string | yes | – |
No output schema declared.
No examples provided.
edgegate_setup_bg_github_action ~190
Generate the Behavioral-Gate GitHub Actions setup — the self-hosted-runner prerequisites, the workflow YAML (using the edgegate-bg composite action), and the gh secret commands. Unlike the standard run gate, BG runs the model on a real device, so it needs a self-hosted runner with the device attached.
| Name | Type | Req | Description |
|---|---|---|---|
| adb_serial | string | – | adb serial of the attached device. |
| api_url | string | – | EdgeGate API URL. Defaults to "https://edgegateapi.frozo.ai". |
| bundle_artifact_id | string | – | – |
| device_label | string | – | – |
| eval_set_artifact_id | string | – | – |
| reference_artifact_id | string | – | – |
| runner_label | string | – | Self-hosted runner label. Defaults to "snapdragon". |
| system_prompt | string | – | – |
| workspace_id | string | yes | – |
No output schema declared.
No examples provided.
edgegate_setup_byo_storage ~288
Enterprise only. Zero-friction BYO storage setup — creates a pending grant with EdgeGate (returns the External ID) and returns the exact AWS CLI commands the agent should run to create the IAM role in the customer's AWS account. Pair with edgegate_attach_byo_role to finalize. Prefer this over edgegate_register_byo_bucket for new setups — the agent doesn't have to figure out the trust policy or guess at role names. Requires owner role. 402 from non-Enterprise workspaces; if a non-pending grant exists, instructs the agent to disconnect first.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | S3 bucket name (not the URI) you want EdgeGate to read model bytes from. |
| kms_key_id | string | – | Optional KMS key ARN if the bucket uses SSE-KMS with a customer-managed key. The IAM role will be granted kms:Decrypt on this key. Leave unset for SSE-S3 or SSE-KMS with the AWS-managed key. |
| region | string | yes | AWS region the bucket lives in, e.g. us-east-1. |
| role_name_override | string | – | Optional override for the IAM role name. Default mirrors the CloudFormation path: edgegate-byo-read-<first-8-chars-of-external-id>. |
| workspace_id | string | yes | Workspace ID. Must be Enterprise-tier with BYO storage enabled. |
No output schema declared.
No examples provided.
edgegate_setup_github_action ~60
Generate the GitHub Actions workflow YAML + gh secret commands so every PR runs EdgeGate as a CI gate.
| Name | Type | Req | Description |
|---|---|---|---|
| model_artifact_id | string | – | – |
| pipeline_id | string | – | – |
| workspace_id | string | yes | – |
No output schema declared.
No examples provided.
edgegate_setup_workspace ~61
Confirm or list EdgeGate workspaces visible to the API key. Run this first in a fresh conversation to lock in which workspace_id the other tools should use.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_id | string | – | Optional UUID. If omitted, lists all visible workspaces. |
No output schema declared.
No examples provided.
edgegate_trigger_replay ~101
Replay pending recorded events against their certified reference (a PASSED gate run for the same model) plus the input-matched baseline. Verdicts land asynchronously — poll edgegate_recorder_status. Events with no certified reference resolve to no_reference.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Optional — only replay events from this device. |
| limit | integer | – | Max pending events to replay this call. Default 100. |
| workspace_id | string | yes | – |
No output schema declared.
No examples provided.
edgegate_update_eval_set ~114
Replace ALL cases of a DRAFT eval-set version (full replacement list, not a patch). Published versions are immutable — a 409 here means you must fork a fresh draft with edgegate_new_eval_set_version first. Still leaves the version a draft; publish separately. Requires workspace write access.
| Name | Type | Req | Description |
|---|---|---|---|
| cases | array | yes | The FULL replacement list of case dicts for this draft version. |
| eval_set_id | string | yes | – |
| version_id | string | yes | – |
| workspace_id | string | yes | – |
No output schema declared.
No examples provided.