Connect The Deploy Log and your agent gets 3 tools, among them deployments_in_week, recent_deployments, search_deployments. It answers at https://deployedbyai.com/log/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 2 October 2026; the last check, on 17 November 2026, succeeded.
AI deployments that shipped and are available now, each sourced to the publisher's own page.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
deployments_in_week | Every row of The Deploy Log that shipped in one ISO week, the same rows as its week page. Each row carries the publisher's own source URL. Inputs: week |
recent_deployments | The newest rows to enter The Deploy Log, newest first. Optionally one lane or one company. Each row names what shipped, when, and the publisher's own source URL. Inputs: lane, company, limit |
search_deployments | Rows of The Deploy Log whose company, subject or what shipped contains the words given, newest first. Each row carries the publisher's own source URL. Inputs: query, limit |
Every block below points at https://deployedbyai.com/log/mcp. Pick your client and copy.
claude mcp add --transport http the-deploy-log https://deployedbyai.com/log/mcp
{
"mcpServers": {
"the-deploy-log": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://deployedbyai.com/log/mcp"]
}
}
}{
"mcpServers": {
"the-deploy-log": {
"url": "https://deployedbyai.com/log/mcp"
}
}
}{
"servers": {
"the-deploy-log": {
"type": "http",
"url": "https://deployedbyai.com/log/mcp"
}
}
}{
"context_servers": {
"the-deploy-log": {
"url": "https://deployedbyai.com/log/mcp"
}
}
}{
"mcpServers": {
"the-deploy-log": {
"serverUrl": "https://deployedbyai.com/log/mcp"
}
}
}{
"mcpServers": {
"the-deploy-log": {
"url": "https://deployedbyai.com/log/mcp"
}
}
}name: The Deploy Log
version: 0.0.1
schema: v1
mcpServers:
- name: The Deploy Log
type: streamable-http
url: https://deployedbyai.com/log/mcp{
"mcpServers": {
"the-deploy-log": {
"httpUrl": "https://deployedbyai.com/log/mcp"
}
}
}{
"mcpServers": {
"the-deploy-log": {
"type": "http",
"url": "https://deployedbyai.com/log/mcp"
}
}
}{
"mcpServers": {
"the-deploy-log": {
"url": "https://deployedbyai.com/log/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fdeployedbyai.com%2Flog%2Fmcp&type=streamable_http&id=the-deploy-log&name=The%20Deploy%20Log
It answered our last check on 17 November 2026 in 450 ms. Over 4 checks since 2 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by deployedbyai.com and served from deployedbyai.com, the vendor's own domain: https://deployedbyai.com/log/mcp.
3, as returned by the server's own tools/list on 20 November 2026: deployments_in_week, recent_deployments, search_deployments.
It answered our last check on 17 November 2026 in 450 ms. Over 4 checks since 2 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://deployedbyai.com/log/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.deployedbyai. Endpoint host: deployedbyai.com. ARD identifier: urn:air:com.deployedbyai:mcp:the-deploy-log.
First indexed 2 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.