LuBot Analytics
REMOTE · MCP.LUBOT.AI
Portfolio X-Ray with ETF look-through, file analysis, and website analytics in plain English.
Available components
Last scanned (32 minutes ago)
Scores higher than 8% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 429. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.lubot.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=staging-mcp.lubot.ai | CN=YE1,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 614f3a1a50ad5669551d08bf8091904ec87 |
| SANs: mcp.lubot.ai, staging-mcp.lubot.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.lubot.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| lubot.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 429 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.lubot.ai/mcp | HTTP error | 429 | |
| http (plaintext) | http://mcp.lubot.ai/mcp | HTTPS enforced | 301 | https://mcp.lubot.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_file Analyze a File ~217
File ownership check + LuBot analysis surface routing. Returns a lightweight AnalysisResult: confirms the file exists + is in the caller's tenant (or the shared demo corpus when the caller has no uploads yet), surfaces its metadata, and points the user at the full LuBot My Files chat for the deep PhD-level answer. Deeper fields — chart, narrative, and richer citations beyond the single-file ownership evidence — populate on the full chat surface once that pipeline is wired. The response has two `content[]` entries: a pre-rendered narrative + citations (priority: 1.0, audience: user+assistant), plus a raw-JSON block + `structuredContent` field including chart data when available (priority: 0.3, audience: assistant only) for programmatic consumers or when the caller explicitly asks for raw data.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | – |
| question | string | yes | – |
No output schema declared.
No examples provided.
analyze_portfolio Analyze My Portfolio ~239
PhD-style analysis over the caller's portfolio. Returns a two-block response. The first `content[]` entry is a pre-rendered plain-English summary (priority: 1.0, audience: user+assistant). The second entry + `structuredContent` field carry the underlying JSON (priority: 0.3, audience: assistant only) for programmatic consumers or when the caller explicitly asks for raw data. Concentration risk (low/medium/high), diversification score (0-10), sector breakdown (with ETF look-through decomposition when the fund is known), biggest winner + loser by dollar impact, plus a 2-4 sentence LLM narrative that ties it together. Anonymous callers + hard-fail engine paths get an honest empty response with a signup nudge. Signed-in callers with no positions yet see a shared demo portfolio with a demo-mode call-to-action in the summary. Positions with unavailable live prices are labeled honestly — the narrator does not compute aggregate P&L over incomplete data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_files List My Files ~120
List files the authenticated user has uploaded to LuBot. The response has two `content[]` entries: a pre-rendered plain-English summary (priority: 1.0, audience: user+assistant), plus a raw-JSON block + `structuredContent` field (priority: 0.3, audience: assistant only) for programmatic consumers or when the caller explicitly asks for raw data. Signed-in callers with no uploads yet see a shared demo corpus with a demo-mode call-to-action.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_portfolio List My Portfolio Holdings ~162
List the caller's portfolio holdings. Returns positions merged from Plaid-synced brokerage + manually- entered trades. The response has two `content[]` entries: a pre-rendered plain-English summary (priority: 1.0, audience: user+assistant), plus a raw-JSON block + `structuredContent` field (priority: 0.3, audience: assistant only) for programmatic consumers or when the caller explicitly asks for raw data. Anonymous callers → honest empty + signup nudge. Signed-in callers with no positions yet → shared demo portfolio with demo_mode=true. Positions with unavailable live prices are labeled honestly rather than reported as fabricated zero P&L.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_watchlist List My Stock Watchlist ~136
List tickers the authenticated user has added to their LuBot watchlist. Returns symbols + added_at, ordered by add time. The response has two `content[]` entries: a pre-rendered plain-English summary (priority: 1.0, audience: user+assistant), plus a raw-JSON block + `structuredContent` field (priority: 0.3, audience: assistant only) for programmatic consumers. Anonymous callers get an empty list — the watchlist requires a LuBot account. Sign in at https://lubot.ai/connect.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_websites List Connected Websites ~85
List website projects the authenticated user can query. The response has two `content[]` entries: a pre-rendered plain-English summary (priority: 1.0, audience: user+assistant), plus a raw-JSON block + `structuredContent` field (priority: 0.3, audience: assistant only) for programmatic consumers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ping Health Check ~19
Return a small health-check payload. Safe to call anonymously.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
stock_analysis Analyze a Stock ~236
Ticker validation + LuBot analysis surface routing. Returns a lightweight AnalysisResult: ticker validation, source label (`watchlist` vs `public`), a narrative pointing the user at the full LuBot analyst, and (when available) an upgrade hint. The deeper fields — live price, fair value, thesis, risks, and recommendation — currently populate only for watchlist-tagged calls; the public path leaves them null. The response has two `content[]` entries: a pre-rendered plain-English summary (priority: 1.0, audience: user+assistant), plus a raw-JSON block + `structuredContent` field (priority: 0.3, audience: assistant only) for programmatic consumers or when the caller explicitly asks for raw data. Anonymous callers get the zero-setup public path (rate-limited to protect against abuse). Authenticated callers get a watchlist-tagged response + upgrade hints when the ticker isn't in their watchlist.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
No output schema declared.
No examples provided.
website_summary Website Traffic Summary ~198
Return traffic summary for one of the caller's websites. Args: site_id: One of the site_ids returned by list_websites. start_date: Inclusive range start in ISO format (YYYY-MM-DD). end_date: Inclusive range end in ISO format (YYYY-MM-DD). The window must not exceed 90 days. The response has two `content[]` entries: a pre-rendered summary (narrative + total visits + top countries + top pages + AI-noticed cards) at priority: 1.0, audience: user+assistant, plus a raw-JSON block + `structuredContent` field at priority: 0.3, audience: assistant only for programmatic consumers or when the caller explicitly asks for raw data.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| site_id | string | yes | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
How do I install the LuBot Analytics MCP server?
LuBot Analytics is a hosted endpoint at https://mcp.lubot.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.lubot.ai
claude mcp add --transport http lubobali-lubot 'https://mcp.lubot.ai/mcp'
What is the LuBot Analytics MCP server?
LuBot Analytics is an MCP server listed in the public MCP registry as io.github.lubobali/lubot. Portfolio X-Ray with ETF look-through, file analysis, and website analytics in plain English. This page covers its hosted endpoint (https://mcp.lubot.ai/mcp).
Is the LuBot Analytics MCP server safe to use?
LuBot Analytics scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LuBot Analytics MCP server expose?
LuBot Analytics exposes 9 tools: list_files, analyze_file, ping, analyze_portfolio, list_portfolio, and 4 more. Their descriptions and schemas cost roughly 1,412 tokens of context every time the server is loaded.
Does the LuBot Analytics MCP server require authentication?
Its publisher declares no required credentials for LuBot Analytics. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the LuBot Analytics MCP server still maintained?
LuBot Analytics is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.