Stream MCP by usefulapi
REMOTE · STREAM.USEFULAPI.IO
Query channels, search messages, and read threads, users and reactions in your Stream Chat app.
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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 redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.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, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 1 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_a_user_and_their_unread_messages” functional
- New prompt “find_messages_that_mention_a_topic” functional
- New prompt “follow_a_thread_and_its_reactions” functional
- New prompt “post_a_message_or_a_reaction_as_a_user” functional
- New prompt “read_a_channel_and_its_latest_messages” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 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 5 Nov 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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.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. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
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 | Redirected | 302 | https://usefulapi.io/stream/ |
| http (plaintext) | http://stream.usefulapi.io/mcp | Inconclusive | 302 | http://stream.usefulapi.io/mcp |
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.
How do I install the Stream MCP by usefulapi server?
Stream MCP by usefulapi 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'
What is the Stream MCP by usefulapi server?
Stream MCP by usefulapi is 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 Stream MCP by usefulapi server safe to use?
Stream MCP by usefulapi scores 18 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 Stream MCP by usefulapi server expose?
Stream MCP by usefulapi 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 Stream MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Stream MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Stream MCP by usefulapi server still maintained?
Stream MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Stream MCP by usefulapi server?
VerifyMCP ran 4 checks on Stream MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Stream MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.