Skip to main content
Glama

Elfa MCP

Model Context Protocol server for the Elfa API — API v3 events, positions and rankings across crypto and equities, Auto, a condition engine that watches the market and fires an action when your conditions are met, plus crypto social intelligence from X and Telegram.

Works with any MCP client, either signed in to the hosted server or running locally with an API key.

Install

Hosted, sign in with Elfa

Add https://mcp.elfa.ai/mcp as a remote MCP server in your client and approve it in your browser with your dev.elfa.ai account. No key to copy, nothing to install. If your client cannot sign in, run the server locally instead. Setup steps are in the MCP guide.

Local, API key

Get an API key at dev.elfa.ai. No install step — npx fetches the server on demand.

One click

Add to Cursor Add to VS Code

Claude Desktop

Download elfa-mcp-<version>.mcpb from the latest release and open it. Claude Desktop installs it, prompts for your API key, and keeps it updated. Nothing else to configure.

Claude Code

claude mcp add elfa --env ELFA_API_KEY=your-key -- npx -y @elfa-ai/mcp

Cursor, VS Code, Claude Desktop, and other clients

{
  "mcpServers": {
    "elfa": {
      "command": "npx",
      "args": ["-y", "@elfa-ai/mcp"],
      "env": {
        "ELFA_API_KEY": "your-key"
      }
    }
  }
}

VS Code uses "servers" instead of "mcpServers". Everything else is the same.

Ask "what's trending in crypto right now?" to confirm it works.

Related MCP server: onchain-safety-mcp

Configuration

Variable

Required

Purpose

ELFA_API_KEY

yes

Authenticates every request

ELFA_TIMEOUT

no

Request timeout in ms, default 120000

ELFA_RETRIES

no

Retries on failure, default 0

ELFA_MCP_MAX_RESPONSE_CHARS

no

Response size ceiling, default 60000

ELFA_EXTRA_HEADERS

no

JSON object of extra headers to send upstream, for proxies and non-production environments

Upstream requests identify themselves as User-Agent: elfa-mcp/<version> (<transport>; client=<app>). On stdio, <app> is the MCP client's name and version from the handshake; over HTTP, it is the connecting client's own User-Agent header. Set User-Agent in ELFA_EXTRA_HEADERS to send your own instead.

The timeout is high and retries are off on purpose. The interpretation endpoints are LLM-backed and can take over a minute, and they cost credits per attempt, so a silent retry would bill you again for a call you never saw. Raise ELFA_RETRIES only if you are calling the cheap measurement endpoints.

Some MCP clients apply their own timeout, often around 60 seconds. narratives and market_chat can exceed that; the request still completes and is still charged, even if the client gives up first.

Tools

16 tools, mapped to every documented /v2 and /v3 operation.

Tool

Mode

Cost

What it does

api_status

read

Free

Check API key tier, credit usage and remaining requests, and historyFrom, how far back events, market and calls read. Also confirms the API is reachable.

entities

read

1 per call

Resolve a ticker, $cashtag, name, @handle, contract address, CoinGecko id, FIGI or CIK to the entity id that events and calls take. Matches exactly, it is not a search.

events

read

1, plus 1 per event or 2 per storyline or arc

What is happening in crypto and equity markets. level=events for what happened and how prices reacted, level=storylines for one development threaded over days, level=arcs for storylines grouped into a larger movement. Searchable by topic.

market

read

call_book 2, mindshare 5, trending_contracts 5 (plus 5 over a 24 hour range), doubled for limit over 50

Whole-market views for crypto or equities. view=mindshare ranks assets by share of attention, view=call_book is the crowd's long/short lean hour by hour, view=trending_contracts ranks contract addresses by how many posts pasted them.

calls

read

1, plus 1 per call or 2 per episode; positioning 2

Positions accounts take in posts. level=calls for each post that takes or changes a position, level=episodes for each position from open to close with the author's track record, level=positioning for open longs and shorts on one asset now.

top_accounts

read

5 by standing, 25 by a track metric, doubled for limit over 50

X accounts ranked by standing (how much other accounts engage with them) or, with metric, by their track record as callers (alphaScore, hitRate, avgReturn).

auto_build

read

1 plus LLM usage

Turn a plain-language monitoring request into an EQL query. Returns a draft to validate and activate, it does not activate anything itself.

