cn.pianam.mcp/devtools-mcp
REMOTE · MCP.PIANAM.CN
Developer toolkit: UUID, timestamp, unit conversion, JSON tools, and QR code (SVG). Free.
Available components
Last scanned (41 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 16 Sep 2026.
Category Developer Tools
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
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.
- 25 Sept 26 −12
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Sept 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Sept 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: 0.37 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 16 Sept 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.
- 14 Sept 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.
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 25 Sept 2026 · Probed https://mcp.pianam.cn/devtools-mcp/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of mcp.pianam.cn. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| mcp.pianam.cn. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.pianam.cn/devtools-mcp/mcp | Unreachable | ||
| http (plaintext) | http://mcp.pianam.cn/devtools-mcp/mcp | HTTPS enforced |
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 →
convert_timestamp ~134
时间戳双向转换，时区统一北京时间(UTC+8)。传入 Unix 时间戳（整数秒或毫秒，自动识别；也接受数字字符串）返回 ISO 8601 北京时间字符串；传入日期/时间字符串（如 2026-09-05、2026-09-05 10:30:00、2026-09-05T10:30:00+08:00）返回 Unix 秒/毫秒时间戳；不传 value 返回当前时间的两种格式。
| Name | Type | Req | Description |
|---|---|---|---|
| to | string | – | – |
| value | – | – | – |
No output schema declared.
No examples provided.
convert_unit ~161
单位换算，支持四类：长度(m/km/cm/mm/mile/foot/inch，含毫米/厘米/英里/英尺/英寸)、重量(kg/g/mg/t/lb/oz，含克/磅/盎司)、温度(c/f/k，摄氏度/华氏度/开尔文，自动做偏移换算)、数据存储(B/KB/MB/GB/TB/PB，按1024二进制换算)。不支持的单位或跨类别换算（如米换算成千克）会返回清晰错误。
| Name | Type | Req | Description |
|---|---|---|---|
| from_unit | string | yes | – |
| to_unit | string | yes | – |
| value | number | yes | – |
No output schema declared.
No examples provided.
format_json ~92
JSON 字符串处理。action 支持：format（美化缩进2格，中文不转义）、minify（压缩为单行去空白）、validate（仅校验合法性，非法时返回错误行号、列号、位置指针和上下文片段）。输入 data 必须是字符串。
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| data | string | yes | – |
No output schema declared.
No examples provided.
generate_qr ~143
生成二维码。默认 format='svg' 返回 SVG 矢量图字符串（纯标准库生成，可直接保存为 .svg 文件，AI agent 可直接写文件）；format='png' 时返回 PNG 图片的 base64 编码和 data URI（需服务器安装 Pillow，未安装会返回提示）。content 支持 URL、纯文本、WiFi 配置（如 WIFI:T:WPA;S:网络名;P:密码;;）等任意字符串，上限 2000 字节。CPU 密集，走线程池不阻塞事件循环。
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| format | string | – | – |
No output schema declared.
No examples provided.
generate_uuid ~108
生成 UUID（通用唯一识别码）。支持 v4 随机 UUID（默认）和 v5 命名空间 UUID（SHA-1 确定性生成，需提供 namespace 和 name）。count 可一次生成多个（1~1000）。namespace 支持预定义名 dns/url/oid/x500 或完整 UUID 字符串。
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| name | – | – | – |
| namespace | – | – | – |
| version | string | – | – |
No output schema declared.
No examples provided.
query_npm_version ~130
查询 npm 包的最新版本信息。输入 npm 包名（如 react、vue、express、@vue/cli），返回最新版本号 latest_version、该版本发布时间 published_at（UTC ISO 8601）、包描述 description、开源协议 license，以及主页/仓库地址等。数据源优先官方 registry.npmjs.org，失败自动兜底淘宝镜像 registry.npmmirror.com（国内更快）。包不存在返回明确的 404 提示。网络 I/O 走线程池不阻塞事件循环。
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | – |
No output schema declared.
No examples provided.
resolve_dns ~163
DNS 域名解析（DoH，JSON API）。输入域名 name（如 baidu.com、www.qq.com）和记录类型 type（A 默认/AAAA/CNAME/MX/TXT），返回解析记录列表（每条含 name、type、ttl、data；MX 数据为 优先级+邮件交换主机，TXT 为文本记录）。数据源优先阿里 DoH（dns.alidns.com，国内快），失败自动兜底 Cloudflare DoH。域名不存在返回 NXDOMAIN 提示；域名存在但无该类型记录时返回空列表并附说明。网络 I/O 走线程池不阻塞事件循环。
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
How do I install the cn.pianam.mcp/devtools-mcp server?
cn.pianam.mcp/devtools-mcp is a hosted endpoint at https://mcp.pianam.cn/devtools-mcp/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 · mcp.pianam.cn
claude mcp add --transport http cn-pianam-mcp-devtools-mcp 'https://mcp.pianam.cn/devtools-mcp/mcp'
What is the cn.pianam.mcp/devtools-mcp server?
cn.pianam.mcp/devtools-mcp is listed in the public MCP registry as cn.pianam.mcp/devtools-mcp. Developer toolkit: UUID, timestamp, unit conversion, JSON tools, and QR code (SVG). Free. This page covers its hosted endpoint (https://mcp.pianam.cn/devtools-mcp/mcp).
Is the cn.pianam.mcp/devtools-mcp server safe to use?
cn.pianam.mcp/devtools-mcp scores 0 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.mcp/devtools-mcp server expose?
cn.pianam.mcp/devtools-mcp exposes 7 tools: generate_uuid, convert_timestamp, convert_unit, format_json, generate_qr, and 2 more. Their descriptions and schemas cost roughly 931 tokens of context every time the server is loaded.
Does the cn.pianam.mcp/devtools-mcp server require authentication?
Its publisher declares no required credentials for cn.pianam.mcp/devtools-mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the cn.pianam.mcp/devtools-mcp server still maintained?
cn.pianam.mcp/devtools-mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 16 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.