Because each capability is a separate built file registered on its own, you can connect just the wallet-value lookup without also loading the trending rankings — useful when tool budget is tight. The setup wrinkle to know about is the Thirdweb key: it is edited into the source before building rather than read from the environment, so it has to be in place at build time, and rotating it means rebuilding.
A set of small MCP servers over NFT APIs for the Monad testnet. Each answers one question: who holds a collection, what an address owns, what that is worth at floor prices, and which collections are trending by sales or by volume.
- The list of holder addresses for an NFT contract
- All the NFT collections a given address holds
- The total value of an address's NFTs, calculated from floor prices
- Top-selling collections ranked by number of sales
- Top-selling collections ranked by volume
- A time window on both rankings: 5 min, 10 min, 30 min, 1 h, 6 h, 24 h, 1 d, 7 d or 30 d
- Each capability ships as its own built file, so you register only the ones you want in the client config
Node.js v16 or later and npm. Clone, `npm install`, then `npm run build`; the client registers the built files it needs by absolute path. The holders lookup additionally needs a Thirdweb client key, created as a project with origin allowance and pasted into `nft-owners.ts` as `THIRDWEB_CLIENT_ID` before the build. Data is Monad testnet, so figures are testnet figures.
Build from source — clone the repository and build it, then point your client at the binary