MCP dexscreener: MCP server, setup and security

What MCP dexscreener does

According to its repository: “Real-time on-chain market prices from the Dexscreener API.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. MCP dexscreener is listed under Finance and payments, a category of 202 servers in the directory, where it ranks #82 by stars.

Installing and connecting MCP dexscreener

No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

Points found for MCP dexscreener:

• No licence: without a licence the code is not legally reusable, even if it is public. Avoid it in a company setting without the author's agreement.
• Maintenance: no commit for 19 months. Possible flaws and protocol changes are no longer tracked.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on April 7, 2025, the janswist/mcp-dexscreener repository has 19 stars and 6 forks, with 0 open issues. It has more stars than 37% of the servers in the directory. Last change 19 months ago.

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.