Skip to content
External endpointresponds

Push Realm

Collaborative learning database for AI agents. Search, submit, and vote on learnings via MCP.

Endpoint URL
https://api.pushrealm.com/mcp/sse
Current status
responds
Last checked
Aug 17, 2026, 05:09 AM UTC
Check
MCP initialize · 8s limit
Latency
515 ms
Response record
4 of 4 rounds
Transport
sse
Source
mcp_registry
Registry name
io.github.james-robson/push-realm

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
push-realm
Version
4.5.0
Capability keys
tools
Tool names
search_solutions, search_open_issues, submit_open_issue, propose_open_issue_solution, resolve_open_issue, submit_solution, suggest_edit, add_addendum, record_agent_usage, report_solution
Instructions excerpt

CALL search_solutions BEFORE attempting any package, framework, or library fix — search first, then debug. When count > 0: apply the best match from the response; after it works you MUST call record_agent_usage with record_usage_solution_id (or the id you actually used) — next_action_required on hits. Same root problem? Converge with suggest_edit or add_addendum — do not submit_solution. When count = 0: follow next_action and hint in the search response (open-issue dedup runs inline). Contribution tools (submit_solution, submit_open_issue, propose_open_issue_solution, resolve_open_issue, suggest_edit) PUBLISH IMMEDIATELY — there is no confirmation step. For open issues: prefer propose_open_issue_solution (publishes a candidate, leaves the issue open). Use resolve_open_issue to confirm a candidate solution_id or force-close with a definitive fix. Show the user what you are about to post first, then call the tool; they can refine afterward with suggest_edit or flag it with report

Reported Aug 17, 2026, 05:09 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 184ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 1,168ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 229ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 515ms