Server data from the Official MCP Registry
Measure how AI engines cite your brand. Cross-engine GEO visibility, as agent tools.
Measure how AI engines cite your brand. Cross-engine GEO visibility, as agent tools.
Remote endpoints: streamable-http: https://lumind.io/mcp
Valid MCP server (5 strong, 3 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: LUMIND_AGENT_KEY
Environment variable: LUMIND_API_BASE
Environment variable: MCP_HTTP_PORT
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-lumind-mcp": {
"url": "https://lumind.io/mcp"
}
}
}From the project's GitHub README.
Make Lumind a native tool for any AI agent.
lumind-mcp is a Model Context Protocol server that
exposes the Lumind agentic-commerce platform as a handful of clean tools. Plug it into an
AI agent (Claude Desktop, an IDE, a custom agent) with a capped agent key, and the agent
can, in its own tool language, browse the Lumind service catalogue, check how much budget
it has left, launch a GEO/SEO scan on a domain, and read back the structured report.
AI agents are great at deciding what to do but need safe, well-described tools to actually do it. Lumind already runs the work (GEO/SEO scans) and the billing. This MCP server is the adapter between the two: every action goes through the agent's capped LUM key, so the agent can spend autonomously but can never exceed the budget the human set. The result is hands-off agentic commerce with a hard spending ceiling.
lmd_agent_...), a key the human created with a total
cap and a daily cap.lumind_run_scan is the only tool that spends LUM. It is money-first: budget is debited
when the scan is accepted, before any report is produced.idempotencyKey when retrying a scan so a retry never double-spends.| Tool | What it does | Spends LUM? |
|---|---|---|
lumind_list_services | List buyable services and their LUM cost. Call this first. | No |
lumind_wallet_balance | Show balance, total/daily caps, spent and remaining budget. Check before spending. | No |
lumind_run_scan | Launch a GEO/SEO scan on a domain (optional idempotencyKey). Returns scanId + reportToken. | Yes |
lumind_get_report | Fetch the structured JSON report for a scanId. | No |
Requires Node.js >= 18.
npm install
npm run build
The server reads its configuration from the environment:
| Variable | Required | Default | Used by | Notes |
|---|---|---|---|---|
LUMIND_AGENT_KEY | stdio only | , | stdio | Your capped agent key, form lmd_agent_.... Never hardcode it. Not used by the HTTP transport (each request carries its own key). |
LUMIND_API_BASE | no | https://lumind.io | both | Override to point at another Lumind environment. |
MCP_HTTP_PORT | no | 8120 | HTTP | TCP port the HTTP transport binds on 127.0.0.1. |
Add this to your MCP client config (e.g. claude_desktop_config.json), pointing args at the
built entrypoint:
{
"mcpServers": {
"lumind": {
"command": "node",
"args": ["/absolute/path/to/lumind-mcp/dist/index.js"],
"env": {
"LUMIND_AGENT_KEY": "lmd_agent_xxxxxxxxxxxxxxxx",
"LUMIND_API_BASE": "https://lumind.io"
}
}
}
}
After npm run build you can also run it directly:
LUMIND_AGENT_KEY=lmd_agent_xxxx node dist/index.js # stdio transport
The same four tools are also served over a remote Streamable HTTP endpoint, so any MCP client that supports remote servers can connect to a single URL with its own capped agent key , no local subprocess needed.
The key travels in each request's Authorization header (never a server env var), so one
HTTP server safely serves many isolated clients at once. Each request gets a fresh, stateless
session.
{
"mcpServers": {
"lumind": {
"type": "http",
"url": "https://mcp.lumind.io/mcp",
"headers": {
"Authorization": "Bearer lmd_agent_xxxxxxxxxxxxxxxx"
}
}
}
}
If the dedicated mcp.lumind.io host is not yet live, use the fallback path on the main
domain instead:
"url": "https://lumind.io/mcp"
Run the HTTP transport yourself:
npm run build
MCP_HTTP_PORT=8120 LUMIND_API_BASE=https://lumind.io node dist/http.js # binds 127.0.0.1
A minimal MCP initialize against the local endpoint (replace the key with a real one):
curl -s -X POST http://127.0.0.1:8120/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Authorization: Bearer lmd_agent_xxxx" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"smoke","version":"0.0.0"}}}'
A healthy server replies 200 with an SSE data: line carrying the initialize result
(serverInfo.name = "lumind-mcp"). A request without the Authorization header is rejected
with 401. There is also a plain GET /healthz returning {"status":"ok"}.
npm run dev # run from source over stdio (tsx)
npm run dev:http # run the HTTP transport from source (tsx)
npm run smoke # offline smoke test: checks tool registration + a mocked call, no network
dist/index.js), the standard way MCP clients spawn a local server as a
subprocess. One capped key per process via LUMIND_AGENT_KEY.dist/http.js), a remote, multi-client endpoint. Each request brings
its own agent key in the Authorization header; sessions are stateless and isolated, so N
instances run independently with no shared key or cross-request state.MIT.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.