Deacon is answering right now. Last checked 1 min ago.
Your customers tell Deacon's chat what broke. Your coding agent reads it and fixes the code.
Nothing serious here today
Today is the operative word: we check Deacon every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
claude mcp add deacon --transport http https://heydeacon.com/mcphttps://heydeacon.com/mcp[mcp_servers.deacon]
url = "https://heydeacon.com/mcp"{
"mcpServers": {
"deacon": {
"url": "https://heydeacon.com/mcp"
}
}
}{
"servers": {
"deacon": {
"type": "http",
"url": "https://heydeacon.com/mcp"
}
}
}This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://heydeacon.com/mcp | streamable-http | sign-in | 724 ms | 1 min ago |
Alternatives to Deacon
same job, measured the same wayYour coding agent scans your pushed code, reads what's worth fixing, fixes it, and rescans.
Checks the context files a coding agent reads against the git index, and reports what drifted.
AI agents use your app like your users, in real browsers, and report what is broken or confusing.
Free live-app check by an AI agent. On request it fixes the code and tests the app again.
Reads security headers and CSP line by line in your config file and names the lines that silently do
Design your site's AI avatar in the ASMI studio; your coding agent ships it into your repo.
A notebook your coding agents write to: notes that track the code's commit, and handoffs.
Your code review comments from Reado, the read-first IDE, as context and tools for your agent.
Deacon — questions
Answers built from our own checks of this server.