io.usefulapi/stream
REMOTE · STREAM.USEFULAPI.IO · SCANNED SEP 20
Query channels, search messages, and read threads, users and reactions in your Stream Chat app.
Available components
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 → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1345 tokens (~103/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/stream MCP server?
io.usefulapi/stream is a hosted endpoint at https://stream.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · stream.usefulapi.io
claude mcp add --transport http io-usefulapi-stream 'https://stream.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-stream": {
"url": "https://stream.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-stream": {
"type": "http",
"url": "https://stream.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-stream] url = "https://stream.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-stream": {
"type": "remote",
"url": "https://stream.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-stream --url 'https://stream.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-stream:
url: "https://stream.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-stream": {
"Transport": "http",
"Url": "https://stream.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-stream -t streamable-http -u 'https://stream.usefulapi.io/mcp'
{
"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.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Sept 26 +54
- Transport: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Destructive annotations: 100 functional
- 9 Sept 26 −10
- Endpoint reachability: behind authorisation → not serving MCP ▼ security
- Transport: pass → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
- 7 Sept 26 +10
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Transport: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 4 Sept 26 −10
- Endpoint reachability: behind authorisation → not serving MCP ▼ security
- Transport: pass → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
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 20 Sept 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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 82f4e93c7750e7e00ec9b94bcafb8891 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://stream.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://stream.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://stream.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://stream.usefulapi.io/mcp |
| Authorisation server | https://stream.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stream.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://stream.usefulapi.io/mcp | Inconclusive | 401 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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 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.
| 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}.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
What is the io.usefulapi/stream MCP server?
io.usefulapi/stream is an MCP server listed in the public MCP registry as io.usefulapi/stream. Query channels, search messages, and read threads, users and reactions in your Stream Chat app. This page covers its hosted endpoint (https://stream.usefulapi.io/mcp).
Is the io.usefulapi/stream MCP server safe to use?
io.usefulapi/stream scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/stream MCP server expose?
io.usefulapi/stream exposes 13 tools: stream_get_app, stream_query_channels, stream_get_channel, stream_search_messages, stream_get_message, and 8 more. Their descriptions and schemas cost roughly 1,345 tokens of context every time the server is loaded.
Does the io.usefulapi/stream MCP server require authentication?
Yes. io.usefulapi/stream asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/stream MCP server still maintained?
io.usefulapi/stream is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.