io.usefulapi/stream

REMOTE · STREAM.USEFULAPI.IO · SCANNED AUG 3

Query channels, search messages, and read threads, users and reactions in your Stream Chat app.

Available components

−51 this week 18 18 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security46

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability0

Transport check failed: declared streamable-http, but the endpoint returned HTTP 429. See how to fix → View diagnostics → Fail

Schema Quality & AI Usability0

Schema not yet verified: we couldn't read the endpoint's schema.Unverified

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage0

Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified

Capabilities0

Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · stream.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-usefulapi-stream https://stream.usefulapi.io/mcp

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-stream]
url = "https://stream.usefulapi.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-stream": {
      "type": "remote",
      "url": "https://stream.usefulapi.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add io-usefulapi-stream --url https://stream.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-stream:
    url: "https://stream.usefulapi.io/mcp"

// mcp.json

{
  "mcpServers": {
    "io-usefulapi-stream": {
      "type": "http",
      "url": "https://stream.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.20 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
2 Aug 26 +55
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
1 Aug 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +57
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional

Show 5 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://stream.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=usefulapi.io	CN=WE1,O=Google Trust Services,C=US	17 Jul 2026	15 Oct 2026	ECDSA 256	ECDSA-SHA256	d5ca3133c8d420460e0a811699d7344a
SANs: usefulapi.io, stream.usefulapi.io, *.stream.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of stream.usefulapi.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
usefulapi.io.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	429

Header	Value
x-frame-options	SAMEORIGIN
referrer-policy	same-origin

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://stream.usefulapi.io/mcp	HTTP error	429
http (plaintext)	http://stream.usefulapi.io/mcp	Inconclusive	429

MCP tools — 13 exposed · ~1,345 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

stream_get_app Get app settings ~39

Fetch the Stream app's settings and configured channel types. Good first call to confirm credentials and discover available channel types. GET /api/v2/app.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

stream_get_channel Get channel state + recent messages ~125

Fetch a single channel's state (config, members) and its most recent messages. Note: uses Stream's get-or-create endpoint — for an existing channel it reads; if the type/id does not exist it may be created empty. POST /api/v2/chat/channels/{type}/{id}/query.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Channel id (the part after the type).
messages_limit	integer	—	Recent messages to return. Default 25.
type	string	yes	Channel type, e.g. "messaging", "team", "livestream".

No output schema declared.

No examples provided.

stream_get_message Get a message ~55

Fetch a single message by its id. GET /api/v2/chat/messages/{id}.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Message id.
show_deleted	boolean	—	Include the message even if soft-deleted. Default false.

No output schema declared.

No examples provided.

stream_get_reactions Get message reactions ~61

List the reactions on a message. GET /api/v2/chat/messages/{id}/reactions.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Message id.
limit	integer	—	Max reactions. Default 50.
offset	integer	—	Pagination offset.

No output schema declared.

No examples provided.

stream_get_replies Get thread replies ~69

Fetch the reply messages in a thread, given the parent message id. GET /api/v2/chat/messages/{parent_id}/replies.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max replies (<=300). Default 25.
parent_id	string	yes	Parent (thread-root) message id.

No output schema declared.

No examples provided.

stream_get_unread_counts Get unread counts for a user ~49

Fetch total and per-channel unread message/mention counts for one user. GET /api/v2/chat/unread.

Input Output Examples

Name	Type	Req	Description
user_id	string	yes	User id to fetch unread counts for.

No output schema declared.

No examples provided.

stream_query_channels Query channels ~161

List/filter channels by a Stream query filter. e.g. filter {"type":"messaging"} or {"members":{"$in":["user-1"]}}. Returns channels with recent state. POST /api/v2/chat/channels.

Input Output Examples

Name	Type	Req	Description
filter	object	—	Stream filter_conditions object, e.g. {"type":"messaging"} or {"members":{"$in":["u1"]}}. Default {} (all channels the app can see).
limit	integer	—	Max channels (<=30). Default 30.
message_limit	integer	—	Recent messages per channel to include. Default 25.
offset	integer	—	Pagination offset.
sort	array	—	Default [{"field":"last_message_at","direction":-1}].

No output schema declared.

No examples provided.

stream_query_members Query channel members ~153

List/filter the members of one channel. Requires the channel type + id. Optional member filter, e.g. {"name":{"$autocomplete":"jo"}}. GET /api/v2/chat/members.

Input Output Examples

Name	Type	Req	Description
filter	object	—	Member filter_conditions, e.g. {"user_id":{"$in":["u1","u2"]}}. Default {}.
id	string	yes	Channel id.
limit	integer	—	Max members (<=100). Default 100.
offset	integer	—	Pagination offset.
sort	array	—	Sort spec, e.g. [{"field":"created_at","direction":1}].
type	string	yes	Channel type, e.g. "messaging".

No output schema declared.

No examples provided.

stream_query_threads Query threads ~103

List threads (messages with replies). Server-side calls should pass a user_id to scope thread read-state to that user. POST /api/v2/chat/threads.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max threads (<=25). Default 10.
reply_limit	integer	—	Replies to preview per thread. Default 3.
sort	array	—	Sort spec for threads.
user_id	string	—	User id to scope thread participation/read-state to.

No output schema declared.

No examples provided.

stream_query_users Query users ~124

List/filter users in the app. e.g. filter {"role":{"$eq":"admin"}} or {"id":{"$in":["u1"]}}. GET /api/v2/users.

Input Output Examples

Name	Type	Req	Description
filter	object	—	User filter_conditions, e.g. {"role":{"$eq":"admin"}}. Default {} (all users).
limit	integer	—	Max users (<=100). Default 100.
offset	integer	—	Pagination offset.
sort	array	—	Sort spec, e.g. [{"field":"created_at","direction":-1}].

No output schema declared.

No examples provided.

stream_search_messages Search messages ~189

Search messages across channels. Scope with a channel filter (filter, e.g. {"type":"messaging"}) plus EITHER a full-text `query` OR a `message_filter` object (e.g. {"text":{"$q":"refund"}}). GET /api/v2/chat/search.

Input Output Examples

Name	Type	Req	Description
filter	object	yes	Channel filter_conditions, e.g. {"type":"messaging"} or {"members":{"$in":["u1"]}}.
limit	integer	—	Max results (<=100). Default 20.
message_filter	object	—	Message filter object, e.g. {"text":{"$q":"refund"}} or {"attachments":{"$exists":true}}.
next	string	—	Pagination cursor returned by a previous search.
query	string	—	Full-text search string. Provide this OR message_filter.
sort	array	—	Sort spec for results.

No output schema declared.

No examples provided.

stream_send_message Send a message (WRITE — posts to Stream) ~114

⚠️ WRITE: post a new message to a channel, attributed to user_id (must be an existing user in the app). POST /api/v2/chat/channels/{type}/{id}/message.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Channel id.
mentioned_users	array	—	User ids to @mention.
text	string	yes	Message text.
type	string	yes	Channel type, e.g. "messaging".
user_id	string	yes	Existing user id to send the message as.

No output schema declared.

No examples provided.

stream_send_reaction Send a reaction (WRITE — posts to Stream) ~103

⚠️ WRITE: add a reaction (e.g. "like", "love") to a message, attributed to user_id (must be an existing user). POST /api/v2/chat/messages/{id}/reaction.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Message id to react to.
reaction_type	string	yes	Reaction type, e.g. "like", "love", "haha".
user_id	string	yes	Existing user id to react as.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	69
28 Jul	70
29 Jul	71
30 Jul	69
31 Jul	72
1 Aug	18
2 Aug	73
3 Aug	18