cn.pianam/devtools-mcp
REMOTE · PIANAM.CN
MCP server with 5 offline developer tools: UUID, timestamp, unit conversion, JSON tools and QR code.
Available components
Last scanned (13 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
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 7 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1311 tokens (~187/item across 7 items; 7 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 21 Nov 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.
- 19 Nov 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.
- 17 Nov 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.
- 15 Nov 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.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 66
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://pianam.cn/devtools-mcp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pianam.cn | CN=YR1,O=Let's Encrypt,C=US | 11 Nov 2026 | 9 Feb 2027 | RSA 2048 | SHA256-RSA | 52faeb2a8c950aa4b834de3ec969b579723 |
| SANs: pianam.cn, www.pianam.cn | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 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://pianam.cn/devtools-mcp/mcp | Verified | 200 | |
| http (plaintext) | http://pianam.cn/devtools-mcp/mcp | HTTPS enforced | 301 | https://pianam.cn/devtools-mcp/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 →
convert_timestamp Convert Timestamp ~222
时间戳双向转换,时区统一北京时间(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 | – | 转换方向提示,"iso"(默认,转北京时间字符串)或 "unix"(转时间戳); 实际方向按 value 类型自动判断 |
| value | – | – | Unix 时间戳(秒/毫秒,整数或数字字符串,自动区分), 或日期时间字符串(ISO 8601、YYYY-MM-DD、YYYY/MM/DD HH:MM 等); 不传或传空字符串则返回当前北京时间 |
Structured output declared, but exposes no named fields.
No examples provided.
convert_unit Convert Unit ~204
单位换算,支持四类:长度(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 | 源单位,如 "km"、"lb"、"f"、"GB" |
| to_unit | string | yes | 目标单位,如 "mile"、"kg"、"c"、"MB" |
| value | number | yes | 待换算的数值 |
Structured output declared, but exposes no named fields.
No examples provided.
format_json Format Json ~127
JSON 字符串处理。action 支持:format(美化缩进2格,中文不转义)、minify(压缩为单行去空白)、validate(仅校验合法性,非法时返回错误行号、列号、位置指针和上下文片段)。输入 data 必须是字符串。
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | "format"(默认,美化缩进2格)、"minify"(压缩)、 "validate"(校验合法性) |
| data | string | yes | JSON 格式的字符串 |
Structured output declared, but exposes no named fields.
No examples provided.
generate_qr Generate Qr ~184
生成二维码。默认 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 | 要编码的内容,支持 URL、纯文本、WiFi 字符串等,不能为空 |
| format | string | – | "svg"(默认,返回 SVG 文本)或 "png"(返回 base64,需 Pillow) |
Structured output declared, but exposes no named fields.
No examples provided.
generate_uuid Generate Uuid ~190
生成 UUID(通用唯一识别码)。支持 v4 随机 UUID(默认)和 v5 命名空间 UUID(SHA-1 确定性生成,需提供 namespace 和 name)。count 可一次生成多个(1~1000)。namespace 支持预定义名 dns/url/oid/x500 或完整 UUID 字符串。
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | 生成数量,1~1000,默认 1 |
| name | – | – | v5 必填,命名用的名称字符串,如域名、URL 等 |
| namespace | – | – | v5 必填,命名空间,可传 "dns"/"url"/"oid"/"x500" 或完整 UUID 字符串 |
| version | string | – | UUID 版本,"v4"(默认,随机)或 "v5"(命名空间确定性) |
Structured output declared, but exposes no named fields.
No examples provided.
query_npm_version Query Npm Version ~151
查询 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 | npm 包名,如 "react"、"vue"、"express"、"@vue/cli" |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_dns Resolve Dns ~233
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 | 要解析的域名,如 "baidu.com"、"www.qq.com"(不含 http:// 和路径) |
| type | string | – | 记录类型,"A"(默认,IPv4)/ "AAAA"(IPv6)/ "CNAME"(别名)/ "MX"(邮件交换)/ "TXT"(文本记录) |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the cn.pianam/devtools-mcp server?
cn.pianam/devtools-mcp is a hosted endpoint at https://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 · pianam.cn
claude mcp add --transport http cn-pianam-devtools-mcp 'https://pianam.cn/devtools-mcp/mcp'
What is the cn.pianam/devtools-mcp server?
cn.pianam/devtools-mcp is listed in the public MCP registry as cn.pianam/devtools-mcp. MCP server with 5 offline developer tools: UUID, timestamp, unit conversion, JSON tools and QR code. This page covers its hosted endpoint (https://pianam.cn/devtools-mcp/mcp).
Is the cn.pianam/devtools-mcp server safe to use?
cn.pianam/devtools-mcp scores 72 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/devtools-mcp server expose?
cn.pianam/devtools-mcp exposes 7 tools: generate_uuid, convert_timestamp, convert_unit, format_json, generate_qr, and 2 more. Their descriptions and schemas cost roughly 1,311 tokens of context every time the server is loaded.
Does the cn.pianam/devtools-mcp server require authentication?
No. We connected to cn.pianam/devtools-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the cn.pianam/devtools-mcp server still maintained?
cn.pianam/devtools-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/devtools-mcp server?
VerifyMCP ran 12 checks on cn.pianam/devtools-mcp, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about cn.pianam/devtools-mcp: Authorization. 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.