Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
AI agent real-name identity: SM2 keypair, QR real-name link, SD-JWT VP generate/verify.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"realagent": {
"command": "npx",
"args": [
"-y",
"realagent-mcp",
"stdio",
"--agent-id",
"your-value"
]
}
}
}Run this in your terminal
claude mcp add realagent -- npx -y realagent-mcp stdio --agent-id your-valueThis one needs values on its command line, so copy the settings and fill them in.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"realagent": {
"command": "npx",
"args": [
"-y",
"realagent-mcp",
"stdio",
"--agent-id",
"your-value"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one needs values on its command line, so copy the settings and fill them in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"realagent": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"realagent-mcp",
"stdio",
"--agent-id",
"your-value"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account RedDateTech, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.4.0) reached the registry last month.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Zoo MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server that provides access to the Zoo API for various CAD operations and tools.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
国信智能体实名关联服务 MCP Server — 单个可执行文件 · 本地通信 · 国密加密 · 全平台支持。
为 AI Agent 提供 SM2 实名身份关联、SD-JWT 可验证证明(VP)生成与验证、SM2 密码学操作等能力。
npm i -g realagent-mcp
必须全局安装(
-g)。这样realagent-mcp会进入 PATH,MCP 配置里的
npx realagent-mcp才会命中全局副本,而不会每次都往_npx缓存里再拉一份
(即避免依赖重复与 npx 旧缓存问题)。
配置 MCP Client(--agent-id 必填,每个 Agent 使用唯一名称):
{
"mcpServers": { "realagent-mcp": { "command": "npx", "args": ["-y", "realagent-mcp", "stdio", "--agent-id", "my-agent"] } } }
npm update -g realagent-mcp
npm i -g realagent-mcp@latest
升级后重启 MCP Client 即可。Agent 会在每次对话开始时自动调用 system_update 检查新版本。
MCP Server 运行时动态暴露以下 14 个工具:
| 工具 | 说明 |
|---|---|
identity_link | 发起实名关联:生成二维码,用户扫码认证后自动领取实名凭证(VC) |
identity_status | 查询当前 Agent 的实名关联状态与身份信息 |
identity_revoke | 注销实名关联并作废凭证 |
| 工具 | 说明 |
|---|---|
identity_vp | 生成 SD-JWT 可验证证明(VP),支持选择性披露字段 |
identity_verify_vp | 验证 VP 的签名与披露内容 |
vp_parse | 解析 VP 结构,提取披露的声明字段 |
| 工具 | 说明 |
|---|---|
vc_info | 查询本地已领取的可验证凭证(VC)摘要信息 |
vc_raw | 获取 VC 原始数据 |
key_info | 查询本地 SM2 密钥对与指纹信息 |
| 工具 | 说明 |
|---|---|
crypto_sign | 使用 SM2 私钥对数据签名 |
crypto_verify | 验证 SM2 签名 |
crypto_encrypt | SM2 加密数据 |
crypto_decrypt | SM2 解密数据 |
| 工具 | 说明 |
|---|---|
system_update | 检查 MCP Server 是否有新版本 |
以下内容供 AI Agent 读取,用于自动完成安装和配置。
node --version and npm --version. If both succeed and node --version reports >= v18.13, skip to step 2.node/npm is not found (no Node.js) or the version is older than 18.13, stop and help the user set it up before going further:winget install OpenJS.NodeJS.LTS (PowerShell), or download the LTS installer from https://nodejs.org.brew install node@22, or nvm install --lts (nvm: https://github.com/nvm-sh/nvm).nvm install --lts (nvm: https://github.com/nvm-sh/nvm), or the NodeSource repo for your distro.node --version, npm --version, and npx --version. Only proceed to step 2 once all three succeed and Node >= 18.13 is confirmed.realagent-mcp is on PATH): npm i -g realagent-mcp
--agent-id. One agent-id = one identity = one SM2 key pair. Never reuse an agent-id across agents. The realagent platform registers each key pair as a separate identity; shared agent-id causes identity conflicts.Generate an agent-id yourself, using a descriptive name based on the current project or the agent's purpose (e.g. "my-claude-code", "frontend-dev-helper", "pr-review-bot"). Use lowercase letters, digits and hyphens only. Then ASK the user to confirm before using it:
I'll configure realagent-mcp with agent-id: \ . This name will be
used to derive your unique SM2 identity. Is that OK? You can change
it to any name you prefer.
Once confirmed, write this MCP config:
{
"mcpServers": { "realagent-mcp": { "command": "npx", "args": [ "-y", "realagent-mcp", "stdio", "--agent-id", " " ] } } }
Data is stored under .realagent/agents/ in the working directory. Add --data-dir to customize the path.
identity_status.system_update at the start of each conversation (or at least once per day). When an update is available, tell the user and help them run npm update -g realagent-mcp or npm i -g realagent-mcp@latest. Only skip the version check if the user explicitly asks you to.