Koskamo

LightRay MCP

This server enables agents to check company backgrounds, read generated reports, and list recent reports directly within the chat interface. It provides background information, questions to ask, and next steps for due diligence on companies.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

LightRay MCP logo, by LightRay Inc.Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by LightRay Inc.
You need:On a Team or Enterprise plan, an owner adds LightRay for the organization first.
MCP endpoint (Streamable HTTP)
https://app.lightray.ai/mcp
Vendor documentation

What you can do with it

  • Check a company by name and location
  • Read a specific company report
  • List recent company reports

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
LightRay 1.0.0
MCP protocol
2025-06-18
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

LightRay checks companies. Use check_company with a company's name and its city or country: a new report takes about 12 minutes and gives the background, any questions to ask and what to do next. get_report shows how far a report has got and what has been found so far, and, once it is ready, the report and its link. LightRay writes each report: its main point, questions, findings and next steps are LightRay's.

Tools

3 advertised

check_company — Check a company
Advertised by the server during the last successful anonymous check.
Open-world

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.

check_company input schema
{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 160,
      "description": "The company's name, as it is registered if known: its legal name with its legal form, such as Limited or LLC."
    },
    "place": {
      "type": "string",
      "maxLength": 80,
      "description": "The company's city or country, if known. It helps find the right company."
    },
    "choice": {
      "type": "string",
      "maxLength": 40,
      "description": "The choice token of one company from the list this tool returned when several matched. Give it with the same name."
    }
  },
  "additionalProperties": false
}
check_company output schema
{
  "type": "object",
  "required": [
    "status"
  ],
  "properties": {
    "status": {
      "enum": [
        "ready",
        "building",
        "choose",
        "several",
        "no_company",
        "declined",
        "limit",
        "paused",
        "failed",
        "stopped",
        "expired",
        "not_found",
        "error"
      ],
      "type": "string"
    }
  }
}
check_company annotations
{
  "title": "Check a company",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
get_report — Read a report
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_report input schema
{
  "type": "object",
  "required": [
    "report_id"
  ],
  "properties": {
    "report_id": {
      "type": "string",
      "maxLength": 300,
      "description": "The report_id that check_company or list_reports returned, or the report's link."
    }
  },
  "additionalProperties": false
}
get_report output schema
{
  "type": "object",
  "required": [
    "status"
  ],
  "properties": {
    "status": {
      "enum": [
        "ready",
        "building",
        "choose",
        "no_company",
        "paused",
        "failed",
        "stopped",
        "expired",
        "not_found",
        "error"
      ],
      "type": "string"
    }
  }
}
get_report annotations
{
  "title": "Read a report",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
list_reports — List my reports
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

list_reports input schema
{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "How many reports to list, newest first: 1 to 20. 10 if not given."
    }
  },
  "additionalProperties": false
}
list_reports output schema
{
  "type": "object",
  "required": [
    "status",
    "reports"
  ],
  "properties": {
    "status": {
      "enum": [
        "listed"
      ],
      "type": "string"
    },
    "reports": {
      "type": "array",
      "items": {
        "type": "object"
      }
    }
  }
}
list_reports annotations
{
  "title": "List my reports",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
464 ms
95th percentile latency
464 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 464 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http lightray-mcp https://app.lightray.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add lightray-mcp --url https://app.lightray.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable lightray-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "lightray-mcp": {
      "url": "https://app.lightray.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "lightray-mcp": {
      "type": "streamableHttp",
      "url": "https://app.lightray.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start lightray-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "lightray-mcp": {
      "type": "http",
      "url": "https://app.lightray.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http lightray-mcp https://app.lightray.ai/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "lightray-mcp": {
      "url": "https://app.lightray.ai/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "lightray-mcp": {
      "serverUrl": "https://app.lightray.ai/mcp"
    }
  }
}

Let your agent find its tools

Find servers like LightRay MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run LightRay MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing