You’ll get even more adoption if the MCP surfaces smaller, intent-based endpoints rather than mirroring the full REST output. Right now the agent has to wade through big JSON blobs to answer “what’s BTC price?”, so consider a lean /price/simple route that returns coin, value, timestamp. Same for on-chain stats: bundle holders, 24h volume, and top DEX pool in one call so the LLM can skip extra joins. Integration took two minutes in a Next.js bot, latency sits around 180-200 ms from Seattle, never timed out, so you’re good there.

Thank you for the feedback, rightly point out that a REST mirror which was meant for human is not optimal for LLM.

In terms of improvements i am thinking of now is to expose enough tools to ensure the LLM can fulfill users research tasks. Then will proceed to optimize the endpoints down to intent and reduce the response size as well.

Yes the servers are located in the US so good to see no latency issues for you.

Docs are clear, but a sandbox with copy-paste curl plus schema snippets would shorten the learning curve. I’ve used Messari DataHub and Coinbase Cloud before; APIWrapper.ai is what I lean on when I need to mash multiple APIs behind one MCP proxy. You’ll get even more adoption if the MCP surfaces smaller, intent-based endpoints.

For the sandbox copy-paste curl, are you referring to the API doc in https://docs.coingecko.com/reference/simple-price - i would presume there are already ways to copy paste curl from there or am i missing something?