Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Clearstream MCP by usefulapi 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
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read lists, subscribers, tags and texts; send texts and change subscribers in Clearstream.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http clearstream-mcp-by-usefulapi https://clearstream.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# clearstream_get_account, clearstream_list_numbers, clearstream_list_lists and 12 more
Clearstream MCP by usefulapi 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 664 servers
usefulapi664 servers
25 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 clearstream-mcp-by-usefulapi https://clearstream.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
15 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.
Get the Clearstream account behind the API key: name, plan and settings. Good first call to confirm which account is connected. Clearstream API: GET /v1/account.
No parameter schema on file.
List the shortcodes and longcodes this account can send texts from, and which one is the default. Clearstream API: GET /v1/numbers.
No parameter schema on file.
List the subscriber lists (groups) in the account, with subscriber counts. Filter by name or locked state. Clearstream API: GET /v1/lists.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Partial match on the list name. |
| locked | string | no | Filter by locked state (default any). |
| limit | integer | no | Results per page (1-100). |
| page | integer | no | Page number (default 1). |
Get one subscriber list: name, subscriber count, active texting subscriber count and sync status. Clearstream API: GET /v1/lists/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | yes | List id (from clearstream_list_lists). |
List the subscribers in one list, with optional name filters. Clearstream API: GET /v1/lists/{id}/subscribers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | yes | List id (from clearstream_list_lists). | |
| full_name | string | no | Partial match on the full name. |
| first | string | no | Partial match on the first name. |
| limit | integer | no | Results per page (1-100). |
| page | integer | no | Page number (default 1). |
Search the account's subscribers by name or mobile number. Clearstream API: GET /v1/subscribers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| full_name | string | no | Partial match on the full name. |
| first | string | no | Partial match on the first name. |
| last | string | no | Partial match on the last name. |
| mobile_number | string | no | Exact match on the mobile number. |
| limit | integer | no | Results per page (default 20). |
| page | integer | no | Page number (default 1). |
Get one subscriber by mobile number: name, opt-in status, lists and tags. Clearstream API: GET /v1/subscribers/{number}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mobile_number | string | yes | Mobile number in E.164 format, for example +12005551000. |
List the subscriber tags in the account. Clearstream API: GET /v1/tags.
No parameter schema on file.
List texts in the account's inbox history, incoming or outgoing, optionally for one number. Use the cursor from a previous reply for the next page. Clearstream API: GET /v1/texts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| direction | string | no | IN for incoming, OUT for outgoing. |
| mobile_number | string | no | Exact match on the contact's mobile number. |
| limit | integer | no | Results per page (1-100). |
| cursor | string | no | Pagination cursor from a previous reply. |
Get text volume statistics for a date range (YYYY-MM-DD, inclusive). Clearstream API: GET /v1/stats/texts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | yes | Start date (YYYY-MM-DD). |
| end | string | yes | End date (YYYY-MM-DD). |
| timezone | string | no | IANA timezone for the statistics (default UTC). |
Send one SMS to one or more numbers. This sends real messages to real phones and cannot be undone. The customer must hold explicit written consent from every recipient before you use this tool (Clearstream terms, section 4G). Opted-out numbers are skipped (for a list of numbers) or cause an error (for one number). Clearstream API: POST /v1/texts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to | yes | One mobile number, or an array of up to 100 numbers. | |
| text_body | string | yes | The message text. Header and body together must fit the character limit. |
| text_header | string | no | Sender name shown before the text, for example the organization name. GSM 7-bit characters only. |
| from | string | no | A sending number from clearstream_list_numbers (default: the account shortcode). |
| use_default_header | boolean | no | Use the account default header instead of text_header. |
| media_url | string | no | Optional JPG or PNG image URL under 5 MB (MMS must be enabled). |
Create or add one subscriber, with optional lists and tags. By default the subscriber must confirm opt-in by text. The customer must hold explicit written consent from every recipient before you use this tool (Clearstream terms, section 4G). Clearstream API: POST /v1/subscribers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mobile_number | string | yes | Mobile number, preferably E.164 format, for example +12005551000. |
| first | string | no | First name. |
| last | string | no | Last name. |
| string | no | Email address. | |
| lists | array | no | List ids to add the subscriber to. |
| tags | array | no | Tag ids to add to the subscriber. |
| double_optin | boolean | no | Send a confirmation text before opt-in (default true). |
Add one mobile number to a subscriber list. Locked lists cannot change. The customer must hold explicit written consent from every recipient before you use this tool (Clearstream terms, section 4G). Clearstream API: POST /v1/lists/{id}/subscribers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | yes | List id (from clearstream_list_lists). | |
| mobile_number | string | yes | Mobile number, preferably E.164 format, for example +12005551000. |
Remove one mobile number from a subscriber list. The subscriber's opt-in status does not change. Locked lists cannot change. Clearstream API: DELETE /v1/lists/{id}/subscribers/{number}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | yes | List id (from clearstream_list_lists). | |
| mobile_number | string | yes | Mobile number in E.164 format, for example +12005551000. |
Add a tag to up to 100 subscribers by mobile number. The customer must hold explicit written consent from every recipient before you use this tool (Clearstream terms, section 4G). Clearstream API: POST /v1/tags/{id}/subscribers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tag_id | yes | Tag id (from clearstream_list_tags). | |
| mobile_numbers | array | yes | Mobile numbers in E.164 format (1-100 per call). |
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 Clearstream MCP by usefulapi 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.0.2 · scanned 8 Nov 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 digeste8b08fc1bd6c1d0dadaad633359d3e7c05d17a78819b4f9ac514f31816dd2ec8
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 |
|---|---|---|
| clearstream_get_account | no tags | |
| clearstream_list_numbers | no tags | |
| clearstream_list_lists | no tags | |
| clearstream_get_list | no tags | |
| clearstream_list_subscribers_of_list | no tags | |
| clearstream_list_subscribers | no tags | |
| clearstream_get_subscriber | no tags | |
| clearstream_list_tags | no tags | |
| clearstream_list_texts | no tags | |
| clearstream_get_text_stats | no tags | |
| clearstream_send_text | external-sinkstate-write | external-sink: keyword "sms"; state-write: declares readOnlyHint: false, destructiveHint: true |
| clearstream_add_subscriber | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| clearstream_add_subscriber_to_list | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| clearstream_remove_subscriber_from_list | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| clearstream_tag_subscribers | state-write | state-write: declares readOnlyHint: false, 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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digeste8b08fc1bd6c1d0d
Scanned2026-11-08
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.0.2.
1.0.2
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 Clearstream MCP by usefulapi 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.