rubyLs/yearning_mcp (rubyLs/yearning_mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 19 tools. No publisher has claimed this listing.

Emerging

74/100

rubyLs/yearning_mcp

Item: rubyLs/yearning_mcp
Rating: 74
Author: M8ven

MCP server for Yearning SQL review platform, enabling read-only queries, ticket management (submit, audit, undo, rollback), query applications, comments, and data source/table exploration via REST/WebSocket APIs.

→ rubyLs/yearning_mcp · listed on glama

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 push why connect →

Who stands behind it

rubyLs

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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: MCP_AUTH_TOKEN, YEARNING_PASSWORD

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// tools this server exposes19 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

yearning_user_info

查看当前登录用户信息、部门、邮箱，以及有权查询的数据源列表。对应 GET /api/v2/fetch/userinfo

yearning_list_sources

列出当前账号有权限的数据源（可按 query/dml/ddl/idc 过滤）。对应 GET /api/v2/fetch/source

yearning_list_databases

列出指定数据源下的数据库列表。对应 GET /api/v2/fetch/base

yearning_list_tables

列出指定数据源、指定库下的表。对应 GET /api/v2/fetch/table

yearning_table_fields

查看表结构：字段列表（类型/可空/键/默认值/注释）与索引。对应 GET /api/v2/fetch/fields

yearning_sql_check

提交前对 SQL 做审核检测。建议先调用本工具，再 yearning_submit_order。对应 PUT /api/v2/fetch/test。不接受 SELECT（请用 yearning_run_query）。

yearning_my_orders

分页列出当前用户提交的工单。状态：8=全部 / 2=待审核 / 3=已完成 / 0=已驳回 / 4=已终止 / 6=已撤回 / 1=执行中 / 5=待执行。对应 WS /api/v2/common/list

yearning_order_detail

查看工单详情：SQL 明细与完整 SQL。对应 GET /api/v2/fetch/detail + /fetch/sql

yearning_order_timeline

查看工单审核时间线与流程步骤。审核时 flag 取自此处。对应 GET /api/v2/fetch/timeline + /fetch/steps

yearning_rollback_sql

获取工单的回滚 SQL。对应 GET /api/v2/fetch/roll

yearning_audit_orders

分页列出与当前用户相关的待审核工单（审核人视角）。对应 WS /api/v2/audit/order/list

yearning_query_status

查看查询审核开关，以及当前用户查询工单是否有效。对应 GET /api/v2/fetch/is_query + /fetch/query_status

yearning_run_query

在指定数据源执行只读 SELECT 查询。需具备查询权限；若开启查询审核，需先 yearning_submit_query_order。对应 WS /api/v2/query/results（msgpack）

yearning_order_comments

读取指定工单的全部评论。对应 WS /api/v2/fetch/comment

yearning_submit_order

yearning_undo_order

撤回自己提交、尚未执行的工单。对应 GET /api/v2/fetch/undo。必须传 confirm=true。

yearning_audit_order

yearning_submit_query_order

提交数据查询申请。开通查询审核时需审批通过后方可 yearning_run_query。对应 POST /api/v2/query/post

yearning_post_comment

在指定工单下发表评论。对应 POST /api/v2/fetch/comment

// 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.

🔐 secretMCP_AUTH_TOKENe =your-strong-token \

configMCP_HOST/ MCP_PORT HTTP 监听 0.0.0.0 / 8080

configMCP_LOG_LEVEL

configMCP_PORTMCP_HOST / HTTP 监听 0.0.0.0 / 8080

configMCP_TRANSPORTstdio / sse / streamable-http stdio

configYEARNING_LOGIN_TYPE"": "general",

🔐 secretYEARNING_PASSWORD"": "your-password",

configYEARNING_URL"": "http://your-yearning:8000",

configYEARNING_USERNAME"": "your-user",

// 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

19/19 tools missing one or more hints — yearning_user_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); yearning_list_sources (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); yearning_list_databases (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 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

17/19 tool handlers declare input schemas (89%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

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 4 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/rubyls/yearning_mcp)](https://m8ven.ai/mcp/rubyls/yearning_mcp)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: 137ea66b8852fa7dbda049abc52a4945386f53e0

code hash: 8bd51338102aad1ff2ed1871e2d4183a0c8b956690b4ac1df30166434b6c83e8

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