mcpbeat Sign in
answering

dylog is answering right now. Last checked 7 min ago.

Notes, files, GitHub, and Drive through one MCP connection.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 17 days of history
17 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
122 ms
Response time
average over 24h
authentication required
Access
streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add dylog --transport http https://dylog.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "dylog": {
      "url": "https://dylog.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.dylog]
url = "https://dylog.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "dylog": {
      "url": "https://dylog.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "dylog": {
      "url": "https://dylog.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://dylog.app/api/mcp streamable-http needs key 168 ms 7 min ago

Alternatives to dylog

same job, measured the same way
Recall
by imjakezimmer32

Notes, files, GitHub, and Drive through one MCP connection.

answering
TalkMill
by imjakezimmer32

Notes, files, GitHub, and Drive through one MCP connection.

answering
Colab Drive MCP
by yummytastycode

Synchronize Colab notebook files through Google Drive without executing notebook code.

110 installs/wk local only
ClawLink
by claw-link

MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.

answering
Cursor Chat Bridge
by udah1

Drive the Cursor agent from Telegram, Discord, or GitHub — with images and voice notes.

51 installs/wk local only
GitHub
by github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

answering
Mne Docs
by weiyongxu

MCP server for MNE-Python documentation, source code, GitHub issues, and forum

125 installs/wk local only
CLI
by noticedso

Search your developer network and trace connection paths via GitHub & LinkedIn.

53 installs/wk local only

dylog — questions

Answers built from our own checks of this server.

Why is there no tool list for dylog?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is dylog working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 122 ms. The bar chart above shows every period we have measured.
Is dylog still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect dylog?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does dylog need an API key?
Yes. Every time we knock, dylog answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is dylog?
It answers our handshake in 122 ms on average, which is faster than 80% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.