PingCode MCP (frontendRicky/pingcode-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Emerging
74/100
2 months ago

PingCode MCP

Enables natural language reading and management of PingCode project work items (defects and requirements) through Cursor, Claude Code, Codex, and other clients.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

frontendRicky

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: PINGCODE_ACCESS_TOKEN, PINGCODE_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretPINGCODE_ACCESS_TOKEN2. :直接配置的官方 Open API access_token。
configPINGCODE_API_BASE_URL"": "https://open.pingcode.com",
configPINGCODE_AUTH_SCHEME
configPINGCODE_AUTH_TOKEN_PATH:用户态 token 存放路径,缺省为 ${XDG_CONFIG_HOME 或 ~/.config}/pingcode-mcp/auth.json(文件权限 0600)。
configPINGCODE_BASE_URLPINGCODE_OAUTH_AUTHORIZE_URL:浏览器授权地址,缺省为 ${}/oauth2/authorize。
configPINGCODE_BUG_TYPE_ID
configPINGCODE_CLIENT_ID每个人自己的 Client ID
🔐 secretPINGCODE_CLIENT_SECRET每个人自己的 Client Secret
configPINGCODE_DEFAULT_ASSIGNEE_NAME每个人自己的 PingCode 展示名
configPINGCODE_OAUTH_AUTHORIZE_URL:浏览器授权地址,缺省为 ${PINGCODE_BASE_URL}/oauth2/authorize。
configPINGCODE_OAUTH_REDIRECT_URI:授权回调地址,须与 PingCode 后台凭据管理里配置的一致。
configPINGCODE_PROJECT_ID
configPINGCODE_PROJECT_IDENTIFIERPROJECT_KEY
configPINGCODE_READONLYtrue 时禁止创建和更新。
configPINGCODE_REQUIREMENT_TYPE_ID
configPINGCODE_TIMEOUT_MS
configXDG_CONFIG_HOMEPINGCODE_AUTH_TOKEN_PATH:用户态 token 存放路径,缺省为 ${ 或 ~/.config}/pingcode-mcp/auth.json(文件权限 0600)。
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

30/30 tools missing one or more hints — pingcode_get_project_schema (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); pingcode_get_current_team (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); pingcode_get_current_user (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +27 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

Only 1/30 tool handlers declare input schemas (3%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

Only 0/30 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Domain consistency

npm scope @succaiss doesn't match GitHub owner frontendricky

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/frontendricky-pingcode-mcp-1t5mzu)](https://m8ven.ai/mcp/frontendricky-pingcode-mcp-1t5mzu)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 00cd2f628250d1be7deb41327bd6b7baab3a6683
code hash: df38328fa88852cf84e2d4bf53bc830ef5b8d5de2270780d1fe460722d4483f3
verified: 6/16/2026, 11:31:14 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client