Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Manto — 馒头新闻

REMOTE · MANTO.XIN · SCANNED SEP 20

Publish, search, and promote time-sensitive news and messages through a public remote MCP server.

Available components

+3 this week 67 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
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 Management55
  • Stability check failed: schema churn in the 18 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
Install

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

# add to Claude Code
claude mcp add --transport http tans-manto 'https://manto.xin/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "tans-manto": {
      "url": "https://manto.xin/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "tans-manto": {
      "type": "http",
      "url": "https://manto.xin/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.tans-manto]
url = "https://manto.xin/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tans-manto": {
      "type": "remote",
      "url": "https://manto.xin/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add tans-manto --url 'https://manto.xin/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  tans-manto:
    url: "https://manto.xin/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "tans-manto": {
      "Transport": "http",
      "Url": "https://manto.xin/mcp"
    }
  }
}
# add to Vellum
assistant mcp add tans-manto -t streamable-http -u 'https://manto.xin/mcp'
// mcp.json
{
  "mcpServers": {
    "tans-manto": {
      "type": "http",
      "url": "https://manto.xin/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 48 to 52.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 42 to 45.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 35 to 38.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 28 to 32.

  • 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
  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 18 to 22.

  • 9 Sept 26 0
    • Server version: 1.0.6 → 1.1.0 functional
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 12 to 15.

Diagnostics

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 20 Sept 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
MCP tools · 10 exposed · ~342 tokens

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 →

Tool Tokens
create_account ~29

Create a passwordless Manto account and receive an API key once

NameTypeReqDescription
emailstringyes

No output schema declared.

No examples provided.

create_recharge ~35

Create a recharge order for an existing account email

NameTypeReqDescription
amount_centsnumberyes
emailstringyes

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

NameTypeReqDescription
recharge_idstringyes

No output schema declared.

No examples provided.

list_account_articles ~44

List an account's published articles; no API key required

NameTypeReqDescription
account_idstringyes
include_contentboolean
limitnumber

No output schema declared.

No examples provided.

lookup_account ~28

Look up a public account by email; no API key required

NameTypeReqDescription
emailstringyes

No output schema declared.

No examples provided.

publish ~52

Create or idempotently update content

NameTypeReqDescription
contentstringyes
expires_atstring
external_idstring
titlestringyes
urlstring

No output schema declared.

No examples provided.

remove_content ~24

Remove content owned by the authenticated account

NameTypeReqDescription
content_idstringyes

No output schema declared.

No examples provided.

search ~50

Search published news and messages; sponsored and organic results are returned separately

NameTypeReqDescription
include_contentboolean
limitnumber
querystringyes
sincestring

No output schema declared.

No examples provided.

set_promotion ~39

Set a daily promotion budget in cents; zero pauses promotion

NameTypeReqDescription
content_idstringyes
daily_budget_centsnumberyes

No output schema declared.

No examples provided.

Common questions

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 67 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.