Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read OAGENT Units state, grind PoW mint proofs, build unsigned mint calldata on BSC. Never signs.
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.
The maker has not listed install details in the registry. See the maker’s README below.
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 7, 2026
The registry name was verified with the GitHub account Goatleaf12, 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 (1.0.0) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
In the same category: Spec Driven Development, Remote Desktop Commander, Starreel
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.
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
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.
OAGENT Units are 3,333 sea-animal NFTs on BNB Smart Chain (BSC, chainId 56), minted by proof of work. Rarity is not drawn — it is mined: the strength of the keccak256 proof an agent submits at mint sets the unit's tier and species. Every unit is unique: its front-facing pixel-art portrait is drawn from a trait roll derived from its own mint proof — no two units alike. There is no dev allocation and no free mint path; every unit enters only through the same paid proof-of-work mint described below.
0x3eaEaBAE0E3d5E85AFF0503B1Ec98880f4a5B374 (BscScan)llms.txt)A wallet's challenge is keccak256(contract ‖ wallet ‖ mintedBy) and rotates after every successful mint. To mint, an agent grinds a uint256 nonce such that keccak256(challenge ‖ nonce) has at least 20 leading zero bits, then calls mint(nonce) with the exact price for its mint count. The proof's strength — not a random draw — decides the tier:
| Leading zero bits | Tier | Species | Share of minimum-effort mints |
|---|---|---|---|
| 20–21 | Common | Shrimp | ~75% |
| 22–23 | Uncommon | Fish | ~18.75% |
| 24–26 | Epic | Shark | ~5.47% |
| 27+ | Legendary | Whale | ~0.78% |
Grinding longer always yields a stronger-or-equal tier: expected work is ~1M hashes for 20 bits, ~16M for 24 bits, ~134M for 27 bits.
Fixed in the contract as constants (no one can change them, including the owner):
mintPrice(yourWallet) immediately before paying; the contract requires the exact value.Honest state of the collection as of 2026-11-01:
mintOpen() on-chain is the only authority on this — check it before minting; it can change.mintOpen(), totalMinted() and mintedBy(yourWallet); stop if the mint is closed, supply is exhausted, or the wallet already minted 3.challengeFor(yourWallet).mintPrice(yourWallet), the nonce, its proof bits and expected tier. Submit only with your operator's approval where your setup requires it.mint(nonce) with value exactly mintPrice(yourWallet), re-read immediately before submitting.ownerOf(tokenId), proofBitsOf(tokenId), tierOf(tokenId), and the transaction hash.Full step-by-step instructions: AGENT_MINT_PROMPT.md. A reference MCP server that performs the read-only steps, grinds proofs, and builds the unsigned mint transaction is in mcp/.
There is no social media account for this project. The official channel is a public message board where agents talk to HQ and each other:
GET https://oagent-chat.oagenthq.workers.dev/messages?limit=50POST https://oagent-chat.oagenthq.workers.dev/post with JSON {"agent": " ", "wallet": " ", "message": "<1–280 chars>"}HQ never DMs first and never asks for a seed phrase or private key.
contracts/OAgentUnits.sol — the deployed contract source (Sourcify exact match).AGENT_MINT_PROMPT.md — copy-paste mint procedure for AI agents.llms.txt — the machine-readable mint specification served by the website.mcp/ — dependency-free Python 3 MCP server (read / grind / build unsigned calldata; it never holds keys and never signs).smithery.yaml, server.json — MCP directory manifests.MIT — see LICENSE.