auto_validate

read

Free

Check EQL syntax and get a cost estimate before activating, or check that a symbol has market data on a venue.

auto_query

read

Free

Read side of Auto: list queries, poll one query, and read its executions and LLM sessions.

auto_query_write

write

5 plus LLM usage to create, free to cancel or delete

Activate, cancel or delete an Auto query. Activated queries run unattended and fire their action when conditions are met.

auto_draft

read

Free

Read side of Auto drafts: list saved drafts and read one. Drafts are queries parked without activating; they never evaluate or fire.

auto_draft_write

write

Free, except convert which costs the same as creating a query

Create, update, delete or activate an Auto draft. Converting a draft activates it as a live query that runs unattended.

mentions

read

1 per call

Social mentions from X and Telegram. mode=top ranks a ticker's mentions by engagement, mode=search filters by keyword or account, mode=news returns the token news feed, which is X posts from accounts tagged as news sources rather than articles from news outlets.

trending

read

1 per call

What is gaining social attention. scope=tokens for tickers, scope=contracts_twitter or scope=contracts_telegram for contract addresses.

narratives

read

5 per call

Written narrative analysis with source links. scope=market extracts market-wide narratives, scope=keywords summarises events for specific keywords.

market_chat

read

Varies by speed

Ask for written market analysis. Supports conversational chat, macro overview, quick summary, token intro, token analysis and account analysis.

Not exposed as tools:

  • chat-stream-v2 — A tool call returns one result, so streaming adds nothing. market_chat covers the same analysis.

  • auto-stream-queries-v2 — Long lived streams have no tool equivalent. Poll with auto_query.

  • auto-stream-query-v2 — Long lived streams have no tool equivalent. Poll with auto_query.

  • getAccountSmartStats-v2 — Deprecated and not maintained, so no tool wraps it. To rank accounts, use top_accounts; mentions with mode=search returns per-post engagement metrics with the posting account.

Some tools depend on the plan: today market_chat, which needs a higher-tier plan than the free one, and the API v3 tools on a key whose scopes leave them out. At startup (stdio) or per request (HTTP, cached for a minute per key), the server reads the key's scopes from /v2/key-status. A tool the plan doesn't include stays listed, but its description says it needs a higher-tier plan, and calling it returns the upgrade link without calling the API or spending credits. If the scopes can't be read within 3 seconds, every tool is listed as usual and the API decides.

Streaming endpoints stay available through the SDKs for applications that can consume SSE.

API v3

entities, events, market, calls and top_accounts read API v3: events, storylines and arcs; call books, mindshare and trending contracts; calls, call episodes and positioning; ranked accounts. They cover crypto and equities and are open to every plan. Each call costs credits, priced per endpoint on the pricing page.

  • Filters take entity ids, not tickers. Resolve an asset with entities first and reuse the id.

  • Times are unix seconds. Milliseconds are refused.

  • How far back a key reads depends on its plan. api_status returns it as historyFrom.

Where this differs from the raw API

The tools deliberately do not inherit every API default, because an agent pays for verbosity in context.

API

Here

Why

pageSize

10 to 50 depending on endpoint, max 100

10

Page through rather than pull everything

limit on v3 tools

10 or 50 depending on endpoint, max 30 or 200

10

Page with cursor rather than pull everything

speed on chat

expert

fast

Cheaper by default, ask for expert when depth matters

Mention fields

full record

high signal fields

Pass verbosity: "detailed" for the rest

Large responses

returned whole

trimmed to fit, with a note

Keeps one call from filling the context window

Every value is still settable per call: pageSize accepts up to 100, and limit up to the endpoint's maximum.

Auto

Auto queries run unattended. Once armed, a query keeps evaluating and fires its action without asking again.

The flow is three steps:

  1. auto_build — describe what to watch in plain language, get EQL back

  2. auto_validate — check the syntax and get the credit cost

  3. auto_query_write — activate it

Actions can notify you, call a webhook, message a Telegram bot, or run an LLM analysis.

There is no push channel over MCP. Poll auto_query with method=get, and wait for the returned pollAfterSeconds between calls.

Remote server

The same server runs over Streamable HTTP for hosted deployments:

ELFA_MCP_TRANSPORT=http ELFA_MCP_PORT=3000 npx -y @elfa-ai/mcp

It is stateless — no sessions, one server instance per request, safe behind a load balancer. Credentials come from the x-elfa-api-key request header, falling back to the environment, or from an OAuth sign-in (see below).

DNS rebinding protection is on by default. The server accepts only the loopback names it binds — localhost:PORT and 127.0.0.1:PORT — which covers the local run above and nothing else. Any deployment that answers on a different Host must list the values it serves:

ELFA_MCP_ALLOWED_HOSTS=mcp.example.com

That includes a public domain, a reverse proxy, and a container that maps the port to a different one than the server binds. A Host the list does not cover is rejected with 403.

Variable

Required

Purpose

ELFA_MCP_TRANSPORT

no

http to serve over Streamable HTTP, default stdio

ELFA_MCP_HOST

no

Bind address, default 127.0.0.1

ELFA_MCP_PORT

no

Bind port, default 3000

ELFA_MCP_ALLOWED_HOSTS

no

Comma separated Host allowlist, defaults to the loopback names bound

ELFA_MCP_ALLOWED_ORIGINS

no

Comma separated Origin allowlist

ELFA_MCP_OPENAI_APPS_CHALLENGE

no

Domain-verification token from OpenAI's plugin portal, served as plain text at /.well-known/openai-apps-challenge

Set ELFA_MCP_ALLOWED_ORIGINS as well when browsers call the server directly. It complements the host allowlist rather than replacing it: a rebound request is same origin, so it carries no Origin header for that list to check, and the Host header is the only one still naming the attacker's domain.

OAuth sign-in

A hosted server can let clients sign in through a browser instead of sending an API key. Set ELFA_MCP_AUTH=oauth and the server becomes an OAuth resource server under the MCP authorization spec:

  1. A request with no credential gets 401 and a WWW-Authenticate challenge.

  2. The challenge points the client to the protected-resource metadata at /.well-known/oauth-protected-resource/mcp.

  3. That metadata names the authorization server, where the user signs in.

  4. The client then sends Authorization: Bearer <token>.

  5. The server checks the token against the authorization server's introspection endpoint. The endpoint answers with the Elfa API key the request runs as, so the token never reaches the Elfa API.

ELFA_MCP_TRANSPORT=http \
ELFA_MCP_AUTH=oauth \
ELFA_MCP_RESOURCE_URL=https://mcp.example.com/mcp \
ELFA_OAUTH_ISSUER=https://auth.example.com \
ELFA_OAUTH_INTROSPECTION_URL=https://auth.example.com/introspect \
ELFA_OAUTH_INTROSPECTION_TOKEN=... \
ELFA_MCP_ALLOWED_HOSTS=mcp.example.com \
npx -y @elfa-ai/mcp

Variable

Required in OAuth mode

Purpose

ELFA_MCP_AUTH

yes

oauth to enable, default apikey

ELFA_MCP_RESOURCE_URL

yes

Canonical URL of this endpoint. Tokens must be issued for exactly this value

ELFA_OAUTH_ISSUER

yes

Authorization server listed in the metadata

ELFA_OAUTH_INTROSPECTION_URL

yes

Where tokens are checked

ELFA_OAUTH_INTROSPECTION_TOKEN

yes

Bearer sent to the introspection endpoint

ELFA_OAUTH_SCOPES

no

Comma separated scopes to advertise, default elfa

Notes:

  • An x-elfa-api-key header still works in OAuth mode.

  • ELFA_API_KEY is ignored in OAuth mode, so a caller with no credential never runs as the server's own key.

  • Valid tokens are cached for up to a minute, which bounds how long a revoked token keeps working.

Safety

api_status is the fastest way to tell an auth problem from a credit problem.

Mentions, news and narratives return third-party social text that anyone can write, events are written up from it, and the v3 tools carry third-party asset, account and channel names. The server marks it as untrusted in every response, and the server instructions tell the model to treat it as data. Keep that in mind before letting an agent chain from that content into auto_query_write.

Development

npm install
npm run build
npm run verify

npm run verify runs typecheck, tests, the spec drift check, and the docs check.

manifest.json maps every documented API operation to the tool that covers it. npm run check:drift fails if the API grows an operation the server does not handle. The tool table above is generated from the same file with npm run docs:tools.

License

MIT

Available Tools

16 tools
api_statusAPI key statusA
Read-onlyIdempotent

