Manto — 馒头新闻
REMOTE · MANTO.XIN
Publish, search, and promote time-sensitive news and messages through a public remote MCP server.
Available components
Last scanned (2 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category News and Social
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 342 tokens (~34/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 3 Oct 26 74
- Stability: fail → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Sept 26 0
- Tool “create_account” rewrote its description, which is the text the model reads security
- Tool “create_recharge” rewrote its description, which is the text the model reads security
- Tool “get_account” rewrote its description, which is the text the model reads security
- Tool “remove_content” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Tool “set_promotion” rewrote its description, which is the text the model reads security
- 9 Sept 26 0
- Server version: 1.0.6 → 1.1.0 functional
- 3 Sept 26 0
- Stability: unverified → fail ▼ security
- Tool “create_recharge” rewrote its description, which is the text the model reads security
- “create_recharge” added a required parameter “email”, so existing callers break ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.6 functional
- 2 Sept 26 0
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://manto.xin/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=manto.xin | CN=YE1,O=Let's Encrypt,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6d84ef19ed0b19f47081bdc9b0ccf9c8821 |
| SANs: manto.xin | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of manto.xin. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xin. | present | 2809 | 8 | Verified |
| manto.xin. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://manto.xin/mcp | Verified | 200 | |
| http (plaintext) | http://manto.xin/mcp | HTTPS enforced | 301 | https://manto.xin/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 →
create_account ~29
Create a passwordless Manto account and receive an API key once
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
No output schema declared.
No examples provided.
create_recharge ~35
Create a recharge order for an existing account email
| Name | Type | Req | Description |
|---|---|---|---|
| amount_cents | number | yes | – |
| string | yes | – |
No output schema declared.
No examples provided.
get_account ~20
Get account quota, balance, account score and recent content
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_recharge ~21
Get recharge status
| Name | Type | Req | Description |
|---|---|---|---|
| recharge_id | string | yes | – |
No output schema declared.
No examples provided.
list_account_articles ~44
List an account's published articles; no API key required
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
| include_content | boolean | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
lookup_account ~28
Look up a public account by email; no API key required
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
No output schema declared.
No examples provided.
publish ~52
Create or idempotently update content
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| expires_at | string | – | – |
| external_id | string | – | – |
| title | string | yes | – |
| url | string | – | – |
No output schema declared.
No examples provided.
remove_content ~24
Remove content owned by the authenticated account
| Name | Type | Req | Description |
|---|---|---|---|
| content_id | string | yes | – |
No output schema declared.
No examples provided.
search ~50
Search published news and messages; sponsored and organic results are returned separately
| Name | Type | Req | Description |
|---|---|---|---|
| include_content | boolean | – | – |
| limit | number | – | – |
| query | string | yes | – |
| since | string | – | – |
No output schema declared.
No examples provided.
set_promotion ~39
Set a daily promotion budget in cents; zero pauses promotion
| Name | Type | Req | Description |
|---|---|---|---|
| content_id | string | yes | – |
| daily_budget_cents | number | yes | – |
No output schema declared.
No examples provided.
How do I install the Manto — 馒头新闻 MCP server?
Manto — 馒头新闻 is a hosted endpoint at https://manto.xin/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 · manto.xin
claude mcp add --transport http tans-manto 'https://manto.xin/mcp'
What is the Manto — 馒头新闻 MCP server?
Manto — 馒头新闻 is an MCP server listed in the public MCP registry as io.github.tans/manto. Publish, search, and promote time-sensitive news and messages through a public remote MCP server. This page covers its hosted endpoint (https://manto.xin/mcp).
Is the Manto — 馒头新闻 MCP server safe to use?
Manto — 馒头新闻 scores 74 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 Manto — 馒头新闻 MCP server expose?
Manto — 馒头新闻 exposes 10 tools: create_account, lookup_account, list_account_articles, search, create_recharge, and 5 more. Their descriptions and schemas cost roughly 342 tokens of context every time the server is loaded.
Does the Manto — 馒头新闻 MCP server require authentication?
No. We connected to Manto — 馒头新闻 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Manto — 馒头新闻 MCP server still maintained?
Manto — 馒头新闻 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.