Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
OAuth-protected JPYC wallet, transfer, and contract workflows on Polygon.
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 …”.
Works in Claude on the web, desktop and mobile:
https://jpyc-info.com/api/jpyc-agent-mcpRun this in your terminal
claude mcp add --transport http jpyc-agent https://jpyc-info.com/api/jpyc-agent-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"jpyc-agent": {
"url": "https://jpyc-info.com/api/jpyc-agent-mcp"
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"jpyc-agent": {
"type": "http",
"url": "https://jpyc-info.com/api/jpyc-agent-mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
https://jpyc-info.com/api/jpyc-agent-mcpMenu names can differ slightly by plan and over time.
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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 8, 2026
The publisher (jpyc-info.com) is not the repo owner (yourbright-jp); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 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 in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, NexusWindows
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.
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
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.
JPYC Agent MCP can be used both as a public MCP endpoint and as a Codex plugin bundle. This repository now uses the repository root as the plugin root so Codex can discover it directly.
Codex should discover the plugin from the repository root via the files below:
.codex-plugin/plugin.json.mcp.jsonskills/jpyc-agent-mcp/SKILL.mdskills/jpyc-agent-mcp/agents/openai.yamlconfig/default.jsonhttps://jpyc-info.com/api/jpyc-agent-mcphttps://jpyc-info.com/api/jpyc-agent-oauthhttps://jpyc-info.com/.well-known/oauth-protected-resourcehttps://jpyc-info.com/.well-known/oauth-authorization-serverhttps://jpyc-info.com/.well-known/openid-configurationhttps://jpyc-info.com/mcp/connecthttps://jpyc-info.com/.well-known/mcp-registry-authThe endpoint is OAuth-protected. Users must log in and grant consent before private wallet operations can run. If you open the MCP endpoint directly in a browser, it redirects to https://jpyc-info.com/mcp/connect. If an MCP client receives 401 unauthorized, it should follow WWW-Authenticate and the resource metadata above to discover the OAuth flow. If ChatGPT/Codex does not surface a full authorization URL automatically, open https://jpyc-info.com/mcp/connect in the browser as the canonical human fallback. Low-level manual auth with /api/jpyc-agent-oauth/start remains available for debugging, but it is not the primary documented path. Clients using the low-level flow must keep the returned auth_session_secret private and present it when polling /api/jpyc-agent-oauth/auth-session.
For the complete OAuth contract and exact URLs, see docs/auth.md and config/oauth.json.
Claude Code does not natively support streamable-http MCP servers. Use mcp-remote to bridge streamable-http + OAuth to stdio.
Add the following to your project .mcp.json or ~/.claude/settings.json:
{
"mcpServers": { "jpyc-agent-mcp": { "command": "npx", "args": [ "mcp-remote", "https://jpyc-info.com/api/jpyc-agent-mcp" ] } } }
On first connection, mcp-remote opens a browser for OAuth consent. After authentication, all tools are available immediately.
This repository defines the OAuth-protected MCP endpoint and the plugin metadata needed for Codex discovery. It does not implement client-side credential storage on behalf of Codex, ChatGPT, or any other MCP client.
Expected client behavior:
https://jpyc-info.com/api/jpyc-agent-mcpauth_statusIf a client can complete browser login but cannot persist and reuse the issued credential locally, the MCP integration is incomplete from the user's point of view. In that case, the fix belongs in the MCP client implementation rather than this repository's server-side OAuth protocol.
For local operator workflows, this repository includes helpers that persist the issued refresh token with DPAPI and reuse it across future sessions:
docs/local-token-cache.mdscripts/jpyc_oauth_cache.py (Python, Windows)scripts/jpyc_oauth_cache.ps1 (PowerShell, Windows)This repository includes server.json for publishing the remote server to the public MCP Registry using the domain-based namespace com.jpyc-info/jpyc-agent-mcp.
For HTTP-based domain verification, host the exact text value v=MCPv1; k=...; p=... at https://jpyc-info.com/.well-known/mcp-registry-auth. In the jpyc-info deployment, that endpoint is served from the MCP_REGISTRY_AUTH environment variable.
auth_statuslist_agent_walletsget_agent_walletcreate_agent_walletget_agent_wallet_balancequote_transfertransfer_jpyclist_transactionsget_transfer_statusread_contractquote_contract_writeexecute_contract_writelist_contract_call_historyget_contract_call_statusDetailed request and response examples are in docs/tools.md.
auth_statuslist_agent_walletscreate_agent_walletTransfer flow:
quote_transfertransfer_jpycContract write flow:
quote_contract_writeexecute_contract_writedocs/auth.md, config/oauth.json, and docs/openai-and-mcp.md.