Federated messaging with your fmsg hosting provider. Connect with OAuth or an API key.
Nothing to run from here
Stream is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
13
tools declared
remote
at its publisher
—
calls last 7d
What it does
Query channels, search messages, and read threads, users and reactions in your Stream Chat app.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-stream-mcp https://stream.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# stream_get_app, stream_query_channels, stream_get_channel and 10 more
Stream costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usefulapi-stream-mcp https://stream.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | object | no | Stream filter_conditions object, e.g. {"type":"messaging"} or {"members":{"$in":["u1"]}}. Default {} (all channels the app can see). |
| sort | array | no | Default [{"field":"last_message_at","direction":-1}]. |
| limit | integer | no | Max channels (<=30). Default 30. |
| offset | integer | no | Pagination offset. |
| message_limit | integer | no | Recent messages per channel to include. Default 25. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Channel type, e.g. "messaging", "team", "livestream". |
| id | string | yes | Channel id (the part after the type). |
| messages_limit | integer | no | Recent messages to return. Default 25. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | object | yes | Channel filter_conditions, e.g. {"type":"messaging"} or {"members":{"$in":["u1"]}}. |
| query | string | no | Full-text search string. Provide this OR message_filter. |
| message_filter | object | no | Message filter object, e.g. {"text":{"$q":"refund"}} or {"attachments":{"$exists":true}}. |
| limit | integer | no | Max results (<=100). Default 20. |
| sort | array | no | Sort spec for results. |
| next | string | no | Pagination cursor returned by a previous search. |
Fetch a single message by its id. GET /api/v2/chat/messages/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Message id. |
| show_deleted | boolean | no | Include the message even if soft-deleted. Default false. |
Fetch the reply messages in a thread, given the parent message id. GET /api/v2/chat/messages/{parent_id}/replies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| parent_id | string | yes | Parent (thread-root) message id. |
| limit | integer | no | Max replies (<=300). Default 25. |
List the reactions on a message. GET /api/v2/chat/messages/{id}/reactions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Message id. |
| limit | integer | no | Max reactions. Default 50. |
| offset | integer | no | Pagination offset. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Channel type, e.g. "messaging". |
| id | string | yes | Channel id. |
| filter | object | no | Member filter_conditions, e.g. {"user_id":{"$in":["u1","u2"]}}. Default {}. |
| sort | array | no | Sort spec, e.g. [{"field":"created_at","direction":1}]. |
| limit | integer | no | Max members (<=100). Default 100. |
| offset | integer | no | Pagination offset. |
List/filter users in the app. e.g. filter {"role":{"$eq":"admin"}} or {"id":{"$in":["u1"]}}. GET /api/v2/users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | object | no | User filter_conditions, e.g. {"role":{"$eq":"admin"}}. Default {} (all users). |
| sort | array | no | Sort spec, e.g. [{"field":"created_at","direction":-1}]. |
| limit | integer | no | Max users (<=100). Default 100. |
| offset | integer | no | Pagination offset. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | string | no | User id to scope thread participation/read-state to. |
| limit | integer | no | Max threads (<=25). Default 10. |
| reply_limit | integer | no | Replies to preview per thread. Default 3. |
| sort | array | no | Sort spec for threads. |
Fetch total and per-channel unread message/mention counts for one user. GET /api/v2/chat/unread.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | string | yes | User id to fetch unread counts for. |
⚠️ 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Channel type, e.g. "messaging". |
| id | string | yes | Channel id. |
| text | string | yes | Message text. |
| user_id | string | yes | Existing user id to send the message as. |
| mentioned_users | array | no | User ids to @mention. |
⚠️ 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Stream or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.11.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestf00dae69d7d62ef442baf075cb02beb0cdea30fccd23ebed5ab1ed4f39e69701
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| stream_get_app | untrusted-input | untrusted-input: keyword "fetch" |
| stream_query_channels | no tags | |
| stream_get_channel | untrusted-input | untrusted-input: keyword "fetch" |
| stream_search_messages | no tags | |
| stream_get_message | untrusted-input | untrusted-input: keyword "fetch" |
| stream_get_replies | untrusted-input | untrusted-input: keyword "fetch" |
| stream_get_reactions | no tags | |
| stream_query_members | no tags | |
| stream_query_users | no tags | |
| stream_query_threads | no tags | |
| stream_get_unread_counts | untrusted-input | untrusted-input: keyword "fetch" |
| stream_send_message | external-sinkstate-write | external-sink: keyword "send_message"; state-write: declares destructiveHint: true |
| stream_send_reaction | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestf00dae69d7d62ef4
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Stream can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.