# emdly (remote · emdly.com)

Search, install and submit Markdown skills for AI agents; private Brain files when signed in.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `emdly.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-emdly-emdly/emdly.md), [page](https://verifymcp.io/servers/com-emdly-emdly/emdly)

## Channel facts

- Endpoint: `https://emdly.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1876 tokens (~208/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the emdly MCP server?

emdly is a hosted endpoint at https://emdly.com/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.

### Claude

```bash
claude mcp add --transport http com-emdly-emdly 'https://emdly.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-emdly-emdly": {
      "url": "https://emdly.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-emdly-emdly": {
      "type": "http",
      "url": "https://emdly.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-emdly-emdly]
url = "https://emdly.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-emdly-emdly": {
      "type": "remote",
      "url": "https://emdly.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-emdly-emdly --url 'https://emdly.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-emdly-emdly:
    url: "https://emdly.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-emdly-emdly": {
      "Transport": "http",
      "Url": "https://emdly.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-emdly-emdly -t streamable-http -u 'https://emdly.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-emdly-emdly": {
      "type": "http",
      "url": "https://emdly.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-23 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “install_skill” rewrote its description, which is the text the model reads
- [cosmetic] “install_skill” reworded the description of “scope”
- [cosmetic] “install_skill” reworded the description of “target”

### 2026-09-19 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (9)

### `search_skills` (~180 tokens)

Search Skills

Use this FIRST, before any non-trivial task, to find a ready-made skill in the emdly catalog (reviewed Markdown playbooks for AI agents). Query with 1–3 short keywords naming the kind of work (e.g. "code review", "jira", "seo audit"); words are matched independently, so a sentence works too. If the result is empty, retry with a single noun, or send an empty query for the top skills. Returns ranked skills with their owner/name id, category, description and install command.

Input parameters:

- `category` (string): Optional category slug or name, e.g. code-review.
- `query` (string, required): 1–3 short keywords for the kind of work (each word is matched on its own against name, description, tags, category and author). Empty = the most popular skills.

### `get_skill` (~84 tokens)

Get Skill

Read a skill's Markdown to inspect it (does not install anything). To install, call install_skill — it returns the file plus the exact path to write it to. Pass version to pin one.

Input parameters:

- `skill` (string, required): owner/name, e.g. opsmith/jira-ticket-scorer
- `version` (integer): Pin a version number; omit for latest.

### `install_skill` (~308 tokens)

Install Skill

Install a skill into the agent you are running in. Returns the complete skill file and the exact path to write it to — YOU must then create that file verbatim (Claude Code: ~/.claude/skills/<name>/SKILL.md, so it becomes available as /<name> in every project; other agents: ./skills/<name>.md) and tell the user where it is. Counts the install. Use target=hermes for Hermes Agent, target=generic for any other agent, scope=project to keep a skill inside the current Claude Code project only (.claude/skills, committable for the team). When emdly agent hosting is enabled and you have a hosted agent, pass agent= to install there instead.

Input parameters:

- `agent` (string): Hosted agent name (only when emdly agent hosting is enabled and you have one).
- `scope` (string): Claude Code only: user (default, ~/.claude/skills, available in every project) or project (.claude/skills in the current project — only when the user asks for a project-local install).
- `skill` (string, required): owner/name, e.g. opsmith/jira-ticket-scorer
- `target` (string): Where the file goes: claude-code (default) → ~/.claude/skills/<name>/SKILL.md; hermes → ~/.hermes/skills/<category>/<name>/SKILL.md; generic → ./skills/<name>.md.

### `get_collection` (~80 tokens)

Get Collection

Curated bundles of skills. Without an argument: list the available collections (slug, name, size). With a slug: the skills in that collection, in order — then call install_skill for each one the user wants (usually all).

Input parameters:

- `collection` (string): Collection slug, e.g. laravel-starter. Omit to list all collections.

### `submit_skill` (~169 tokens)

Submit Skill

Submit a skill to emdly for review (needs sign-in). Creates it under your account — or a new version if you already own one with this name — runs the automated checks and the AI safety scan, and queues it for a human reviewer. Nothing is published by this tool; you get the check results back. The body must be a complete Markdown skill with a title and a "## License" section (MIT recommended).

Input parameters:

- `body` (string, required): Full Markdown: # title, when to use, rules, output format, ## License
- `category` (string): Category name; required for a new skill.
- `name` (string, required): kebab-case skill name, unique within your account
- `note` (string): Release note when submitting a new version of an existing skill.

### `brain_list` (~119 tokens)

Brain List

List the files in your Brains (named sets of private Markdown memory), including brains shared with you. Needs your agent bearer token. Returns the brain, your role in it, name, folder, size, whether the file is in the agent context and shared with members, and when it changed.

Input parameters:

- `brain` (string): Optional brain name; for a brain shared with you, owner-handle/name (e.g. jan/Team). Omit to list every brain.
- `folder` (string): Optional folder filter, e.g. Engineering.

### `brain_search` (~147 tokens)

Brain Search

Use this BEFORE answering anything about the user's own context — their projects, conventions, decisions, people, infrastructure, past work. Searches the user's Brain files (their brains plus those shared with them); every word of the query is matched on its own, case-insensitively, and files are ranked by how many words hit. Returns the matching files with the surrounding lines so you can decide what to brain_get. Needs a signed-in user.

Input parameters:

- `brain` (string): Optional brain to search (owner-handle/name for shared brains). Omit to search all.
- `query` (string, required): Keywords to look for; each word is matched on its own, case-insensitively.

### `brain_get` (~78 tokens)

Brain Get

Read one Brain file by name (e.g. coding-conventions.md), across your brains and brains shared with you. Needs your agent bearer token.

Input parameters:

- `brain` (string): Optional brain to read from (owner-handle/name for shared brains). Omit to search all your brains.
- `name` (string, required): File name including .md

### `brain_write` (~169 tokens)

Brain Write

Create or update a Brain file. Writes to your default brain unless you name one; shared brains need editor access. Replaces the whole body (use mode "append" to add to the end); the previous body is kept as a version. Credentials are refused — the Brain is memory, not a vault. Needs your agent bearer token.

Input parameters:

- `body` (string, required): Markdown content.
- `brain` (string): Brain to write into (owner-handle/name for shared brains, needs editor access). Omit for your default brain.
- `folder` (string): Folder, e.g. Company. New files default to "Agent".
- `mode` (string): replace (default) or append.
- `name` (string, required): File name ending in .md, e.g. customer-faq.md

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-emdly-emdly/emdly#diagnostics

## Score history

- 2026-09-24: 77
- 2026-09-23: 77
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 73
- 2026-09-14: 73
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 68
- 2026-09-02: 68
- 2026-09-01: 67
- 2026-08-31: 67
- 2026-08-30: 68

## Common questions

### What is the emdly MCP server?

emdly is an MCP server listed in the public MCP registry as com.emdly/emdly. Search, install and submit Markdown skills for AI agents; private Brain files when signed in. This page covers its hosted endpoint (https://emdly.com/mcp).

### Is the emdly MCP server safe to use?

emdly scores 77 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 emdly MCP server expose?

emdly exposes 9 tools: search_skills, get_skill, install_skill, get_collection, submit_skill, and 4 more. Their descriptions and schemas cost roughly 1,334 tokens of context every time the server is loaded.

### Does the emdly MCP server require authentication?

No. We connected to emdly without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the emdly MCP server still maintained?

emdly is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://emdly.com/mcp
- Website: https://emdly.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-emdly-emdly/emdly.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-emdly-emdly/emdly.json
- HTML version of this page: https://verifymcp.io/servers/com-emdly-emdly/emdly