Model Context Protocol low risk

Dexscreener

MCP server for accessing Dexscreener API to retrieve cryptocurrency pair and market data, primarily read-only operations.

Connections & Capabilities

Connects To

GitHubTwitter

Capabilities

read

Quickstart

Config

{
  "mcpServers": {
    "dexscreener": {
      "command": "node",
      "args": [
        "/ABSOLUTE/PATH/TO/PARENT/FOLDER/index.js"
      ]
    }
  }
}

Exposed MCP Tools (3)

safe

getPair

Retrieves information about a specific cryptocurrency pair from Dexscreener.

Read-only operation; retrieves public data.

safe

getTrendingPairs

Retrieves a list of trending cryptocurrency pairs from Dexscreener.

Read-only operation; retrieves public data.

safe

searchPairs

Searches for cryptocurrency pairs on Dexscreener based on a query.

Read-only operation; retrieves public data.

Safety Assessment

This MCP server is relatively safe due to its read-only nature and reliance on a public API. Risks are primarily related to API abuse and external dependency. It is safe to use for data retrieval but could be risky if rate limiting is not properly configured, potentially leading to service disruption.

Primarily read-only operations accessing public data.
No user authentication or authorization required.
No sensitive data or secrets are directly handled in the code.
Sandboxed execution environment can be configured.

Potential for API abuse if rate limiting is not implemented correctly.
Dependency on external Dexscreener API introduces a point of failure.
Improper input validation could lead to unexpected behavior.
Network connectivity is required for API calls.