Check the Elfa API key tier, credit usage and remaining requests, and confirm the API is reachable. Free. historyFrom is the earliest time, in unix seconds, the events, market and calls tools read on this plan.

Inputs: no named parameters. Returns: key, problem, reachable, historyFrom

auto_buildAuto query builderA
Read-only

Turn a plain-language monitoring request into an EQL query. Costs 1 credit plus LLM usage. This only drafts the query: nothing runs until it is activated. Say what to watch, the threshold, and what should happen when it fires. It drafts tweet conditions only for accounts in Elfa's real-time set (included), not for other X accounts.

Inputs: message (required), speed, sessionId. Returns: title, planIds, response, reasoning, +1 more

auto_draftRead Auto draftsA
Read-onlyIdempotent

Read side of Auto drafts. Free. method=list browses saved drafts, method=get returns one draft. A draft is an Auto query parked without activating it: it never evaluates and never fires.

Inputs: method (required), limit, offset, search, +2 more. Returns: data, method

auto_draft_writeWrite Auto draftsA
Destructive

Create, update, delete or activate an Auto draft. method=upsert parks a query as a draft without activating it; drafts never evaluate and never fire. method=delete removes a draft. method=convert activates a draft as a live query, which runs unattended and fires its action without asking again, and costs the same as creating a query. upsert and delete are free.

Inputs: method (required), query, title, draftId, +1 more. Returns: data, method

auto_queryRead Auto queriesA
Read-onlyIdempotent

Read side of Auto. Free. method=list browses queries, method=get polls one query and returns its latest evaluation, plus failure when it failed with a recorded reason, method=executions and method=execution show what fired, method=sessions and method=session return the LLM analysis attached to a query. There is no push channel here, poll with method=get and respect pollAfterSeconds.

Inputs: method (required), type, limit, offset, +5 more. Returns: data, method, pollAfterSeconds

auto_query_writeWrite Auto queriesA
Destructive

Activate, cancel or delete an Auto query. Creating costs 5 credits plus LLM usage, cancel and delete are free. An activated query runs unattended and fires its action without asking again. Per-post X accounts in its tweet conditions and per-day accounts in its x_follow_made or x_follow_overlap conditions are billed on top while it runs.

Inputs: method (required), query, title, queryId, +1 more. Returns: data, method

auto_validateValidate Auto queryA
Read-onlyIdempotent

Check EQL syntax and get the estimated cost of activating a query. Free. tweetAccounts lists the X account behind each tweet condition: billing=per_post accounts cost creditsPerPost for every post from the account (not replies or reposts), matched or not, while the query runs, on top of estimatedCredits. followAccounts lists the X account behind each x_follow_made or x_follow_overlap condition: billing=per_day accounts cost creditsPerDay for each UTC day their follows are read while the query runs, also on top of estimatedCredits. Pass either an inline query or a draftId. method=symbol instead checks that a symbol has market data on a venue, which price and ta conditions need.

Inputs: query, title, method, symbol, +3 more. Returns: valid, errors, warnings, tweetAccounts, +2 more

callsCallsA
Read-onlyIdempotent

What accounts are doing: positions taken in posts on X and Telegram.. level=calls: each post that opened, added to, trimmed, reaffirmed, reversed, closed or stopped out of a position. level=episodes: each position from open to close, with entry and exit prices and the author's track record. level=positioning: open longs and shorts on one asset right now. level=episodes with status=open and from set to now reads what every matching account holds right now. Not returned: post text or a recommendation.

Inputs: to, ids, from, level, +9 more. Returns: items, level, notice, hasMore, +2 more

entitiesEntitiesA
Read-onlyIdempotent

Turn a ticker, $cashtag, name, @handle, contract address, CoinGecko id, FIGI or CIK into the entity id that events and calls take.. It matches exactly, it is not a search: a prefix or a misspelling returns nothing. A ticker is not unique, so take the first row and check its name, or narrow with entityType. Forms of an asset share one family id where known: WBTC and cbBTC are Bitcoin. Resolve once and reuse the id.

Inputs: q (required), limit, cursor, entityType. Returns: items, notice, hasMore, nextCursor

eventsEventsA
Read-onlyIdempotent

