# LightRay (remote · app.lightray.ai)

Company background checks and due diligence: who owns and runs a company, its filings and press.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `app.lightray.ai`: 78/100 (this document), [markdown](https://verifymcp.io/servers/ai-lightray-lightray/app.md), [page](https://verifymcp.io/servers/ai-lightray-lightray/app)

## Channel facts

- Endpoint: `https://app.lightray.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-lightray-lightray 'https://app.lightray.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-lightray-lightray": {
      "url": "https://app.lightray.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-lightray-lightray": {
      "type": "http",
      "url": "https://app.lightray.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-lightray-lightray]
url = "https://app.lightray.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-lightray-lightray": {
      "type": "remote",
      "url": "https://app.lightray.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-lightray-lightray --url 'https://app.lightray.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-lightray-lightray:
    url: "https://app.lightray.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-lightray-lightray": {
      "Transport": "http",
      "Url": "https://app.lightray.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-lightray-lightray -t streamable-http -u 'https://app.lightray.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-lightray-lightray": {
      "type": "http",
      "url": "https://app.lightray.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 78, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.10 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-02 (score 78, +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.

### 2026-11-01 (score 77, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 77)

First indexed and scored.

## MCP tools (3)

### `check_company` (~206 tokens)

Check a company

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.

Input parameters:

- `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, required): 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.

Output parameters:

- `status` (string)

### `get_report` (~137 tokens)

Read a report

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.

Input parameters:

- `report_id` (string, required): The report_id that check_company or list_reports returned, or the report's link.

Output parameters:

- `status` (string)

### `list_reports` (~69 tokens)

List my reports

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.

Input parameters:

- `limit` (integer): How many reports to list, newest first: 1 to 20. 10 if not given.

Output parameters:

- `reports` (array)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-lightray-lightray/app#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 77
- 2026-10-31: 77

## Common questions

### 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.

### What did VerifyMCP test on the LightRay MCP server?

VerifyMCP ran 3 checks on LightRay, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about LightRay: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://app.lightray.ai/mcp
- Website: https://www.lightray.ai/claude?ref=RG
- Changelog RSS feed: https://verifymcp.io/servers/ai-lightray-lightray/app.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-lightray-lightray/app/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-lightray-lightray/app.json
- HTML version of this page: https://verifymcp.io/servers/ai-lightray-lightray/app