NewsMAN MCP by usefulapi
REMOTE · NEWSMAN.USEFULAPI.IO
Read NewsMAN lists, subscribers, segments, newsletter and automation stats; manage subscribers.
Available components
Last scanned (2 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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.
- 2 Nov 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.20 → 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_automation_performance” functional
- New prompt “compare_newsletter_results” functional
- New prompt “handle_an_unsubscribe_request” functional
- New prompt “look_up_a_subscriber” functional
- New prompt “subscribe_and_tag_a_person_who_gave_consent” functional
- New prompt “track_list_growth” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.7.0 → 1.9.0 functional
- Server version: 1.6.0 → 1.7.0 functional
- Server version: 1.5.2 → 1.6.0 functional
- 30 Oct 26 +1
- Server version: 1.5.1 → 1.5.2 functional
- Server version: 1.5.0 → 1.5.1 functional
- 29 Oct 26 0
- Server version: 1.4.0 → 1.5.0 functional
- Server version: 1.3.0 → 1.4.0 functional
- 28 Oct 26 +1
- Server version: 1.1.0 → 1.3.0 functional
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- 26 Oct 26 63
First indexed and scored.
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://newsman.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 newsman.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://newsman.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/newsman/ |
| http (plaintext) | http://newsman.usefulapi.io/mcp | Inconclusive | 302 | http://newsman.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 →
newsman_add_subscriber_tags Add tags to a subscriber ~53
WRITE: add tags to a subscriber (existing tags stay). POST /v2/subscriber/addTags.
| Name | Type | Req | Description |
|---|---|---|---|
| subscriber_id | – | yes | NewsMAN subscriber id. |
| tags | array | yes | Tags to add. |
No output schema declared.
No examples provided.
newsman_add_subscriber_to_segment Add a subscriber to a segment ~55
WRITE: add a subscriber to a (static) segment. POST /v2/subscriber/addToSegment.
| Name | Type | Req | Description |
|---|---|---|---|
| segment_id | – | yes | NewsMAN segment id. |
| subscriber_id | – | yes | NewsMAN subscriber id. |
No output schema declared.
No examples provided.
newsman_count_list_subscribers Count list subscribers ~42
The number of active (subscribed) subscribers of a list. GET /v2/list/count.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | – | yes | NewsMAN list id. |
No output schema declared.
No examples provided.
newsman_count_segment_subscribers Count segment subscribers ~45
The number of active subscribers in a segment. GET /v2/segment/count.
| Name | Type | Req | Description |
|---|---|---|---|
| segment_id | – | yes | NewsMAN segment id (from newsman_list_segments). |
No output schema declared.
No examples provided.
newsman_get_automation Get automation ~57
One automation workflow: name, type, status, version, recurrence, stats and preview links. GET /v2/automation/getWorkflow.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | – | yes | NewsMAN workflow id (from newsman_list_automations). |
No output schema declared.
No examples provided.
newsman_get_automation_stats Get automation stats ~172
Daily stats of the automations of a list: sends, opens, clicks, purchases, bounces, unsubscribes. Optionally for given workflows and a period (last N days, or start_date/stop_date; at most 90 days). GET /v2/automation/stats.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | The last N days, 1-90 (alternative to start_date/stop_date; NewsMAN allows at most 90 days). |
| list_id | – | yes | NewsMAN list id. |
| start_date | string | – | Start of the period, UTC, YYYY-MM-DD. |
| stop_date | string | – | End of the period, UTC, YYYY-MM-DD. |
| workflow_ids | string | – | Comma-separated workflow ids (default: all workflows of the list). |
No output schema declared.
No examples provided.
newsman_get_import_status Get import status ~53
Status of a background subscriber import by import_id: new, running, finished or error, with times and the last error. GET /v2/import/status.
| Name | Type | Req | Description |
|---|---|---|---|
| import_id | – | yes | NewsMAN import id. |
No output schema declared.
No examples provided.
newsman_get_list Get list properties ~63
Properties of one list: sender name and email, owner contact details, site, link parameters, send rate. The list secret is never returned. GET /v2/list/getProps.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | – | yes | NewsMAN list id (from newsman_list_lists). |
No output schema declared.
No examples provided.
newsman_get_list_growth Get list growth ~148
Daily evolution of a list: total and eligible subscribers, unsubscribes, spam reports and hard bounces per day. Give `days` (last N days) OR start_date/stop_date; the period is at most 90 days. GET /v2/list/subscribersEvolution.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | The last N days, 1-90 (alternative to start_date/stop_date; NewsMAN allows at most 90 days). |
| list_id | – | yes | NewsMAN list id. |
| start_date | string | – | Start of the period, UTC, YYYY-MM-DD. |
| stop_date | string | – | End of the period, UTC, YYYY-MM-DD. |
No output schema declared.
No examples provided.
newsman_get_newsletter Get newsletter ~63
Properties of one newsletter: subject, sender, status, dates, segments, links to the online view. Long HTML is clipped. GET /v2/newsletter/getProps.
| Name | Type | Req | Description |
|---|---|---|---|
| newsletter_id | – | yes | NewsMAN newsletter id (from newsman_list_newsletters). |
No output schema declared.
No examples provided.
newsman_get_newsletter_clicked_links Get newsletter clicked links ~50
The links clicked in one newsletter with the number of clicks and the last click time. GET /v2/newsletter/linksClicked.
| Name | Type | Req | Description |
|---|---|---|---|
| newsletter_id | – | yes | NewsMAN newsletter id. |
No output schema declared.
No examples provided.
newsman_get_newsletter_stats Get newsletter stats ~57
Delivery and engagement stats of one newsletter: sent, views, clicks, unsubscribes, bounces, spam reports and rates. GET /v2/newsletter/stats.
| Name | Type | Req | Description |
|---|---|---|---|
| newsletter_id | – | yes | NewsMAN newsletter id. |
No output schema declared.
No examples provided.
newsman_get_subscriber Get subscriber by email ~62
One subscriber of a list by email address: status and dates, name, IP, custom properties and segments. GET /v2/subscriber/getByEmail.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address. | |
| list_id | – | yes | NewsMAN list id. |
No output schema declared.
No examples provided.
newsman_get_subscriber_by_id Get subscriber by id ~50
One subscriber by subscriber_id: status and dates, name, IP, custom properties and segments. GET /v2/subscriber/get.
| Name | Type | Req | Description |
|---|---|---|---|
| subscriber_id | – | yes | NewsMAN subscriber id. |
No output schema declared.
No examples provided.
newsman_get_subscriber_history Get subscriber history ~64
The last 100 actions of a subscriber: subscribe, unsubscribe, send, view, click, bounce, spam, each with a date and metadata (newsletter, link). GET /v2/subscriber/history.
| Name | Type | Req | Description |
|---|---|---|---|
| subscriber_id | – | yes | NewsMAN subscriber id. |
No output schema declared.
No examples provided.
newsman_list_automations List automations ~203
Automation workflows of a list with workflow_id, name, type, status (0 inactive, 1 active), version and stats. Filter by name, status and last-updated range. GET /v2/automation/all.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | – | yes | NewsMAN list id. |
| name | string | – | Workflow name filter (default: any). |
| start_date | string | – | Updated on or after, UTC, YYYY-MM-DD or YYYY-MM-DD HH:mm:ss. |
| status | string | – | all (default), 0 inactive or 1 active. |
| stop_date | string | – | Updated on or before, UTC, YYYY-MM-DD or YYYY-MM-DD HH:mm:ss. |
| type | string | – | Workflow type: all (default), sub_date, newsletter_view, newsletter_click, advanced, unsub, manual, ecommerce_cart_update, ecommerce_order_completed, ecommerce_product_view, segment_add, segment_remo… |
No output schema declared.
No examples provided.
newsman_list_lists List subscriber lists ~52
All email lists (and SMS lists) this key can access, each with list_id, list_name and list_type. Start here: most other tools need a list_id. GET /v2/list/all.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
newsman_list_newsletters List newsletters ~244
Newsletters (campaigns) of a list with newsletter_id, subject, status, dates, segments and headline stats. Filter by status (-1 cancelled, 0 new, 1 confirmed, 2 sending, 3 paused, 4 resumed, 5 sent; or a comma list such as 1,5; default all), by creation date range, or the last N days. Paged. GET /v2/newsletter/all.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Created in the last N days (alternative to start_date/stop_date). |
| limit | integer | – | Results per page, 1-1000 (default 100). |
| list_id | – | yes | NewsMAN list id. |
| page | integer | – | Page number, starting at 0 (default 0). |
| start_date | string | – | Created on or after, UTC, YYYY-MM-DD or YYYY-MM-DD HH:mm:ss. |
| status | string | – | Newsletter status: all, -1..5 or a comma list (default all). |
| stop_date | string | – | Created on or before, UTC, YYYY-MM-DD or YYYY-MM-DD HH:mm:ss. |
No output schema declared.
No examples provided.
newsman_list_segment_subscribers List segment subscribers ~96
The subscribers of a segment (subscriber_id and email). Paged (page from 0, up to 1000 per page). GET /v2/segment/getSubscribers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-1000 (default 100). |
| page | integer | – | Page number, starting at 0 (default 0). |
| segment_id | – | yes | NewsMAN segment id. |
No output schema declared.
No examples provided.
newsman_list_segments List segments ~73
The segments of a list with segment_id, segment_name, subscriber count and status (0 idle, 1 import running, 2 counting, 3 searching). NewsMAN allows 20 calls a minute for this method. GET /v2/segment/all.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | – | yes | NewsMAN list id. |
No output schema declared.
No examples provided.
newsman_list_subscribers List subscribers by status ~167
Subscribers of a list with a given status (subscribed, unsubscribed, bounced, spam, inactivated), optionally only those who joined since a UTC date. Each item has subscriber_id, email and the date of that status. Paged (page from 0, up to 1000 per page). GET /v2/list/getSubscribers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-1000 (default 100). |
| list_id | – | yes | NewsMAN list id. |
| page | integer | – | Page number, starting at 0 (default 0). |
| since | string | – | Only subscribers who joined on or after this moment, UTC, YYYY-MM-DD or YYYY-MM-DD HH:mm:ss. |
| status | string | yes | Subscriber status. |
No output schema declared.
No examples provided.
newsman_remove_subscriber_from_segment Remove a subscriber from a segment ~59
WRITE: remove a subscriber from a segment (the subscriber stays on the list). POST /v2/subscriber/removeFromSegment.
| Name | Type | Req | Description |
|---|---|---|---|
| segment_id | – | yes | NewsMAN segment id. |
| subscriber_id | – | yes | NewsMAN subscriber id. |
No output schema declared.
No examples provided.
newsman_search_subscribers Search subscribers ~169
Search the subscribers of a list by keywords (email or name) and status, optionally only those who joined since a UTC date. Paged (page from 0, up to 1000 per page). GET /v2/subscriber/search.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | string | yes | Text to search for, for example part of an email address. |
| limit | integer | – | Results per page, 1-1000 (default 100). |
| list_id | – | yes | NewsMAN list id. |
| page | integer | – | Page number, starting at 0 (default 0). |
| since | string | – | Only subscribers who joined on or after this moment, UTC, YYYY-MM-DD or YYYY-MM-DD HH:mm:ss. |
| status | string | – | Subscriber status (default subscribed). |
No output schema declared.
No examples provided.
newsman_subscribe_email Subscribe an email ~176
WRITE: subscribe an email address to a list (or update it if it exists), with optional name and custom properties. A property key with the tag_ prefix sets a tag. Only use for people who gave consent. The subscriber is active at once, with no confirmation email. Returns the subscriber_id. POST /v2/subscriber/saveSubscribe.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address. | |
| firstname | string | – | First name. |
| ip | string | – | IP address to record for this action (NewsMAN requires one). Defaults to 0.0.0.0 when omitted. |
| lastname | string | – | Last name. |
| list_id | – | yes | NewsMAN list id. |
| props | object | – | Custom properties, for example {"city": "Paris", "tag_vip": "1"}. |
No output schema declared.
No examples provided.
newsman_unsubscribe_email Unsubscribe an email ~97
WRITE: unsubscribe an email address from a list, so it no longer receives campaigns from that list. Returns the subscriber_id. POST /v2/subscriber/saveUnsubscribe.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address. | |
| ip | string | – | IP address to record for this action (NewsMAN requires one). Defaults to 0.0.0.0 when omitted. |
| list_id | – | yes | NewsMAN list id. |
No output schema declared.
No examples provided.
newsman_update_subscriber Update a subscriber ~89
WRITE: change the email, first name or last name of a subscriber. Give only the fields to change; the others are left as they are. POST /v2/subscriber/update.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | New email address. | |
| firstname | string | – | New first name. |
| lastname | string | – | New last name. |
| subscriber_id | – | yes | NewsMAN subscriber id. |
No output schema declared.
No examples provided.
How do I install the NewsMAN MCP by usefulapi server?
NewsMAN MCP by usefulapi is a hosted endpoint at https://newsman.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 · newsman.usefulapi.io
claude mcp add --transport http io-usefulapi-newsman 'https://newsman.usefulapi.io/mcp'
What is the NewsMAN MCP by usefulapi server?
NewsMAN MCP by usefulapi is listed in the public MCP registry as io.usefulapi/newsman. Read NewsMAN lists, subscribers, segments, newsletter and automation stats; manage subscribers. This page covers its hosted endpoint (https://newsman.usefulapi.io/mcp).
Is the NewsMAN MCP by usefulapi server safe to use?
NewsMAN 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 NewsMAN MCP by usefulapi server expose?
NewsMAN MCP by usefulapi exposes 26 tools: newsman_list_lists, newsman_get_list, newsman_count_list_subscribers, newsman_list_subscribers, newsman_get_list_growth, and 21 more. Their descriptions and schemas cost roughly 2,459 tokens of context every time the server is loaded.
Does the NewsMAN MCP by usefulapi server require authentication?
Its publisher declares no required credentials for NewsMAN 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 NewsMAN MCP by usefulapi server still maintained?
NewsMAN 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 NewsMAN MCP by usefulapi server?
VerifyMCP ran 4 checks on NewsMAN 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 NewsMAN 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.