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.

卡有谱流量卡查询

REMOTE · WWW.KAYOUPU.COM

Search and compare mobile data plans for mainland China, with terms, sources, and source dates.

Available components

+3 this week 81 Trust /100

Last scanned (8 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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 Security80
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 461 tokens (~153/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 58% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

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 5 Nov 2026 · Probed https://www.kayoupu.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.kayoupu.com CN=YR2,O=Let's Encrypt,C=US 24 Sept 2026 23 Dec 2026 RSA 2048 SHA256-RSA 677233a37dcafee96a2f22b9943e53ec84d
SANs: www.kayoupu.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.kayoupu.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
kayoupu.com. 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
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://*.clarity.ms https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://www.kayoupu.com https://www.xuankazn.com https://static.91haoka.cn https://static.haokavip.com https://*.clarity.ms https://c.bing.com https://www.googletagmanager.com https://*.google-analytics.com; font-src 'self'; connect-src 'self' https://*.clarity.ms https://c.bing.com https://www.googletagmanager.com https://*.google-analytics.com https://*.google.com; frame-src 'none'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.kayoupu.com/api/mcp Verified 200
http (plaintext) http://www.kayoupu.com/api/mcp HTTPS enforced 308 https://www.kayoupu.com/api/mcp
MCP tools · 3 exposed · ~369 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
compare_plans ~79

对比两到三款不同 slug 的在售套餐,包括月租、通用及定向流量、通话和已知办理条件。未知项不推断为免费或无限制,不比较信号质量。

NameTypeReqDescription
slugsarrayyes从 search_plans 获取的 2–3 个不同套餐 slug。

No output schema declared.

No examples provided.

get_plan ~61

用 search_plans 返回的 slug 读取在售套餐。保留首充、优惠、合约等已知条款、未知项和渠道资料日期;不提交申请。

NameTypeReqDescription
slugstringyessearch_plans 返回的套餐 slug。

No output schema declared.

No examples provided.

search_plans ~229

按收货省份、运营商、预算、通用流量和通话筛选本站在售套餐,返回条件、资料日期和详情链接。默认按月租升序,不保证可办或全市场最优。

NameTypeReqDescription
limitinteger––
max_monthly_feenumber–标注月租上限,单位元。不是首月或全年总费用。
min_general_data_gbnumber–每月最低通用流量,单位 GB,不含定向流量。
min_voice_minutesnumber––
nationwideboolean–仅查渠道明确标注全国发货的套餐,具体禁发地址仍需确认。
offsetinteger––
operatorstring––
provincestring–收货省份简称,例如广东。只保留渠道明确标注可发的套餐,具体地址仍需确认。
querystring–套餐名称、运营商或发货条件关键词。
sortstring––

No output schema declared.

No examples provided.

Install

How do I install the 卡有谱流量卡查询 MCP server?

卡有谱流量卡查询 is a hosted endpoint at https://www.kayoupu.com/api/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 · www.kayoupu.com

# add to Claude Code
claude mcp add --transport http com-kayoupu-www-plans 'https://www.kayoupu.com/api/mcp'
Common questions

What is the 卡有谱流量卡查询 MCP server?

卡有谱流量卡查询 is an MCP server listed in the public MCP registry as com.kayoupu.www/plans. Search and compare mobile data plans for mainland China, with terms, sources, and source dates. This page covers its hosted endpoint (https://www.kayoupu.com/api/mcp).

Is the 卡有谱流量卡查询 MCP server safe to use?

卡有谱流量卡查询 scores 81 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 卡有谱流量卡查询 MCP server expose?

卡有谱流量卡查询 exposes 3 tools: search_plans, get_plan, compare_plans. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.

Does the 卡有谱流量卡查询 MCP server require authentication?

No. We connected to 卡有谱流量卡查询 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 卡有谱流量卡查询 MCP server still maintained?

卡有谱流量卡查询 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.