LightRay MCP server
ai.lightray/lightraylightray.aistreamable-httpv1.0.2Scanned
Send a company name and city, get a report on its owners, directors, filings, courts and press.
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the LightRay MCP server can do
The LightRay MCP server is published by lightray.ai, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: check_company), but cannot delete data. 2 tools only read.
1 tool brings in text other people can write (check_company).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 1Claude Code: ask
check_companyUse this when someone asks about a company or wants one checked.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a company
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 2Show 2 read-only tools
get_reportUse 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, …No findings
Why it is in this group
- The name "get_report" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read a report
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_reportsUse this to see the reader's recent reports from here, newest first, each with whether it is ready and its link.No findings
Why it is in this group
- The name "list_reports" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List my reports
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:21 UTC, unchanged since Oct 31, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://app.lightray.ai/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://app.lightray.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://app.lightray.ai/mcp: tools/list returned 3 tools to an anonymous client, including check_company (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http lightray https://app.lightray.ai/mcpclaude mcp add --transport http lightray https://app.lightray.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__lightray__get_report",
"mcp__lightray__list_reports"
],
"ask": [
"mcp__lightray__check_company"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lightray. Review it before you use it.
Capability tags behind 1 rule
- mcp__lightray__check_company untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.lightray/lightray/verify?hash=167c44eb8fcbcb9803d7ed9a47fc3f970a1b4c66595f1ab56e6f63f9a75c9941" | jq -e '.changed == false'Pinned hash 167c44eb8fcb, from Nov 19, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.lightray/lightray/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.lightray/lightray)Source: MCP Registry. Synced Nov 5, 2026, 17:17 UTC.
LightRay MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the LightRay MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the LightRay MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the LightRay MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the LightRay MCP server have?
- 3 tools: 1 write, 2 read. check_company, get_report and list_reports.
Does the LightRay MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the LightRay MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the LightRay MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.