Where it fits
Agents and users checking Solana DeFi positions, tokens, and swaps with a free account key.
- Create a Dexra key and send it as a Bearer token.
- Check a token launch and its holders.
- Run swap preflight and review the evidence.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Dexra
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Investigates a question against high-trust primary sources and records the findings in a Markdown file inside the repo. Use it when a topic needs research, docs or API facts need gathering, or reading legwork should go to a background agent.
Show recorded token use, cache reads, and mode attribution for the current Claude Code session.
Improves application speed across the frontend, backend, database, and query layers. Reach for it when a performance target exists, a regression is suspected, Core Web Vitals or load times need work, N+1 queries need fixing, or profiling has exposed a bottleneck.
No skills found
Try a different search term or clear the filters.
Keyed install
Dexra requires an API key. Create a free account, then pass the dxr_ key to the installer or send it as Authorization: Bearer dxr_... in client config.
- Create a Dexra key
Sign in to Dexra and create an API key that starts with dxr_.
- Run the keyed installer
Run npx -y @dexra-dev/mcp install --key dxr_YOUR_KEY, or add the endpoint with the Authorization header.
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name dexra. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
dexraappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Create a Dexra key and send it as a Bearer token. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
- The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Dexra documentationhttps://dexra.dev/