What is happening in crypto and equity markets, written up from posts across many sources.. level=events: what happened, what it names, how prices reacted where measured (impacts is empty on most events), and the posts behind it. level=storylines: the events of one development, threaded over days. level=arcs: storylines grouped into a larger movement. Search any level by topic with q, filter by asset with entityIds from the entities tool, or fetch up to 30 you hold with ids. Not returned: post text, a sentiment score or a price.

Inputs: q, to, ids, from, +17 more. Returns: items, level, notice, hasMore, +2 more

marketMarketA
Read-onlyIdempotent

Whole-market views, no asset needed.. view=mindshare ranks assets by share of attention over a period, with hot on those heating up. view=call_book is the crowd's long/short lean, one bar per hour plus a live tick: read crowdingPercentile rather than longShare, since the accounts lean long almost always. view=trending_contracts ranks contract addresses by how many posts pasted them, crypto only, and the unnamed ones are often the ones worth watching.

Inputs: to, from, view, limit, +5 more. Returns: view, items, market, notice, +3 more

market_chatMarket chatA
Read-only

Ask Elfa for written market analysis grounded in its social data. Costs credits and varies by speed, so fast is the cheaper option. Pass sessionId from a previous reply to continue the same conversation. The reply includes sources: links to the posts and pages the research read (links only, not their text), so you can cite or check them.

Inputs: chain, speed, symbol, message, +5 more. Returns: message, sources, sessionId, creditsConsumed

mentionsMentionsA
Read-onlyIdempotent

Social mentions from X and Telegram. 1 credit per call. Returns engagement metrics and a link per post, not the post text. mode=top ranks one ticker's mentions by engagement. mode=search filters by keywords or by account. mode=news returns the token news feed, which is X posts from accounts tagged as news sources rather than articles from news outlets.

Inputs: mode (required), to, from, page, +11 more. Returns: mode, next, total, notice, +1 more

narrativesNarrativesA
Read-onlyIdempotent

Written narrative analysis with source links, for when counts are not enough. 5 credits per call. scope=market extracts the narratives moving the market. scope=keywords summarises events for keywords you supply, and can take over a minute to return.

Inputs: to, from, scope, keywords, +5 more. Returns: note, items, scope, notice, +1 more

top_accountsTop accountsA
Read-onlyIdempotent

X accounts ranked by standing (how much other accounts engage with them) or, with metric, by their track record as callers.. Standing measures attention, not accuracy; track is null for an account that has never opened a position. For the best callers use metric=alphaScore, not avgReturn, which a few big wins or a rally can top. Track metrics rank only accounts with at least 20 scored positions, over every position since late June 2026; scoredEpisodes is the number of positions behind each account's track metrics.

Inputs: limit, order, cursor, metric. Returns: items, notice, hasMore, nextCursor

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 16 tools

    Disambiguation3/5

    The Auto tools are mostly separable by read/write and draft/query roles, but auto_draft_write convert overlaps auto_query_write activation. Social-attention tools such as mentions, trending, and market mindshare, plus written-analysis tools such as narratives and market_chat, have overlapping boundaries that require close reading to distinguish.

    Naming Consistency3/5

    All names use readable snake_case and the auto_* family has a useful _write suffix pair, but the set mixes bare resource nouns (events, calls, entities) with action-like names (auto_build, auto_validate, market_chat). There is no single predictable verb_noun pattern throughout.

    Tool Count4/5

    Sixteen tools is slightly above the typical 3-15 range, but the surface covers a broad domain: Auto lifecycle, drafts, validation, entity resolution, social reads, market views, and API status. Each tool has a plausible role, though the Auto group is somewhat heavy.

    Completeness4/5

    The set covers the core lifecycle well: build, validate, draft, activate, cancel, and delete Auto queries, plus entity resolution and multiple social/market read paths. Minor gaps include no raw post text and no direct price-series tool, but these appear intentionally out of scope and can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides AI agents with crypto token safety checks (honeypot, liquidity, rug risk) and alpha signals (smart money buys, fresh rug radar) across PulseChain, Monad, Base, and BSC.
      94 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server that exposes QuantXData's institutional crypto market data APIs to AI assistants, enabling natural language queries for trades, order books, OHLCV, options, and more across 120+ exchanges.
      12
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for accessing crypto market data (prices, portfolio analytics) from CoinGecko and performing RAG-based search over internal documents with responsible-AI guardrails.
      4
      MIT