optics-mcp server
com.sunex/optics-mcpsunex.comssev1.0.0Scanned
Search Sunex lenses and imager sensors, match compatible optics, get pricing. No API key needed.
5 tools: 1 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the optics-mcp server can do
The optics-mcp server is published by sunex.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: recommend_lens_for_imager), but cannot delete data. 4 tools only read.
1 tool brings in text other people can write (get_imager_detail).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 29, 2026, version 1.0.0.
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.
5 tools
Changes things 1Claude Code: ask
recommend_lens_for_imagerOne-shot recommendation: given an imager part number (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it One-shot recommendation: given an imager part number (e.g. 'IMX577'), looks up its geometry, then returns compatible lenses with FOV and angular resolution. Use this when the user names a sensor and wants lens options.
Only reads 4Show 4 read-only tools
find_compatible_lensesGiven an imager's pixel count and pitch, return lenses whose image circle and resolving power cover the sensor, with per-lens FOV and angular resolution.No findings
Why it is in this group
- The name "find_compatible_lenses" says "find": a word for reading.
Description, as the server wrote it Given an imager's pixel count and pitch, return lenses whose image circle and resolving power cover the sensor, with per-lens FOV and angular resolution. Supports optional FOV and F/# range filters.
get_imager_detailGet full imager specs PLUS computed sensor geometry (effective width/height/diagonal in mm) and a pre-built lens-wizard URL.Reads text others writeNo findings
Why it is in this group
- The name "get_imager_detail" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Get full imager specs PLUS computed sensor geometry (effective width/height/diagonal in mm) and a pre-built lens-wizard URL.
search_imagersSearch the Sunex imager (sensor) catalog by part number, manufacturer, or resolution class.No findings
Why it is in this group
- The name "search_imagers" says "search": a word for reading.
Description, as the server wrote it Search the Sunex imager (sensor) catalog by part number, manufacturer, or resolution class. Use detail=true with a specific pn for a single-record exact lookup.
search_productsSearch the full Sunex product catalog by PN prefix and/or description keyword.No findings
Why it is in this group
- The name "search_products" says "search": a word for reading.
Description, as the server wrote it Search the full Sunex product catalog by PN prefix and/or description keyword. Returns sample price, currency, and URLs for spec sheet, sample order, and RFQ.
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 20, 2026, 18:47 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 410
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- yes
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The SSE endpoint answered HTTP 410.
Posture changes
- Nov 6, 2026
- HTTP status of an anonymous initialize: 202 to 410
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
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.
PostureRemote posture changed. HTTP status of an anonymous initialize: 202 -> 410; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 202 to 410
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport sse optics https://mcp.sunex-ai.com/sseclaude mcp add --transport sse optics https://mcp.sunex-ai.com/sseRun 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__optics__search_imagers",
"mcp__optics__get_imager_detail",
"mcp__optics__find_compatible_lenses",
"mcp__optics__search_products"
],
"ask": [
"mcp__optics__recommend_lens_for_imager"
],
"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 optics. Review it before you use it.
Capability tags behind 1 rule
- mcp__optics__get_imager_detail 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/com.sunex/optics-mcp/verify?hash=9379158a29ecbabcf1628302577967be5ace11ae410d016987b371510dd93b7e" | jq -e '.changed == false'Pinned hash 9379158a29ec, from Oct 29, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.sunex/optics-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.sunex/optics-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:05 UTC.
optics-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the optics-mcp server safe?
- No scan can promise that. What its definitions show: 5 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 optics-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the optics-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 optics-mcp server have?
- 5 tools: 1 write, 4 read. recommend_lens_for_imager, search_imagers, get_imager_detail, find_compatible_lenses and search_products.
Does the optics-mcp server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the optics-mcp server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the optics-mcp server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 29, 2026.