Lumonic
by Lumonic
Query private-credit portfolio monitoring data — borrower financials, covenant status and reporting deliverables — from an AI agent. 24 tools, all read. OAuth sign-in with a single read scope.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Lumonic via MCP
https://mcp.lumonic.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Lumonic Tools & Capabilities (24)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Lumonic publishes no tool list. The 24 names come from Anthropic's directory. We searched Lumonic's help centre, its
/mcp,/mcp/libraryand/mcp/pitchbookpages and its connector guide, and not one of the 24 tool names appears as a literal string on any Lumonic page. This is the "no vendor enumeration" case: there is no second list to diff against, so we cannot report a clean listing — only that nothing exists to check it with. That is a weaker statement than "no undisclosed tools were found". - What partly substitutes for an enumeration is a negative one. Lumonic's
/mcppage and its connector guide both constrain the surface to read access, and Anthropic's directory description uses only read verbs — discover, build, summarize, identify, validate, generate, inspect. A constraint is more useful than a feature list, but it names no tools, so renames would be invisible to us either way. - We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here.
- One prompt is listed and we could not read it. Anthropic's directory lists a
build_lumonic_workbookprompt.prompts/listrequires authentication, so we cannot say what it contains or what it calls. - Lumonic's own contract terms were unreadable.
/footer/license-agreementand/footer/terms-of-usereturned byte-identical responses on 2026-08-23, both Framer shells whose HTML contains no legal prose and no embedded JSON payload. A control path under the same prefix returned a genuine 404, so this is not a blanket catch-all — those two routes specifically do not serve their documents to an unauthenticated fetch. We therefore report no contractual terms for this connector, and the confidentiality analysis above rests on the nature of credit agreements generally, not on Lumonic's paper. reporting_reminder_targetsis unresolved. We could not establish from documentation whether it only identifies who is delinquent or also dispatches a reminder to them, and we did not test it. Lumonic does send notification emails.- "Currently read-only" is a statement about today. Lumonic's own wording is that the connector "is currently read-only". The single
readscope is consistent with that, but a scope namedreadis a label, not an enforcement proof — we could not inspect the server's dispatch path. - Permission inheritance is a vendor claim we could not verify. Lumonic states MCP queries run as the requesting user's role. We had no credentials and did not test it.
- The connector is for Lumonic customers only. Lumonic states the MCP is included for every Lumonic customer; there is no standalone or trial access.
- Accuracy is your problem to check. Lumonic's troubleshooting section anticipates the model using the wrong metric and returning incomplete results, and advises asking it to confirm the workspace context, reporting period, entities and fields it used. Ask for source dates and traceback links when the answer will be acted on.
Frequently asked questions
No. All 24 tools read. Lumonic states its connector is currently read-only, so an analyst querying a borrowing base cannot modify the underlying record. The platform does let staff edit restatements and set compliance status in its own interface, but no MCP tool reaches either. The OAuth grant carries one scope, read, which matches.
Third-party company financials and loan economics. Lumonic states the connector gives models read access to financials, cash flows, covenants, reporting status and entities. Its query language documents fields including adjusted_ebitda, total_debt_outstanding, accounts_receivable and monthly-burn. That is your borrowers' confidential reporting, not your own firm's data.
Lumonic does not address that question, and you should not assume it does. Its documentation covers model training and permissions, not the confidentiality clauses in your credit agreements. Those clauses govern disclosure of borrower information to third parties, and an AI provider is a third party. Ask counsel before connecting a portfolio.
Lumonic states it does not. It says it does not contribute client data to any model's training and passes queries through under enterprise terms that exclude training. Lumonic also notes the model provider may log conversations under its own terms, which it calls a separate decision from what the data platform retains.
No. Lumonic states the MCP is included for every Lumonic customer, and no documentation mentions per-query pricing, credits or metered usage. No tool reports a balance or quota either, so nothing in the surface could observe spend — but with no per-call charge documented, there is nothing to observe.
Yes, according to Lumonic. It states each MCP query maps to the requesting user's existing role, so the model inherits the permission boundaries your team already administers. Lumonic's permission model runs Cluster to Namespace to Entity with allow and deny rules, and deny always wins. We could not verify this behaviour ourselves.
Anthropic's directory lists 24, and Lumonic publishes no tool list of its own. The endpoint returned 401 to an anonymous request, so we never read a live tools/list and cannot confirm the count independently. Treat 24 as Anthropic's figure rather than a verified total.
Your workspace owner has probably not added it yet. Lumonic states that on Claude Team or Enterprise an Owner or Primary Owner may need to enable the connector before individual users can connect. Lumonic documents a fallback: copy your MCP URL from Settings, open the MCP tab, and add it as a custom connector.
Sources
- Lumonic help centre, "Connect Lumonic to Claude with MCP" (retrieved 2026-08-23). The
.mdvariant of this URL was verified as a genuine second rendering, not a shell: its body hash differs from the HTML page, every distinctive string in it also appears in the HTML, and a non-existent article under the same pattern returned 404 rather than interpolated content. · retrieved 2026-08-23 - Lumonic MCP product page (retrieved 2026-08-23) · retrieved 2026-08-23
- Lumonic, "How to Connect AI Models to Portfolio Data with MCP" (retrieved 2026-08-23). Source of the read-only statement and the training and retention statements. · retrieved 2026-08-23
- Lumonic product update, "Introducing the Lumonic MCP: artifacts included", 21 July 2026 (retrieved 2026-08-23) · retrieved 2026-08-23
- Lumonic MCP library (retrieved 2026-08-23) · retrieved 2026-08-23
- Lumonic help centre, "Tracking reporting and compliance" (retrieved 2026-08-23) · retrieved 2026-08-23
- Lumonic help centre, "As of Dates and Restatements" (retrieved 2026-08-23) · retrieved 2026-08-23
- Lumonic help centre, "Adding Team Members & Permissions" (retrieved 2026-08-23) · retrieved 2026-08-23
- Lumonic help centre, "The Definitive Guide to LX" (retrieved 2026-08-23). Source of the field vocabulary and the absence of mutating syntax. · retrieved 2026-08-23
- Lumonic help centre machine index,
llms.txt(retrieved 2026-08-23).llms-full.txtreturned 404. · retrieved 2026-08-23 - Lumonic security page, SOC 2 Type II and encryption (retrieved 2026-08-23) · retrieved 2026-08-23
- Live OAuth posture check: anonymous
initializereturned 401 with aWWW-Authenticatechallenge namingscope="read"; RFC 9728 metadata athttps://mcp.lumonic.com/.well-known/oauth-protected-resource/mcpand authorization server metadata athttps://mcp.lumonic.com/.well-known/oauth-authorization-server, both advertisingscopes_supported: ["read"](2026-08-23). A control path under the same prefix returned 404, confirming no catch-all. · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Lumonic support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Finance
- Developer
- Lumonic
- Tools
- 24
- Domain
- mcp.lumonic.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.