MCP server for accessing JueJin (掘金) article data and information
Scoring was not performed
No tool descriptions visible in source code. All three tools lack documentation explaining what they do, when to use them, or what they return. LLMs cannot determine tool selection criteria without descriptions.
No input parameter schemas visible. JueJinArticleService method signatures are not provided in source code. Cannot verify parameter types, required vs optional, constraints (enums, ranges), or parameter descriptions.
No output schema documentation. Baseline requires 100% of A+ tools to have documented return types. No evidence of return type documentation, field descriptions, pagination support, or structured response shaping.
Tool definitions inferred rather than directly visible. Source code shows MethodToolCallbackProvider.builder().toolObjects(jueJinArticleService).build() but does not include JueJinArticleService class implementation, method signatures, or annotations.
No error handling patterns visible. No evidence of error classification, recovery guidance, or actionable error messages. Rubric baseline: A+ tools guide LLM recovery with specific next steps.
Credentials exposed as configuration. JueJinApiProperties.getCookie() is logged at startup (McpServerApplication.java:run()). API keys/cookies should never be logged or passed as plain config. Use server-side secret injection via environment variables or vault. Agent traces log every parameter, secrets in params leak into logs.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 0 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 16 | - | v1 |