io.github.xnjiang/autowhisper-mcp
REMOTE · AUTOWHISPER.XYZ · 2 COMPONENTS · SCANNED OCT 8
Drive your AutoWhisper AI CMO to generate and publish marketing content from any MCP client.
Available components
Recent critical change
Authorization (3 Oct 2026). See the changelog before you install this server.
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the io.github.xnjiang/autowhisper-mcp server?
io.github.xnjiang/autowhisper-mcp is a hosted endpoint at https://autowhisper.xyz/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 · autowhisper.xyz
claude mcp add --transport http xnjiang-autowhisper-mcp 'https://autowhisper.xyz/mcp'
{
"mcpServers": {
"xnjiang-autowhisper-mcp": {
"url": "https://autowhisper.xyz/mcp"
}
}
} {
"servers": {
"xnjiang-autowhisper-mcp": {
"type": "http",
"url": "https://autowhisper.xyz/mcp"
}
}
} [mcp_servers.xnjiang-autowhisper-mcp] url = "https://autowhisper.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xnjiang-autowhisper-mcp": {
"type": "remote",
"url": "https://autowhisper.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xnjiang-autowhisper-mcp --url 'https://autowhisper.xyz/mcp' --transport streamable-http
mcp_servers:
xnjiang-autowhisper-mcp:
url: "https://autowhisper.xyz/mcp" {
"McpServers": {
"xnjiang-autowhisper-mcp": {
"Transport": "http",
"Url": "https://autowhisper.xyz/mcp"
}
}
} assistant mcp add xnjiang-autowhisper-mcp -t streamable-http -u 'https://autowhisper.xyz/mcp'
{
"mcpServers": {
"xnjiang-autowhisper-mcp": {
"type": "http",
"url": "https://autowhisper.xyz/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.
- 7 Oct 26 −30
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 Oct 26 +2
- Authorization: unverified → fail ▼ critical
- Tool “autowhisper_edit_content” is now declared destructive security
- Tool “autowhisper_action” is now declared destructive security
- Tool “autowhisper_confirm” is now declared destructive security
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- 2 Oct 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.
- 30 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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 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 8 Oct 2026 · Probed https://autowhisper.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=autowhisper.xyz | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 69684b7b63d4d74a13cf36140c0f5bfc |
| SANs: autowhisper.xyz | ||||||
| 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 autowhisper.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| autowhisper.xyz. | 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 connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="autowhisper", resource_metadata="https://autowhisper.xyz/.well-known/oauth-protected-resource"
Bearer realm="autowhisper", resource_metadata="https://autowhisper.xyz/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| www-authenticate | Bearer realm="autowhisper", resource_metadata="https://autowhisper.xyz/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://autowhisper.xyz/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://autowhisper.xyz/mcp |
| Authorisation server | https://autowhisper.xyz/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://autowhisper.xyz/mcp | Auth required | 401 | |
| http (plaintext) | http://autowhisper.xyz/mcp | HTTPS enforced | 301 | https://autowhisper.xyz/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 →
autowhisper_action ~404
Run an explicit feed or post action without an AI chat turn. High-impact actions return a confirmation message_id; confirm it with autowhisper_confirm. approve_feed_item PUBLISHES: it schedules the piece to every connected platform, and for a video draft it also starts the render and charges credits for it — approving is the spend, not a bookmark. When nothing is connected it schedules nothing, and connecting a platform later does NOT go back for it; the result line says which happened. regenerate_content rewrites an existing draft IN PLACE (same record id, new text) — it takes content_type + content_id, not feed_item_id, and always returns a confirmation because it spends credits.
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| content_id | number | – | Required for regenerate_content. The id from the row's `content: <type> #<id>` — NOT feed_item_id. |
| content_type | string | – | Required for regenerate_content. The snake_case value from the row's `content: <type> #<id>` — NOT the class name. |
| feed_item_id | number | – | Required for feed actions. The leading `feed_item #<id>` in an autowhisper_feed row — NOT the `content: <type> #<id>` on the same row. |
| post_id | number | – | Required for post actions. |
| reason | string | – | Optional reason for rejecting a feed item. |
| scheduled_at | string | – | Required for reschedule_post; ISO8601 or natural language supported by AutoWhisper. |
| tool | string | yes | – |
| workspace_id | number | – | Workspace to act in. Omit for the user's CURRENT workspace. The target item must live in that workspace — an id from another workspace will not be found. |
No output schema declared.
No examples provided.
autowhisper_cmo ~333
Send a natural-language instruction to your AutoWhisper AI CMO and get its reply. Best at: (1) generating batches of on-brand ad creatives (UGC video, posts, images) for paid campaigns, (2) advising which creative to fund and how to target, (3) keeping every social channel alive across 30+ networks, plus analytics. Examples: "Make a batch of ad creatives for my product https://mystore.com/widget", "Which creative should I run first, and how should I target?", "Keep my channels posted this week". Honest scope: posting ≠ traffic — reach comes from the user's paid ads. To add a product, pass a product URL (the CMO extracts the image from the page) — a text-only description will not create it, and placeholder/stock images are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| instruction | string | yes | What you want the CMO to do, in natural language. |
| product_id | string | – | Optional: act on a specific product by its id. |
| workspace_id | number | – | Workspace to act in. Omitting it uses the account's FIRST active workspace, which may not be the one you were just reading — and the workspace decides the generated content's LANGUAGE. Pass the works… |
No output schema declared.
No examples provided.
autowhisper_confirm ~174
Approve or decline a high-impact action the CMO or autowhisper_action asked you to confirm. Pass the message_id it gave you and decision "yes" or "no".
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| decision | string | yes | "yes" to perform the action, "no" to decline. |
| message_id | number | yes | The message_id from the confirmation request. |
| workspace_id | number | – | The workspace the confirmation lives in — pass the SAME one you used for autowhisper_cmo. Omitting it falls back to the account's first active workspace and 404s on a bubble that lives anywhere else. |
No output schema declared.
No examples provided.
autowhisper_edit_content ~267
Directly update exact content fields without a generation run or credit spend. Pass body for the full replacement copy/story. IDs: content_id is the CONTENT id — in autowhisper_feed output that is the `content: <type> #<id>` part of a row, NOT the leading `feed_item #<id>` (that one belongs to autowhisper_action).
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| body | string | – | – |
| content_id | number | yes | The CONTENT id from the feed row's `content: <type> #<id>` — not the feed_item id. |
| content_type | string | yes | Content type in snake_case, as printed in the feed row's `content:` part. |
| cta | string | – | – |
| hook | string | – | – |
| keywords | array | – | – |
| title | string | – | – |
| tone | string | – | – |
| workspace_id | number | – | Workspace to act in. Omit for the user's CURRENT workspace. The target item must live in that workspace — an id from another workspace will not be found. |
No output schema declared.
No examples provided.
autowhisper_feed ~173
Fast CMO feed list with status counts and the actions available on each row (with their arguments). Each row prints BOTH ids: `feed_item #<id>` addresses the review card (autowhisper_action) while `content: <type> #<id>` addresses the content itself (autowhisper_edit_content).
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| status | string | – | Filter by feed status (pending / approved / rejected / executed / all). |
| workspace_id | number | – | Workspace to read. Omit for the user's CURRENT workspace — other workspaces are NOT included. Get other ids from autowhisper_status. |
No output schema declared.
No examples provided.
autowhisper_performance ~218
Read-only cross-channel results for ONE workspace: a four-layer funnel, a per-channel breakdown, and ad spend over the window. Use this to answer how published content is actually doing, and before advising which creative to fund or scale — autowhisper_feed and autowhisper_posts only say what was made and sent, never whether it worked. ad_spend_cents is null (not 0) when the account has no active workspace: null means we cannot answer, 0 would assert nothing was spent.
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| window_days | number | – | Look-back window in days. The server clamps it to its own supported range and defaults when omitted. |
| workspace_id | number | – | Workspace to read. Omit for the user's CURRENT workspace — other workspaces are NOT included. Get other ids from autowhisper_status. |
No output schema declared.
No examples provided.
autowhisper_platforms ~97
Fast connected-platform list and connection health for ONE workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| workspace_id | number | – | Workspace to read. Omit for the user's CURRENT workspace — other workspaces are NOT included. Get other ids from autowhisper_status. |
No output schema declared.
No examples provided.
autowhisper_posts ~130
Fast post queue list, optionally filtered by status. Failed rows carry the reason and whether a retry can help (needs reconnect means a human must re-authorise that channel).
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| status | string | – | Filter by post status. |
| workspace_id | number | – | Workspace to read. Omit for the user's CURRENT workspace — other workspaces are NOT included. Get other ids from autowhisper_status. |
No output schema declared.
No examples provided.
autowhisper_products ~152
Fast product list with optional workspace/archive filters. Each row carries the product id used by autowhisper_cmo, its type, whether it has a main image, and its storefront link.
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| include_archived | boolean | – | Include archived products. |
| limit | number | – | Maximum products to return, capped by the API. |
| workspace_id | number | – | Workspace to read. Omit for the user's CURRENT workspace — other workspaces are NOT included. Get other ids from autowhisper_status. |
No output schema declared.
No examples provided.
autowhisper_products_summary ~121
Fast product counts by account/workspace. Use this for "how many products do I have?" instead of spending a CMO chat turn. Counts by workspace come with it.
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| workspace_id | number | – | Workspace to read. Omit for the user's CURRENT workspace — other workspaces are NOT included. Get other ids from autowhisper_status. |
No output schema declared.
No examples provided.
autowhisper_status ~142
Fast CMO/account snapshot for the current workspace: products, feed, platforms, wallet, settings — plus the directory of workspaces (with ids) to pass as workspace_id. Every count is for the CURRENT workspace; account-wide product counts are in autowhisper_products_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
| workspace_id | number | – | Workspace to read. Omit for the user's CURRENT workspace — other workspaces are NOT included. Get other ids from autowhisper_status. |
No output schema declared.
No examples provided.
autowhisper_wallet ~56
Fast credit balance for the account.
| Name | Type | Req | Description |
|---|---|---|---|
| autowhisper_token | string | – | Optional: your AutoWhisper API token, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back. |
No output schema declared.
No examples provided.
What is the io.github.xnjiang/autowhisper-mcp server?
io.github.xnjiang/autowhisper-mcp is listed in the public MCP registry as io.github.xnjiang/autowhisper-mcp. Drive your AutoWhisper AI CMO to generate and publish marketing content from any MCP client. This page covers its hosted endpoint (https://autowhisper.xyz/mcp).
Is the io.github.xnjiang/autowhisper-mcp server safe to use?
io.github.xnjiang/autowhisper-mcp scores 38 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.github.xnjiang/autowhisper-mcp server expose?
io.github.xnjiang/autowhisper-mcp exposes 12 tools: autowhisper_products_summary, autowhisper_products, autowhisper_status, autowhisper_feed, autowhisper_posts, and 7 more. Their descriptions and schemas cost roughly 2,267 tokens of context every time the server is loaded.
Does the io.github.xnjiang/autowhisper-mcp server require authentication?
Yes. io.github.xnjiang/autowhisper-mcp 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.github.xnjiang/autowhisper-mcp server still maintained?
io.github.xnjiang/autowhisper-mcp is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.