mcp-registry/com.emdly/emdly · v1.0.0
As of 2026-10-17 05:02 UTC, the Emdly MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Search, install and submit Markdown skills for AI agents; private Brain files when signed in.
Claude Code
claude mcp add --transport http emdly-mcp-server https://emdly.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"emdly-mcp-server": {
"type": "http",
"url": "https://emdly.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
39 of 39 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
7 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.
Handshake + tools/list takes ~2,238 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.emdly%2Femdly/fixes
{
"name": "api_list",
"description": "List the apps the owner connected on emdly by API key — Jira, Trello, Airtable, Pipedrive or their own API: name, service, whether you may change data, the skill that explains its API (for a custom API also its base address and the owner's description of it). Pass the name as `app` to api_request.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Api List"
}{
"name": "automation_get",
"description": "Show one automation in the form automation_save takes (edit it and save it back with the same id), what is still missing, and its last runs with every step's answer.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "integer",
"description": "The automation id (automation_list)."
},
"agent": {
"type": "string",
"description": "Your hosted agent's name, when you have several (a hosted agent leaves it out)."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Automation Get"
}{
"name": "automation_list",
"description": "List the automations of the hosted agent: id, name, on/off, what starts it, how many steps, the last run. automation_get shows one whole.",
"inputSchema": {
"type": "object",
"properties": {
"agent": {
"type": "string",
"description": "Your hosted agent's name, when you have several (a hosted agent leaves it out)."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Automation List"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.emdly/emdly"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.emdly/emdly"}) over MCP.
automation_save ~736 tokensga4_report ~510 tokensgsc_query ~497 tokensapi_request ~419 tokensdrive_save ~382 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.emdly%2Femdly?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.emdly%2Femdly?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.emdly%2Femdly.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.emdly%2Femdly.svg :target: https://glimind.com/server/mcp-registry%2Fcom.emdly%2Femdly?ref=badge :alt: MCP agent-readiness
Compare: most reliable knowledge servers · most reliable other servers · most reliable devops servers · most reliable search servers · most reliable design servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 05:02 UTC, the Emdly MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Emdly MCP server advertises 39 tools, including agent_skill_save, api_list, api_request, automation_get, automation_list.
Point your MCP client at this streamable-http endpoint: https://emdly.com/mcp
Glimind scanned all 39 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.