Stream Social Metrics for Trading
LunarCrush's remote MCP server giving AI assistants access to LunarCrush's social/crypto market intelligence, via HTTP or stdio.
Maintainer of this project? Claim this page to edit the listing.
1.0.0Add to Favorites
Why it matters
Access real-time and historical social media metrics and posts from LunarCrush. Optimize data for LLMs and token usage to power automated trading and financial advisory applications.
Outcomes
What it gets done
Fetch current social metrics and posts via HTTP or SSE.
Retrieve historical social data for in-depth analysis.
Format data for LLM consumption and token efficiency.
Integrate social insights into automated trading strategies.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-lunarcrush-remote-mcp | bash Overview
LunarCrush Remote MCP Server
LunarCrush Remote MCP Server connects an AI assistant to LunarCrush's social and crypto market intelligence via hosted HTTP/SSE or local stdio, authenticated with a LunarCrush API key. Use the hosted remote endpoint when possible for LunarCrush AI-assisted market intelligence; requires a valid LunarCrush API key in all configurations.
What it does
LunarCrush Remote MCP Server connects an AI assistant to LunarCrush's AI and market intelligence capabilities via the Model Context Protocol. It is offered as a hosted remote server (Streamable HTTP at https://lunarcrush.ai/mcp, or SSE at https://lunarcrush.ai/sse), which is the preferred connection method, or as a local stdio server run from source with a LunarCrush API key.
When to use - and when NOT to
Use this connector when you want an assistant to tap into LunarCrush's social and crypto market intelligence data through a standard MCP connection, preferring the hosted remote endpoint over running a local server when possible.
Do not use it without a valid LunarCrush API key - authentication (a bearer token for the remote server, or LUNARCRUSH_API_KEY for the local stdio server) is required in every configuration.
Inputs and outputs
Connection is configured via a bearer token (remote HTTP/SSE) or the LUNARCRUSH_API_KEY environment variable (local stdio). Specific tool inputs/outputs are defined by LunarCrush's AI/MCP capabilities documented at lunarcrush.com/developers/api/ai.
Capabilities
- Remote hosted access via Streamable HTTP (
https://lunarcrush.ai/mcp) or SSE (https://lunarcrush.ai/sse) - Local stdio server option for running from source
- Bearer-token or API-key authentication against a LunarCrush account
How to install
Remote (preferred), Streamable HTTP:
{
"mcpServers": {
"LunarCrush": {
"type": "http",
"url": "https://lunarcrush.ai/mcp",
"headers": { "Authorization": "Bearer ${input:lunarcrush-api-key}" }
}
}
}
Or local stdio:
{
"mcpServers": {
"LunarCrush": {
"command": "node",
"args": ["<absolute_path_to_project_root>/index.js"],
"env": { "LUNARCRUSH_API_KEY": "<your_lunarcrush_api_key>" }
}
}
}
Get an API key at lunarcrush.com/developers/api/authentication.
Who it's for
Crypto and social-market researchers who want an AI assistant connected to LunarCrush's intelligence data via MCP.
Source README
More information on using LunarCrush AI & MCP Capabilities here: https://lunarcrush.com/developers/api/ai
LunarCrush Remote MCP Server (preferred)
Streamable HTTP
{
"mcpServers": {
"LunarCrush": {
"type": "http",
"url": "https://lunarcrush.ai/mcp",
"headers": {
"Authorization": "Bearer ${input:lunarcrush-api-key}"
}
}
}
}
SSE
{
"mcpServers": {
"LunarCrush": {
"type": "http",
"url": "https://lunarcrush.ai/sse",
"headers": {
"Authorization": "Bearer ${input:lunarcrush-api-key}"
}
}
}
}
LunarCrush stdio MCP Server
{
"mcpServers": {
"LunarCrush": {
"command": "node",
"args": ["<absolute_path_to_project_root>/index.js"],
"env": {
"LUNARCRUSH_API_KEY": "<your_lunarcrush_api_key>",
}
}
}
}
Authentication / API Key
Get your LunarCrush API keys here: https://lunarcrush.com/developers/api/authentication
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.