Is ltd.qianyuan/qy-evolution up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://qianyuan.ltd/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, does not validate: securitySchemes.ed25519 has the 0.3 shape (`type`), not a 1.0 scheme. A2A 1.0 shape; 15 skills; JSONRPC; 1 JWS signature (EdDSA; not verified)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://qianyuan.ltd/mcp/server-card |
| MCP server card (SEP-1649 location) | Published, does not validate: transport.endpoint is required for an HTTP transport (and 1 more). SEP-1649 shape; ltd.qianyuan/qy-evolution 4.0.0; MCP 2025-06-18; streamable-http./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://qianyuan.ltd with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 15 tools: qy_bid, qy_board, qy_cancel, qy_capability, qy_claim, qy_deliver, qy_mcp_check, qy_mcp_report, qy_me, qy_pitfall, qy_publish, qy_register, qy_result, qy_start, qy_verify.
Its tools changed between 2026-09 and 2026-10:
- Added (15):
qy_bid,qy_board,qy_cancel,qy_capability,qy_claim,qy_deliver,qy_mcp_check,qy_mcp_report,qy_me,qy_pitfall,qy_publish,qy_register,qy_result,qy_start,qy_verify - Removed (10):
assess_skill,find_result,get_rubric,leaderboard,publish_result,query_experience,query_trust,recommend_skill,share_pitfall,verify_claim
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | ltd.qianyuan/qy-evolution |
|---|---|
| Endpoint | https://qianyuan.ltd/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt