CCXT
Official CCXT MCP server - Market data and trading across 100+ exchanges and prediction markets
Governed AI-agent memory, Evidence Ledger traces, evals, and portable context tools.
Pick the AI app you use, then copy the settings.
Passed 2/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Lore Context key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
One time only; it works for every server that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
SettingsDeveloperEdit Config
{
"mcpServers": {
"lore-context": {
"command": "npx",
"args": [
"-y",
"@lore-context/server"
],
"env": {
"LORE_API_URL": "your-value",
"LORE_API_KEY": "your-value",
"LORE_MCP_TRANSPORT": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Lore Context and tell me what you can do for me, then show me one thing✓ If Claude says it is using Lore Context or shows a Lore Context tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Lore Context yet
Lore Context runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Lore Context
B · Others in Accounting, finance & tax that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Lore Context key (create it on the maker’s site) · Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user lore-context --env LORE_API_URL=your-value --env LORE_API_KEY=your-value --env LORE_MCP_TRANSPORT=your-value -- npx -y @lore-context/serverReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Lore Context listed as connected
Use Lore Context and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Lore Context or shows a Lore Context tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Lore Context key (create it on the maker’s site) · Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Lore Context settings, LORE_API_URL, LORE_API_KEY, LORE_MCP_TRANSPORT is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Lore Context and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Lore Context or shows a Lore Context tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Lore Context key (create it on the maker’s site) · Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Lore Context settings, LORE_API_URL, LORE_API_KEY, LORE_MCP_TRANSPORT is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Lore Context and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Lore Context or shows a Lore Context tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user lore-context --env LORE_API_URL=your-value --env LORE_API_KEY=your-value --env LORE_MCP_TRANSPORT=your-value -- npx -y @lore-context/serverClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"lore-context": {
"command": "npx",
"args": [
"-y",
"@lore-context/server"
],
"env": {
"LORE_API_URL": "your-value",
"LORE_API_KEY": "your-value",
"LORE_MCP_TRANSPORT": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"lore-context": {
"command": "npx",
"args": [
"-y",
"@lore-context/server"
],
"env": {
"LORE_API_URL": "your-value",
"LORE_API_KEY": "your-value",
"LORE_MCP_TRANSPORT": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"lore-context": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@lore-context/server"
],
"env": {
"LORE_API_URL": "your-value",
"LORE_API_KEY": "your-value",
"LORE_MCP_TRANSPORT": "your-value"
}
}
}
}LORE_API_URL required envLORE_API_KEY secret envLORE_MCP_TRANSPORT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @lore-context/serveroci: ghcr.io/lore-context/lore-context-mcp:0.6.0-alpha.1Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 12, 2026
The registry name was verified with the GitHub account Lore-Context, which owns the repo
Code last changed 31 days ago
GitHub could not identify the licence type; open the file to check
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: LORE_API_URL, LORE_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 31 days ago, and the latest version (0.6.0-alpha.1) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: CCXT, Finance Toolkit, AKQuant
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Official CCXT MCP server - Market data and trading across 100+ exchanges and prediction markets
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Write and backtest trading strategies with AKQuant: API lookup, strategy checks, backtest runs
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The control plane for AI-agent memory, eval, and governance.
Know what every agent remembered, used, and should forget — before memory becomes production risk.
Getting Started · Website Quickstart · Benchmark Methodology · API Reference · Architecture · Project Plan · Release Status · Roadmap · Integrations · Deployment · Changelog
🌐 Read this in your language: English · 简体中文 · 繁體中文 · 日本語 · 한국어 · Tiếng Việt · Español · Português · Русский · Türkçe · Deutsch · Français · Italiano · Ελληνικά · Polski · Українська · Bahasa Indonesia
Localized docs may lag the current English release notes; the canonical v2.1 docs are the English README and docs/ set.
Lore Context is an open-core control plane for AI-agent memory: it composes context across memory, search, repository graphs, and tool traces; evaluates retrieval quality on your own datasets; routes governance review for sensitive content; and exports memory as a portable interchange format you can move between backends.
It does not try to be another memory database. The unique value is what sits on top of memory:
candidate / active / flagged / redacted / superseded / deleted), risk-tag scanning, poisoning heuristics, immutable audit log.provenance / validity / confidence / source_refs / supersedes / contradicts. Works as a migration format between memory backends.agentmemory integration with version probe + degraded-mode fallback; clean adapter contract for additional runtimes.| Use Lore Context when... | Use a memory database (agentmemory, Mem0, Supermemory) when... |
|---|---|
| You need to prove what your agent remembered, why, and whether it was used | You just need raw memory storage |
| You run multiple agents (Claude Code, Cursor, Qwen, Hermes, Dify) and want shared trustable context | You're building a single agent and OK with a vendor-locked memory tier |
| You require local or private deployment for compliance | You prefer a hosted SaaS |
| You need eval on your own datasets, not vendor benchmarks | Vendor benchmarks are sufficient signal |
| You want to migrate memory between systems | You don't plan to ever switch backends |
# 1. Clone + install
git clone https://github.com/Lore-Context/lore-context.git cd lore-context && pnpm install
pnpm quickstart -- --dry-run --activation-report
export LORE_API_KEY=$(openssl rand -hex 32)
pnpm build && PORT=3000 LORE_STORE_PATH=./data/lore-store.json pnpm start:api
curl -H "Authorization: Bearer $LORE_API_KEY" -H "Content-Type: application/json" \ -X POST http://127.0.0.1:3000/v1/memory/write \ -d '{"content":"Use RDS as truth store and Qdrant as the derived recall index for Lore Context production.","memory_type":"project_rule","project_id":"demo"}'
curl -H "Authorization: Bearer $LORE_API_KEY" -H "Content-Type: application/json" \ -X POST http://127.0.0.1:3000/v1/context/query \ -d '{"query":"production storage","project_id":"demo","token_budget":1200}'
For the public website quickstart, see lorecontext.com/quickstart. For full setup (Postgres, Docker Compose, Dashboard, MCP integration), see docs/getting-started.md.
The canonical alpha quickstart is git clone + pnpm quickstart. Lore does not currently publish or claim a public @lore-context/quickstart npm package. The MCP stdio server is published separately as @lore-context/server for registry and client distribution, and the SDK middleware ships as @lore-context/sdk-middleware (npm) and lore-context-middleware (PyPI).
For AI-readable discovery, the website publishes /llms.txt and /llms-full.txt from public documentation only. The Official MCP Registry entry is published, and additional distribution drafts live under docs/distribution. Launch drafts live under docs/launch, and design partner intake under docs/design-partners. The public benchmark page is a reproducible methodology and small smoke-run report, not a competitive benchmark-win claim.
The diagram below shows the full open-core plus hosted-production shape. In the public OSS repo, local file/Postgres deployment is supported directly; hosted Google sign-in, AWS SQS workers, private embeddings, billing, and multi-tenant operations are commercial hosted-cloud surfaces.
┌───────────────────────────────────────────────┐
MCP/REST clients ─► │ apps/api (auth + rate limit + evidence) │ (Claude Code, │ ├── Memory Inbox / lifecycle / audit │ Codex, Cursor, │ ├── capture ingestion + recall hydration │ OpenCode...) │ ├── context query (memory/web/repo/traces) │ │ ├── repo graph query / symbol / impact │ │ ├── Google sign-in + hosted MCP metadata │ │ └── OpenAPI + usage + operator surfaces │ └───────────────┬───────────────────────────────┘ │ capture / embedding / graph jobs ▼ ┌───────────────────────────────────────────────┐ │ memory-worker (AWS SQS + DLQ fan-out) │ │ ├── auto redaction / curation / save │ │ ├── dreaming butler (prune/merge/resolve) │ │ ├── private Qwen3 embedding service │ │ └── Qdrant dense+sparse indexing │ └───────────────┬───────────────────────────────┘ │ ┌────────────────────┼────────────────────┐ ▼ ▼ ▼ RDS PostgreSQL 16 Qdrant derived index apps/dashboard truth store + audit lore_memories_v12 user-facing SaaS
For detail, see docs/architecture.md.
v2.1.0 is the Repo Graph API and MCP Tools release. It makes Lore's own repository graph a first-class agent memory surface: deterministic TypeScript/JavaScript repository indexing for files, symbols, imports, calls, routes, tests, and process hints, exposed through API routes and read-only MCP tools so agents ground repository answers in a stable project-context contract instead of ad hoc text search.
v2.1.0 is the current open-core source line. The hosted Lore Cloud production line also runs v2.1.0 on the commercial AWS/Qdrant/private-embedding substrate, but hosted operations, billing, production release automation, and Secret Vault runtime stay in Lore-Context/lore-cloud.
| Capability | Status | Where |
|---|---|---|
Repo graph API + MCP tools (repo.graph_query / symbol_context / impact / detect_changes) | ✅ OSS + hosted production | packages/repo-graph, apps/api, apps/mcp-server |
| Code knowledge graph indexer | ✅ OSS + hosted production | packages/code-indexer, packages/code-indexer-python |
| Context Query composing memory + web + repo + tool traces | ✅ OSS + hosted production | apps/api, docs/api-reference.md |
7-stream HybridSearchOrchestrator (FTS / pgvector / Qdrant dense+sparse / graph / temporal / wiki) | ✅ OSS + hosted production | packages/search |
| Cross-encoder reranker (post-fusion, opt-in) | ✅ OSS, provider key required | apps/api/src/rerankers/ |
| Dreaming butler memory consolidation (prune / merge / resolve / surface) | ✅ OSS, flag-gated | apps/api/src/workers/butler-v18.ts |
| Agent memory self-improvement loop + context recipes | ✅ OSS, human-gated promotion | packages/eval, packages/search |
| SDK middleware (auto-inject + auto-retain for OpenAI / Anthropic clients) | ✅ Published | packages/sdk-middleware-typescript, packages/sdk-middleware-python |
| Generated SDK source previews | ✅ OSS source preview | packages/sdk-python, packages/sdk-go, packages/sdk-java, packages/sdk-dotnet |
| Browser extension capture scaffold | ✅ OSS scaffold | apps/browser-extension |
| Secret vault for AI agents (MCP-native, three-button authorization) | Hosted beta, pending crypto audit | commercial runtime in Lore-Context/lore-cloud |
| Cloud Memory Engine: RDS truth store + SQS worker fan-out + Qdrant index | Hosted production | commercial hosted cloud |
| Private Qwen3-Embedding-0.6B 1024-dim vector service | Hosted production | commercial hosted cloud |
| Automatic capture ingestion and Memory Inbox exceptions | ✅ OSS + hosted production | apps/api, packages/capture, apps/dashboard |
| Google sign-in + personal vault bootstrap | Hosted production | commercial hosted cloud |
| Commercial SaaS: individual subscriptions, billing, quota gating | Hosted production | Lore-Context/lore-cloud |
| REST API with API-key auth (reader/writer/admin) | ✅ OSS + hosted production | apps/api |
OpenAPI 3.1 contract at /openapi.json (reports 2.1.0) | ✅ OSS + hosted production | apps/api/src/openapi.ts |
| MCP stdio server (legacy + official SDK transport) | ✅ OSS + hosted production | apps/mcp-server |
| Next.js dashboard customer workflow scaffold | ✅ OSS scaffold + hosted production | apps/dashboard |
| Evidence Ledger API + Dashboard summary | ✅ OSS + hosted production | apps/api, apps/dashboard |
| Governance state machine + audit log | ✅ OSS + hosted production | `packages/g