Item: tinode/chat
Rating: 40.0

tinode/chat

Instant messaging platform. Backend in Go. Clients: Swift iOS, Java Android, JS webapp, scriptable command line; chatbots

[GPL-3.0]M6 · CommunicationG1 · APIs & Web Servicescurrent state

Trust Score

40.0

Last full review 2026-10-06 · Trust Score decays −2 points per month without a fresh review (never below 20)

50%evidence coverage 50%req_1976386e9241

Six dimensions

Anchors 0 · 25 · 50 · 75 · 100

U Ministry Utility

“README: 'Instant messaging full stack. Backend in pure Go... clients for Android (Java), iOS (Swift), and web (ReactJS)...' — generic…”
source unavailable

M Maturity

“api.releases: latest tag v0.25.3 published 2026-07-04; api.repos: pushed_at 2026-09-27; README: 'This is beta-quality software…”
source unavailable

Plan your first step with tinode/chat

tinode/chat looks like a candidate for communication; License GPL-3.0 restricts redistribution for ministry SaaS ambitions.

server:Checking

License: GPL-3.0 has sharing obligations — check them before you build on it.

Use it with

Selected: Gloo AI Studio

Tool names and logos belong to their owners; shown so you can pick your own client. Not affiliated.

Step 1 — Connect Refinry once (prompt only)

Gloo AI Studio does not document external MCP server setup. Use this prompt with the copied Refinry research brief in Studio.

https://studio.ai.gloo.com/

Connection prompt

I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s plain-language agent feed — https://refinry.dev/docs.md — then help me evaluate tinode/chat: summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.

Connection didn't work?

Some clients need manual setup. Follow the plain-language steps on the Docs page.

Step 2 — Plan your first step

Tell the AI what you want to do; edit this to match your situation.

I want to…Starter prompt

I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s public review of tinode/chat (https://refinry.dev) and help me assess it for using tinode/chat for communication in my ministry. Summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites, separating reviewed evidence from what still needs verification. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.

Prefer a hand-off that works without a connection? Copy the research brief: every reviewed fact, all caution flags, and a feasibility-only first assignment.