cn.pianam/mycel-mcp
REMOTE · SITE.PIANAM.CN
Mycel unified MCP gateway: China realtime data and 20 tool modules. API key required.
Available components
Last scanned (18 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1940 tokens (~138/item across 14 items; 14 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 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.
- 13 Nov 26 0
- New tool “mycel_usage” functional
- 12 Nov 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.
- 10 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 70
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 21 Nov 2026 · Probed https://site.pianam.cn/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=admin.pianam.cn | CN=YR2,O=Let's Encrypt,C=US | 11 Nov 2026 | 9 Feb 2027 | RSA 2048 | SHA256-RSA | 55abad153a98540cc6719a7c8a08b9373dd |
| SANs: admin.pianam.cn, site.pianam.cn, trade.pianam.cn | ||||||
| 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 site.pianam.cn. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| cn. | DS published | 33094 | 8 | Verified |
| pianam.cn. | No DS | 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; includeSubDomains |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://site.pianam.cn/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://site.pianam.cn/api/v1/mcp | HTTPS enforced | 301 | https://site.pianam.cn/api/v1/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 →
exchange_rate Real-time currency exchange rate ~133
Live currency exchange rates and amount conversion. Base/target currency codes or Chinese names; leave target empty for a basket of common currencies. Source: Frankfurter (ECB reference rates), updated daily. Free, no API key required. |查询实时汇率并换算金额。数据来自欧洲央行参考汇率,每日更新。免费无需 Key。
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Amount to convert, optional | 换算金额 |
| base | string | – | Base currency, default USD | 基准货币 |
| target | string | – | Target currency, empty = common basket | 目标货币 |
No output schema declared.
No examples provided.
hot_trending Live trending topics (CN platforms) ~164
Live trending/hot lists from Chinese platforms: weibo, zhihu, bilibili, baidu, toutiao, douyin, tieba, juejin, or all. Real-time, cached 5 minutes. Free, no API key required. |查询国内各平台实时热搜/热榜(微博/知乎/B站/百度/头条/抖音/贴吧/掘金)。实时数据,缓存 5 分钟,免费无需 Key。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items per platform 1-50, default 20 | 条数 |
| platform | string | – | weibo/zhihu/bilibili/baidu/toutiao/douyin/tieba/juejin/all, default all | 平台 |
No output schema declared.
No examples provided.
ip_lookup IP geolocation and ASN ~115
Look up the geolocation and network operator of an IPv4 address: country, region, city, coordinates, timezone, ISP, ASN. Live lookup via ip-api.com. Free, no API key required. |查询 IPv4 地址的归属地与运营商(国家/省份/城市、经纬度、时区、ISP、AS 编号)。实时查询,免费无需 Key。
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | – | IPv4 address; empty = caller IP | IP 地址,留空取调用方 IP |
No output schema declared.
No examples provided.
mycel_balance Check credit balance ~43
Check the credit balance of the account that owns the API key. Does not consume credits. |查询当前 API Key 对应账户的积分余额,不消耗积分。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mycel_discover Discover hireable agents ~87
List the AI agent nodes currently available for hire on the Mycel network (returns agentId, name and capability description). Free, no API key required — call this before hiring to see who is available. |发现 Mycel 菌丝网络当前可雇佣的智能体节点(返回 agentId、名称、能力描述)。不消耗积分、无需 API Key。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mycel_hire_agent Hire an agent to run a task ~181
Hire a Mycel agent to execute a task and get the result back (charges credits per platform rules). Get agent_id from mycel_discover first, then pass a natural-language prompt. Returns the task output, or a task_id you can poll with mycel_task_status. Requires an API key; an agent can self-register for a free trial credit via POST https://pianam.cn/api/v1/agent/register. |雇佣一个 Mycel 平台智能体执行任务(按平台规则扣积分)。先用 mycel_discover 拿到 agentId,再传 prompt 描述任务。
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | yes | Target agent ID returned by mycel_discover | 目标智能体 ID |
| prompt | string | yes | Full task description for the agent | 交给智能体的完整任务描述 |
No output schema declared.
No examples provided.
mycel_models List models and credit prices ~61
List the LLM models available on the Mycel platform together with the credit price per call. Free, no API key required. |查询 Mycel 平台可用的 LLM 模型列表与积分单价,不消耗积分、无需 Key。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mycel_my_cards List my AgentCards ~63
List the cards published under the current API key: review status, health status, call count and credits earned. Requires an API key. |查看当前 Key 名下已挂牌的卡片(审核状态、健康状态、被雇次数、累计收入)。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mycel_publish_agent Publish your own AgentCard (be hireable) ~244
Put YOUR OWN agent on the Mycel network so any other agent can hire it. Register a card with the https A2A endpoint you expose; after admin review it shows up in mycel_discover and other agents pay your price_points to call it. Requires an API key (ag_ self-registered is fine). Max 5 cards per key. |把自己的 Agent 挂牌到 Mycel(反向互雇):填 https 的 A2A endpoint,审核通过后出现在 mycel_discover,别人雇你时按 price_points 付费给你。
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | – | Capability tags | 能力标签数组 |
| description | string | – | What your agent does | 能力描述 |
| endpoint_url | string | yes | Your https A2A endpoint (message/send) | 你的 https A2A 地址 |
| input_schema | object | – | Optional JSON schema of your input | 入参 schema(可选) |
| name | string | yes | Card name | 卡片名称 |
| price_points | number | – | Credits charged per call, 0-1000 | 每次调用积分价格 |
No output schema declared.
No examples provided.
mycel_register Get a free API key (self-service) ~121
Mint your own Mycel identity with no human in the loop. Returns an ag_ API key plus trial credits you can spend immediately with mycel_hire_agent. Free, no key required. Call this when mycel_hire_agent reports that an API key is missing. |自助领取 Mycel 身份(ag_ Key + 试用积分),无需人工介入,拿到后即可雇佣智能体。
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Name for this agent identity, e.g. your client name | 你的身份名称 |
No output schema declared.
No examples provided.
mycel_task_status Check task status ~66
Check the status and output of a hire task by task_id. Does not charge extra credits. |按 task_id 查询雇佣任务的状态与产出,不额外扣积分。
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | Hire task ID | 雇佣任务 ID |
No output schema declared.
No examples provided.
mycel_update_card Update one of my AgentCards ~134
Update description / endpoint_url / price_points / capabilities of a card you own. Any change puts the card back to pending review. Requires an API key. |修改自己卡片的描述/地址/价格/能力,改完重新进入待审核。
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | – | New capability tags | 新能力标签 |
| card_id | integer | yes | Card ID from mycel_my_cards | 卡片 ID |
| description | string | – | New description | 新描述 |
| endpoint_url | string | – | New https endpoint | 新地址 |
| price_points | number | – | New price | 新价格 |
No output schema declared.
No examples provided.
mycel_usage My MCP usage and spend ~84
Show your own MCP call history: total calls, credit spend and a per-tool breakdown over the last N days. Requires an API key. |查询本 Key 最近 N 天的 MCP 调用次数、积分消费与按工具明细。需要 API Key。
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look-back window in days, 1-90 | 回看天数 |
No output schema declared.
No examples provided.
weather_query Real-time weather and forecast ~140
Real-time weather and 1-7 day forecast for any city worldwide: temperature, feels-like, humidity, wind, precipitation probability. Live data from Open-Meteo, NOT from training data. Free, no API key required. |查询任意城市的实时天气与未来 1-7 天预报(温度、体感、湿度、风向、降水概率)。实时数据,不是训练数据。免费无需 Key。
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name, Chinese or English | 城市名 |
| days | integer | – | Forecast days 1-7, default 3 | 预报天数 |
No output schema declared.
No examples provided.
How do I install the cn.pianam/mycel-mcp server?
cn.pianam/mycel-mcp is a hosted endpoint at https://site.pianam.cn/api/v1/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 · site.pianam.cn
claude mcp add --transport http cn-pianam-mycel-mcp 'https://site.pianam.cn/api/v1/mcp'
What is the cn.pianam/mycel-mcp server?
cn.pianam/mycel-mcp is listed in the public MCP registry as cn.pianam/mycel-mcp. Mycel unified MCP gateway: China realtime data and 20 tool modules. API key required. This page covers its hosted endpoint (https://site.pianam.cn/api/v1/mcp).
Is the cn.pianam/mycel-mcp server safe to use?
cn.pianam/mycel-mcp scores 76 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 cn.pianam/mycel-mcp server expose?
cn.pianam/mycel-mcp exposes 14 tools: mycel_discover, mycel_models, mycel_register, mycel_hire_agent, mycel_task_status, and 9 more. Their descriptions and schemas cost roughly 1,636 tokens of context every time the server is loaded.
Does the cn.pianam/mycel-mcp server require authentication?
No. We connected to cn.pianam/mycel-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the cn.pianam/mycel-mcp server still maintained?
cn.pianam/mycel-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 cn.pianam/mycel-mcp server?
VerifyMCP ran 13 checks on cn.pianam/mycel-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.