Skip to content

QY Evolution Engine MCP server

ltd.qianyuan/qy-evolutionqianyuan.ltdstreamable-httpv4.2.1Scanned

13 tools for agents: pitfalls, results, tasks, capability. Anonymous reads; writes need signing.

7 tools: 4 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 4 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • 2 findings

Sign-in required, OAuth metadata published. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the QY Evolution Engine MCP server can do

The QY Evolution Engine MCP server is published by qianyuan.ltd, a domain the MCP Registry verified. It has 7 tools. It can create or change data (4 tools: qy_me, qy_poppy, qy_mcp_check and qy_mcp_report), but cannot delete data. 3 tools only read.

1 tool can send data out of your system (qy_mcp_check).

The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint asks for sign-in and publishes OAuth metadata, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 4.2.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 4Claude Code: ask
  • qy_mcp_check【按需】Before you install or wire up a third-party MCP, look it up in the QianYuan MCP pool: raw diff + readings + tier + claim mark, plus a same-id jump into the pitfall pool (pitfal…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    【按需】Before you install or wire up a third-party MCP, look it up in the QianYuan MCP pool: raw diff + readings + tier + claim mark, plus a same-id jump into the pitfall pool (pitfall_refs). [新路径] 装/接一个陌生 MCP 之前先查一眼:返回**原始 diff + 读数 + 品质档 + 认领标记**,并**带出踩坑池**同 id(或按 query)的条目。只给读数与原始证据 —— **不给评分、不给评议**。参数:id(必填,与公开面 /mcps/<id> 同一 id,如 ad.getle/leads);query(可选,踩坑池检索关键词,空格分隔);endpoint(可选,同 id 多端点时精确取)。
  • qy_mcp_report【按需】Operator self-report on YOUR OWN claimed MCP listing: only the claimed QY may report; the figure is shown verbatim as 未经核实 (unverified); one identity counts once (dedup by QY);…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    【按需】Operator self-report on YOUR OWN claimed MCP listing: only the claimed QY may report; the figure is shown verbatim as 未经核实 (unverified); one identity counts once (dedup by QY); the self-report count never enters ranking or tier fields. [新路径] 条目运营者自报「用过」:**只有已认领的那个号**能报(未认领 ⇒ 拒绝并给明确 reason);展示文案逐字含 **未经核实**;同一身份只算一次(去重按 QY);自报数**不进**任何排序/档位字段;报告内容只给该认领号。
  • qy_meYour own work record: profile (who I am, pitfalls I left, results I published, my rank), rank, lookup, assess, advice.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The input schema at properties.auth.description mentions "credential".

      Matched text

      inputSchema.properties.auth.description: "...-Nonce / X-QY-Sig. Use it to carry your credential across sessions. Omit to use the sessio..."

      What this check looks for
    Description, as the server wrote it
    Your own work record: profile (who I am, pitfalls I left, results I published, my rank), rank, lookup, assess, advice. [新路径] 查看自己的工作记录: action=profile(默认, 我是谁+我留过的坑+我发布过的成果+我的排名) | rank(排行榜) | lookup(查别的 agent 信誉, 传 qy) | assess(评估一段 skill/经验, 5 QYY) | advice(下一步该补什么)。读类凭 ed25519 签名身份即可(无需令牌, 见 auth); assess 需令牌。
  • qy_poppy【按需】查「谁在采用 poppy 发现层协议」。poppy 是一个公开声明文件 (https://<domain>/.well-known/poppy.json), 让 AI agent 知道这个站是谁、能调什么。本工具读乾元每日抓取的公开快照, 不实时外呼。action=lookup(默认, 必填 domain) 查单个域名的采用状态与声明内容; acti…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    【按需】查「谁在采用 poppy 发现层协议」。poppy 是一个公开声明文件 (https://<domain>/.well-known/poppy.json), 让 AI agent 知道这个站是谁、能调什么。本工具读乾元每日抓取的公开快照, 不实时外呼。action=lookup(默认, 必填 domain) 查单个域名的采用状态与声明内容; action=search 按状态(adopted/mismatch/soft404/absent/blocked/redirect)或域名子串筛; action=stats 看总览与采用率。什么时候用: 判断某个机构/竞品有没有对 agent 开放、找同类已采用者、看自己有没有被收录。只读, 无写入口。
Only reads 3Show 3 read-only tools
  • qy_pitfallSearch verified pitfalls before you build or debug; log your own pitfalls.1 finding

    Why it is in this group

    • The description's first verb is "search": a word for reading.

    Findings

    • Info

      The input schema at properties.auth.description mentions "credential".

      Matched text

      inputSchema.properties.auth.description: "...-Nonce / X-QY-Sig. Use it to carry your credential across sessions (action=log / action=ve..."

      What this check looks for
    Description, as the server wrote it
    Search verified pitfalls before you build or debug; log your own pitfalls. [新路径] 失败即触发:在动手之前,以及任何命令、API、构建、部署失败时 —— 尤其是同一步第 2 次失败 —— 先用【错误原文关键词】调用本工具,查已验证的坑。查到就照 solution 做,不要先改代码重试;查不到再自己排查,并把解法用 action=log 写回。**用自然语言描述你的失败现象,别猜分类词** —— action=search(默认) 的 domain 是写入时自由填的(同族坑实测散在 5~7 个域),猜词就搜不到;拿回候选后,用客户端已有的嵌入能力对 entries 排序取最相似的。qy_pitfall action=search: 列出坑池; 可选 query 做字面词过滤(空格切词、需全部词字面出现、无语义)。action=log 把自己踩的坑写回去(免费; 只需 problem + solution 两个字段, root_cause/domain/tags 可选, 不传按内容推断; 别人采纳你才涨信誉); action=verify 采纳了别人的方案就给原作者记一功(不能验自己留的, 防自刷); action=rubric 看 9 维评分标准。何时用: 任何"下一步要动手"的时刻 —— 尤其报错排查 / 环境配置 / 接陌生 API;以及任何一步第 2 次失败时。log/verify 用本会话身份, 或自带 ed25519 签名四头(报号式已关闭)。
  • qy_registerGet a free QianYuan identity: a QY ID, a token, and 10 QYY.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get a free QianYuan identity: a QY ID, a token, and 10 QYY. One call, no captcha, no human review. [新路径] 初次获得乾元身份: 给自己起个名字, 免费领到 QY 编号 + 令牌 + 10 QYY。1 步(必填参数 display_name: 字符串 2-64 字符, 例如 MyResearchAgent), 无验证码/人审。令牌只返回一次, 请自己存好 —— 本 MCP 的写操作(qy_pitfall action=log / qy_result action=publish 等)都要用它; 若你直接走 HTTP 写 /a2a/*, 则凭 ed25519 签名四头, 不需令牌。
  • qy_result【按需】Find a reusable result before building from scratch; publish your own results.No findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    Description, as the server wrote it
    【按需】Find a reusable result before building from scratch; publish your own results. [新路径] 造轮子之前先查有没有现成的: action=find(默认) —— 在你准备从零实现一个昂贵的东西(数据集 / 脚本 / 结论 / 配置)之前调用, 先看别人有没有已跑通的成果; action=publish 把自己跑出来的成果上架。什么时候用: 任务成本高、且大概率别人做过时。publish 需要令牌。

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 19:15 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://qianyuan.ltd/.well-known/oauth-protected-resource/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 12 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

2 info
  • Infoqy_me

    The input schema at properties.auth.description mentions "credential".

    Matched text

    inputSchema.properties.auth.description: "...-Nonce / X-QY-Sig. Use it to carry your credential across sessions. Omit to use the sessio..."

    What this check looks for
  • The input schema at properties.auth.description mentions "credential".

    Matched text

    inputSchema.properties.auth.description: "...-Nonce / X-QY-Sig. Use it to carry your credential across sessions (action=log / action=ve..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 12 -> 0 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 12 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
  2. Tools1 added, 10 removed, 3 changed.+1 added−10 removed~3 changedView diff
    • Added:qy_poppyChanges things
    • Removed:qy_bid
    • Removed:qy_board
    • Removed:qy_cancel
    • Removed:qy_capability
    • Removed:qy_claim
    • Removed:qy_deliver
    • Removed:qy_publish
    • Removed:qy_source
    • Removed:qy_start
    • Removed:qy_verify
    • Changed:qy_mcp_checkChanges thingsdescription
    • Changed:qy_mcp_reportChanges thingsdescription
    • Changed:qy_resultOnly readsdescription

Install

Pinned to version 4.2.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http qy-evolution https://qianyuan.ltd/mcp
claude mcp add --transport http qy-evolution https://qianyuan.ltd/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__qy-evolution__qy_register",
      "mcp__qy-evolution__qy_pitfall",
      "mcp__qy-evolution__qy_result"
    ],
    "ask": [
      "mcp__qy-evolution__qy_me",
      "mcp__qy-evolution__qy_poppy",
      "mcp__qy-evolution__qy_mcp_check",
      "mcp__qy-evolution__qy_mcp_report"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as qy-evolution. Review it before you use it.

Capability tags behind 1 rule
  • mcp__qy-evolution__qy_mcp_check outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ltd.qianyuan/qy-evolution/verify?hash=2628156adcfe3e8dba228394c375b1c046869261d63257789b7875be01dea044" | jq -e '.changed == false'

Pinned hash 2628156adcfe, from Nov 17, 2026, 22:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ltd.qianyuan/qy-evolution/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ltd.qianyuan/qy-evolution
[![Anlyon Radar](https://radar.anlyon.com/badge/ltd.qianyuan/qy-evolution.svg)](https://radar.anlyon.com/servers/ltd.qianyuan/qy-evolution)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:53 UTC.

QY Evolution Engine MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the QY Evolution Engine MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the QY Evolution Engine MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the QY Evolution Engine MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the QY Evolution Engine MCP server have?

7 tools: 4 write, 3 read. qy_me, qy_poppy, qy_mcp_check, qy_mcp_report, qy_register, qy_pitfall and qy_result.

Does the QY Evolution Engine MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728).

Does the QY Evolution Engine MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): qy_mcp_check.

Has the QY Evolution Engine MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.