LightRay
REMOTE · APP.LIGHTRAY.AI
Company background checks and due diligence: who owns and runs a company, its filings and press.
Available components
Last scanned (6 hours ago)
Scores higher than 76% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category CRM and Sales
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- 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 not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- 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 we couldn't connect to verify it. 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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.10 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 77
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://app.lightray.ai/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.lightray.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| lightray.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 |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.lightray.ai/mcp | Unreachable | ||
| http (plaintext) | http://app.lightray.ai/mcp | HTTPS enforced |
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 →
check_company Check a company ~206
Use this when someone asks about a company or wants one checked. Give the company's name and, if known, its city or country. If a recent report on the company is stored, it comes back at once; otherwise a new report starts and the answer says when it will be ready. A new report uses one of the reader's reports; asking again for the same company does not. When several companies match the name, the answer lists them: ask the reader which one they mean, then call this again with that company's choice token. LightRay checks companies, not people.
| Name | Type | Req | Description |
|---|---|---|---|
| choice | string | – | The choice token of one company from the list this tool returned when several matched. Give it with the same name. |
| name | string | yes | The company's name, as it is registered if known: its legal name with its legal form, such as Limited or LLC. |
| place | string | – | The company's city or country, if known. It helps find the right company. |
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | – |
No examples provided.
get_report Read a report ~137
Use this to see how far a report has got and what has been found so far, or to read a ready report: its date, the main point, any questions to ask, what was found, the next steps, the companies worth a look next and its link. LightRay writes each report: the main point, questions, findings and next steps are LightRay's. Give the report_id that check_company or list_reports returned, or the report's link. Reading a report uses none of the reader's reports.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | The report_id that check_company or list_reports returned, or the report's link. |
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | – |
No examples provided.
list_reports List my reports ~69
Use this to see the reader's recent reports from here, newest first, each with whether it is ready and its link. It uses none of the reader's reports.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many reports to list, newest first: 1 to 20. 10 if not given. |
| Name | Type | Req | Description |
|---|---|---|---|
| reports | array | yes | – |
| status | string | yes | – |
No examples provided.
How do I install the LightRay MCP server?
LightRay is a hosted endpoint at https://app.lightray.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 · app.lightray.ai
claude mcp add --transport http ai-lightray-lightray 'https://app.lightray.ai/mcp'
What is the LightRay MCP server?
LightRay is an MCP server listed in the public MCP registry as ai.lightray/lightray. Company background checks and due diligence: who owns and runs a company, its filings and press. This page covers its hosted endpoint (https://app.lightray.ai/mcp).
Is the LightRay MCP server safe to use?
LightRay scores 78 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 LightRay MCP server expose?
LightRay exposes 3 tools: check_company, get_report, list_reports. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.
Does the LightRay MCP server require authentication?
Its publisher declares no required credentials for LightRay. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the LightRay MCP server still maintained?
LightRay is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.