Add QianYuan (乾元) remote MCP server

[alvinxiao2]

MCP Server Information

Server Name: qianyuan
Repository URL: https://github.com/alvinxiao2/qianyuan-protocol
Brief Description: Trust and result-reuse layer for AI agents, exposed as a hosted remote MCP server (streamable-http, no local install). Search verified pitfalls before you build, publish results others can reuse, query an agent's trust score, or register a free agent identity.

Basic Requirements

• Open Source: Apache-2.0 — https://github.com/alvinxiao2/qianyuan-protocol/blob/main/LICENSE
• MCP Compliant: verified over streamable-http — initialize → serverInfo.name = qy-evolution, tools/list → 13 tools (protocolVersion 2025-06-18)
• Active Development: actively maintained
• Docker Artifact: N/A — remote (hosted) server; per CONTRIBUTING no Dockerfile is required for remote servers
• Documentation: https://qianyuan.ltd/llms.txt
• Security Contact: https://qianyuan.ltd/.well-known/security.txt

Submitter Checklist

• This server meets the basic requirements listed above
• I understand this will undergo automated and manual review.
• I have tested the MCP Server using task validate -- --name qianyuan
• I have built the MCP Server using task build -- --tools qianyuan
• If the server requires credentials to test it, I have shared test credentials using this form — not applicable: read tools are anonymous and require no credentials

Note on the two unchecked items. Our build host runs Go 1.22 while this repo requires Go 1.24, so task validate / task build could not be executed locally. We are relying on your CI as the gate and will address anything it reports. The entry follows the notion-remote template (remote, dynamic.tools: true) with the OAuth section omitted, since write-tool auth is a self-issued ed25519 agent identity rather than per-user OAuth — read tools need no auth at all.

Verification performed

POST https://qianyuan.ltd/mcp   (initialize, protocolVersion 2025-06-18)
→ HTTP 200 · serverInfo.name = qy-evolution · capabilities.tools.listChanged = true
tools/list → 13 tools

Live server card (generated by a handshake against the deployed endpoint, so it cannot drift):
https://qianyuan.ltd/.well-known/mcp/server-card.json

Notes

• tools.json is [] because dynamic.tools: true; the declared tool set is published at the server-card URL above.
• meta.category is set to knowledge; happy to change it to whichever enum the catalog expects.