emdly
REMOTE · EMDLY.COM · SCANNED SEP 24
Search, install and submit Markdown skills for AI agents; private Brain files when signed in.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · emdly.com
claude mcp add --transport http com-emdly-emdly 'https://emdly.com/mcp'
{
"mcpServers": {
"com-emdly-emdly": {
"url": "https://emdly.com/mcp"
}
}
} {
"servers": {
"com-emdly-emdly": {
"type": "http",
"url": "https://emdly.com/mcp"
}
}
} [mcp_servers.com-emdly-emdly] url = "https://emdly.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-emdly-emdly": {
"type": "remote",
"url": "https://emdly.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-emdly-emdly --url 'https://emdly.com/mcp' --transport streamable-http
mcp_servers:
com-emdly-emdly:
url: "https://emdly.com/mcp" {
"McpServers": {
"com-emdly-emdly": {
"Transport": "http",
"Url": "https://emdly.com/mcp"
}
}
} assistant mcp add com-emdly-emdly -t streamable-http -u 'https://emdly.com/mcp'
{
"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.
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.
- 23 Sept 26 +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.
- 21 Sept 26 +1
- 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 security
- “install_skill” reworded the description of “scope” cosmetic
- “install_skill” reworded the description of “target” cosmetic
- 19 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
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 24 Sept 2026 · Probed https://emdly.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=emdly.com | CN=WE1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | a0ee9e875cacde840e9616aee76e3162 |
| SANs: emdly.com, *.emdly.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of emdly.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| emdly.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://emdly.com/mcp | Verified | 200 | |
| http (plaintext) | http://emdly.com/mcp | HTTPS enforced | 301 | https://emdly.com/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 →
brain_get Brain Get ~78
Read one Brain file by name (e.g. coding-conventions.md), across your brains and brains shared with you. Needs your agent bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| brain | string | – | Optional brain to read from (owner-handle/name for shared brains). Omit to search all your brains. |
| name | string | yes | File name including .md |
No output schema declared.
No examples provided.
brain_list Brain List ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
brain_search Brain Search ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brain | string | – | Optional brain to search (owner-handle/name for shared brains). Omit to search all. |
| query | string | yes | Keywords to look for; each word is matched on its own, case-insensitively. |
No output schema declared.
No examples provided.
brain_write Brain Write ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | 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 | yes | File name ending in .md, e.g. customer-faq.md |
No output schema declared.
No examples provided.
get_collection Get Collection ~80
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).
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Collection slug, e.g. laravel-starter. Omit to list all collections. |
No output schema declared.
No examples provided.
get_skill Get Skill ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| skill | string | yes | owner/name, e.g. opsmith/jira-ticket-scorer |
| version | integer | – | Pin a version number; omit for latest. |
No output schema declared.
No examples provided.
install_skill Install Skill ~308
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
search_skills Search Skills ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category slug or name, e.g. code-review. |
| query | string | yes | 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. |
No output schema declared.
No examples provided.
submit_skill Submit Skill ~169
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).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Full Markdown: # title, when to use, rules, output format, ## License |
| category | string | – | Category name; required for a new skill. |
| name | string | yes | kebab-case skill name, unique within your account |
| note | string | – | Release note when submitting a new version of an existing skill. |
No output schema declared.
No examples provided.
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.