Summary
It hands over the API's own specification and lets the model compose the request, rather than modelling NFT concepts itself.
The consequence is that the surface is as wide as the published spec and no wider: nothing here knows what a collection or a floor price is, so every answer depends on the model reading api-path-schema correctly before it calls request. That makes the discovery step load-bearing rather than optional. It also means a new NFTGo endpoint is reachable the day it appears in the specification, with no change on this side.
What it is
A passthrough to the NFTGo data API at https://data-api.nftgo.io, driven by that API's OpenAPI specifications through 3 tools.
What you get
- api-documentation returns the list of NFT API endpoints with their documentation.
- api-path-schema returns the description and parameters for one path.
- request issues the HTTP call against https://data-api.nftgo.io with the url, type, headers and body the schema calls for.
Requirements
An NFTGo API key, passed to the server at start-up.
Setup effort
One command — npx -y @nftgo/mcp-nftgo-api NFTGO-API-KEY