Skip to content

Add DexPaprika MCP and CoinPaprika MCP to MCP Servers#32

Open
donbagger wants to merge 1 commit intojmanhype:mainfrom
donbagger:add-coinpaprika-dexpaprika-mcp
Open

Add DexPaprika MCP and CoinPaprika MCP to MCP Servers#32
donbagger wants to merge 1 commit intojmanhype:mainfrom
donbagger:add-coinpaprika-dexpaprika-mcp

Conversation

@donbagger
Copy link
Copy Markdown

Adds two free crypto data MCP servers:

  • DexPaprika MCP — DEX data across 34 chains, 30M+ pools. Free, no auth needed.
  • CoinPaprika MCP — 12K+ coins, 350+ exchanges, tickers, OHLCV. Free, no auth needed.

@qodo-code-review
Copy link
Copy Markdown

Review Summary by Qodo

Add DexPaprika and CoinPaprika MCP servers to registry

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Add DexPaprika MCP server for DEX data across 34 chains
• Add CoinPaprika MCP server for crypto market data
• Both servers are free with no authentication required
Diagram
flowchart LR
  MCP["MCP Servers Registry"]
  DEX["DexPaprika MCP<br/>DEX data: 34 chains, 30M+ pools"]
  COIN["CoinPaprika MCP<br/>Crypto data: 12K+ coins, 350+ exchanges"]
  MCP -- "adds" --> DEX
  MCP -- "adds" --> COIN
Loading

Grey Divider

File Changes

1. README.md 📝 Documentation +2/-0

Add two free crypto data MCP servers

• Added DexPaprika MCP entry with DEX data capabilities across 34 chains and 30M+ pools
• Added CoinPaprika MCP entry with crypto market data for 12K+ coins and 350+ exchanges
• Both entries marked as free with no authentication required

README.md


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Copy Markdown

qodo-code-review bot commented Mar 31, 2026

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider


Remediation recommended

1. Status table out-of-date 🐞 Bug ≡ Correctness
Description
After adding two MCP servers, the README Status section still reports "MCP servers | 5" and an older
"Last updated" value, so the summary no longer matches the actual list. This makes the README’s
quick-glance metrics misleading.
Code

README.md[R43-44]

+| [DexPaprika MCP](https://github.com/coinpaprika/dexpaprika-mcp) | None (free) | DEX data: 34 chains, 30M+ pools, tokens, OHLCV, trades |
+| [CoinPaprika MCP](https://github.com/coinpaprika/coinpaprika-mcp) | None (free) | Crypto market data: 12K+ coins, 350+ exchanges, tickers |
Evidence
The Status table still lists 5 MCP servers and an older last-updated quarter, while the MCP Servers
table now contains 7 entries including the two newly added rows.

README.md[7-14]
README.md[34-45]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The README Status table is now inconsistent with the MCP Servers table after adding DexPaprika and CoinPaprika.

### Issue Context
The MCP Servers table has 7 entries, but the Status section still says 5, and the "Last updated" quarter is stale.

### Fix Focus Areas
- README.md[7-14]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Advisory comments

2. MCP table order broken 🐞 Bug ⚙ Maintainability
Description
The MCP Servers table is in alphabetical order, but the new CoinPaprika and DexPaprika rows are
appended after Supabase, breaking the established ordering. This makes the list harder to scan and
maintain.
Code

README.md[R43-44]

+| [DexPaprika MCP](https://github.com/coinpaprika/dexpaprika-mcp) | None (free) | DEX data: 34 chains, 30M+ pools, tokens, OHLCV, trades |
+| [CoinPaprika MCP](https://github.com/coinpaprika/coinpaprika-mcp) | None (free) | Crypto market data: 12K+ coins, 350+ exchanges, tickers |
Evidence
Existing entries are alphabetically ordered (Atlassian, GitHub, Google Workspace, Notion, Supabase);
the newly added CoinPaprika and DexPaprika entries should be placed between Atlassian and GitHub to
preserve that order.

README.md[36-45]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
New MCP server rows are not placed in the table’s existing alphabetical order.

### Issue Context
Current order is Atlassian, GitHub, Google Workspace, Notion, Supabase, then the new entries; alphabetically, CoinPaprika and DexPaprika should appear after Atlassian and before GitHub.

### Fix Focus Areas
- README.md[36-45]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant