Helprism is listed as active in the registry but did not answer our last check.
Your coding agent keeps your help center current: it drafts article fixes after code changes.
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.
claude mcp add mcp --transport http https://api.helprism.com/mcp
https://api.helprism.com/mcp
[mcp_servers.mcp]
url = "https://api.helprism.com/mcp"
{
"mcpServers": {
"mcp": {
"url": "https://api.helprism.com/mcp"
}
}
}
{
"servers": {
"mcp": {
"type": "http",
"url": "https://api.helprism.com/mcp"
}
}
}
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.helprism.com/mcp | streamable-http | answering | 82 ms | 2 min ago |
Your customers tell Deacon's chat what broke. Your coding agent reads it and fixes the code.
Your coding agent scans your pushed code, reads what's worth fixing, fixes it, and rescans.
Code review for your coding agent's changes: a cloud bug hunt. From $4; $0 if clean or minor-only.
Returns only the unit tests affected by your current Kotlin/Android code changes.
Upgrade intelligence for AI agents: what an upgrade changes, where it touches your code, CVE scans.
Save tokens while coding — your AI agent gets structured code context, not file dumps.
What changed in the packages, APIs and services your code depends on, and the fixes it needs.
Code review on your own machine, for you and your coding agent. Nothing leaves your computer.
Answers built from our own checks of this server.