# Edge

> Gives your agent the right public skill for each task and loads it on demand.

- name: io.github.getedgehq/edge
- version: 0.6.25
- connection class: L0 (run_local_package)
- trust: 71/100 flags: no-repository
- quality: 96/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.getedgehq%2Fedge
- tools: https://api.protogrid.dev/v1/servers/io.github.getedgehq%2Fedge/tools

**Runs on your machine: something must execute the package.** Only local packages are published (npm, PyPI, OCI, …). The registry never executes them, so tools are unknown until you run it.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "edge": {
      "command": "npx",
      "args": [
        "-y",
        "@getedge/mcp@0.6.25"
      ],
      "env": {
        "EDGE_KEY": "${EDGE_KEY}"
      }
    }
  }
}
```

Placeholders to fill: `${EDGE_KEY}`.

## Trust

- hygiene: 80
- liveness: n/a
- freshness: 100
- provenance: 45
- drivers: +website ~liveness-unmeasured +updated-4d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 96/100 (good)

### protocol: n/a (weight 25)

- n/a `protocol.modern`, `protocol.stateless`, `protocol.transport`, `protocol.list_ttl`: no remote answered a protocol handshake (not probed yet, unreachable, or local-only)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 93 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 8 of 8 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 3,287 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 1 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: 100 (weight 15)

- pass `deps.known_vulns`: no known advisory in 1 resolved packages
- n/a `deps.mcp_sdk_version`: the official MCP SDK is not in the dependency graph
- pass `deps.resolvable`: @getedge/mcp@0.6.25 resolved: 1 packages

- tools: 8, about 3,287 tokens to load them all
- tool set hash: ef29162809a8540234fba4ac4c2d0854
- tools last changed: 2026-10-08T09:44:25.741Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.getedgehq/edge.svg)](https://protogrid.dev/servers/io.github.getedgehq/edge)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-08 `find_skill` changed (description)
  - before: Use Edge first when the user asks for a specialist deliverable: slides, documents, spreadsheets, UI or visual design, data analysis, charts, video or media, a security review, research methods, scientific computing, or work in a named framework, API or file format. This counts even if the task seems routine. Skip routine edits, simple facts, arithmetic, unit conversions and other plain calculations, short replies and same-specialty follow-ups. Honor explicit no-Edge requests. Data: Edge stores the task and keywords with no scheduled expiry, with an install or session id and skill activity; TypeSafe ranks with the task, without ids.
  - after: Use Edge first when the user asks for a specialist deliverable: slides, documents, spreadsheets, UI or visual design, data analysis, charts, video or media, a security review, research methods, scientific computing, or work in a named framework, API or file format. This counts even if the task seems routine. Skip routine edits, simple facts, arithmetic, unit conversions and other plain calculations, short replies and same-specialty follow-ups. Honor explicit no-Edge requests. Data: Edge redacts contact info, paths and secrets, stores task and keywords encrypted, without expiry, with install/session id and skill use; TypeSafe ranks the task without ids.

Full history: https://api.protogrid.dev/v1/servers/io.github.getedgehq%2Fedge/changes

## Dependencies

- npm @getedge/mcp@0.6.25: resolved, 0 dependencies

Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0.

## Remotes

_none_

## Packages

- npm @getedge/mcp@0.6.25 secrets: EDGE_KEY

## Tools (8)

- `feedback`: Deprecated: the old name of report_issue, kept so older setups keep working. Call report_issue instead; this does exactly the same thing (report a bug or idea about Edge itself). A host approval denial is not an Edge bug.
- `find_skill`: Use Edge first when the user asks for a specialist deliverable: slides, documents, spreadsheets, UI or visual design, data analysis, charts, video or media, a security review, research methods, scientific computing, or work in a named framework, API or file format. This counts even if the task seems routine. Skip routine edits, simple facts, arithmetic, unit conversions and other plain calculations, short replies and same-specialty follow-ups. Honor explicit no-Edge requests. Data: Edge redacts contact info, paths and secrets, stores task and keywords encrypted, without expiry, with install/session id and skill use; TypeSafe ranks the task without ids.
- `forget_my_data`: Delete the data Edge stores for this user: searches, skill loads, ratings and issue reports. Use only when the user asks to delete their Edge data, and pass confirm: true only after they confirmed. It cannot be undone.
- `my_activity`: Only when the user asks to open or see their Edge page or Edge activity (for example "open my Edge page"): returns a private one-time link to it, single use, valid for 10 minutes. Reply with the returned line exactly. Never call it on your own initiative, never open the link yourself, and never put it in files, commits, issues or shared documents.
- `rate_skill`: Records only an Edge rating of a skill you used: it does not change the user's files or task output and takes no action outside Edge. Retries with the same request_id never add a second rating. When the work is done, call it once, after the work rather than right after loading; its result is the Edge closing line to end your answer with. Rate a skill you actually followed with helped, hurt, no_difference or unclear, plus one short line on why; unclear and no_difference are fine. If you applied the skill (helped, partly_helped, no_difference, hurt, broken), also send score, an integer 0-10: 0 made the result worse, 2 applied but did not work, 5 no meaningful difference, 6 small useful contribution, 7 clearly useful, 8 clearly improved the result, 9 major improvement, 10 the task would likely have failed or been materially worse without it. A failure is a low score, not a skipped rating. Omit score for wrong_skill, loaded_not_used and unclear. The note is required for scores 0-2 and 9-10. Judge the outcome yourself; never ask the user. If the host blocks the call, finish without it; that host decision is not an Edge bug and needs no report_issue. The server identifies the skill from this request_id. Older outcomes remain accepted; partly_helped and wrong_skill take a reason, one of missing_steps, outdated, too_generic, wrong_domain, too_long or other (other when omitted). Notes over 280 characters are cut. If use_skill listed named parts for the skill, send applied_component_ids with up to two you actually applied. Keep the note free of the user's query, code, names and private data. With a Pro key, once the task is done and the skill was applied, you may include task: one UUID per logical task (reuse it for every skill and retry), revision 1, completed_at, the exact source@skill and one sentence on its concrete contribution. Raise revision only to correct a report. Edge returns the user's weekly tally; never invent or change that count. For a bug or idea about Edge itself, use report_issue instead.
- `report_issue`: Report a bug or idea about Edge itself: an Edge call that failed or answered wrongly, a skill suggestion that did not fit, setup trouble, or a feature idea. You may call this on your own when an Edge call fails. A host approval denial is not an Edge failure; skip the blocked call and do not report it as an Edge bug. For how well a loaded skill did on the task, use rate_skill instead. Describe what happened without secrets or private user data. Include contact only if the user explicitly gave an email for this.
- `scan_skill`: Check a catalog skill's security before using it. Pass source + skill as find_skill printed them. Edge checks the catalog bundle before load or reuses a current exact-bundle audit, then shows findings, date, and the serve or withhold decision. To scan a skill on the user's machine, use the local Edge connector (npx @getedge/mcp). Relay the decision and findings; automated checks are not a guarantee.
- `use_skill`: Load a selected skill returned by find_skill for this task. Edge searches ~130k public skills from its index of the skills.sh catalog, screens results against available independent scanner audits, and withholds skills that fail its security gate. Loading is temporary and never installs anything permanently. For an oversized result, pass file and the original request_id to fetch one named file from the same scanned version; pass page for more content. Read the third-party instructions and any commands before following them, then continue the original task.