_ registry / mcp http-sse · checked 3h ago

sunex-optics

https://mcp.sunex-ai.com

Registry code: 42cff8a52cbe1f1e

api record

Search Sunex lenses and imager sensors, match compatible optics, get pricing. No API key needed.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.sunex-ai.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is sunex-optics live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is sunex-optics free to use?
Yes — the hub reached it with no key and no payment.
What tools does sunex-optics have?
5 tools: get_imager_detail, recommend_lens_for_imager, find_compatible_lenses, search_products, search_imagers.
Is sunex-optics safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.5%· all time 99.5%

latency
1,470ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 382 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • find lenses compatible with an image sensor
  • search image sensors by part number
  • get lens pricing
  • get sensor specifications
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_products reads open 24h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "q": {
          "type": "string",
          "description": "Description keyword (e.g. 'fisheye')"
        },
        "pn": {
          "type": "string"
        },
        "limit": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1
        },
        "detail": {
          "type": "boolean"
        }
      }
    }
    arguments 21 lines
  • search_imagers reads open 24h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "pn": {
          "type": "string",
          "description": "Partial ImagerPN match (e.g. 'IMX577', 'OV')"
        },
        "mfg": {
          "type": "string",
          "description": "Partial manufacturer match (e.g. 'Sony')"
        },
        "limit": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1
        },
        "detail": {
          "type": "boolean"
        },
        "resClass": {
          "type": "string",
          "description": "Resolution class prefix (e.g. '2MP (1080p)')"
        }
      }
    }
    arguments 26 lines
  • get_imager_detail reads unknown 19h ago

    Get full imager specs PLUS computed sensor geometry (effective width/height/diagonal in mm) and a pre-built lens-wizard URL.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "pn"
      ],
      "properties": {
        "pn": {
          "type": "string",
          "description": "Required. Partial ImagerPN match."
        },
        "limit": {
          "type": "integer",
          "maximum": 256,
          "minimum": 1
        }
      }
    }
    arguments 18 lines
  • recommend_lens_for_imager reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "imagerPn"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1
        },
        "dFovMax": {
          "type": "number"
        },
        "dFovMin": {
          "type": "number"
        },
        "fNumMax": {
          "type": "number",
          "description": "Cap F-number (e.g. 2.0 = fast lenses only)"
        },
        "hFovMax": {
          "type": "number"
        },
        "hFovMin": {
          "type": "number"
        },
        "imagerPn": {
          "type": "string",
          "description": "Imager part number, e.g. 'IMX577', 'AR0820'"
        }
      }
    }
    arguments 34 lines
  • find_compatible_lenses reads unknown 24h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "hPixel",
        "vPixel",
        "hPitch"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1
        },
        "hPitch": {
          "type": "number",
          "description": "Horizontal pixel pitch in µm",
          "exclusiveMinimum": 0
        },
        "hPixel": {
          "type": "integer",
          "maximum": 9007199254740991,
          "exclusiveMinimum": 0
        },
        "vPitch": {
          "type": "number",
          "description": "Defaults to hPitch",
          "exclusiveMinimum": 0
        },
        "vPixel": {
          "type": "integer",
          "maximum": 9007199254740991,
          "exclusiveMinimum": 0
        },
        "dFovMax": {
          "type": "number"
        },
        "dFovMin": {
          "type": "number"
        },
        "fNumMax": {
          "type": "number"
        },
        "fNumMin": {
          "type": "number"
        },
        "hFovMax": {
          "type": "number"
        },
        "hFovMin": {
          "type": "number"
        },
        "vFovMax": {
          "type": "number"
        },
        "vFovMin": {
          "type": "number"
        }
      }
    }
    arguments 60 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 42cff8a52cbe1f1e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/42cff8a52cbe1f1e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/42cff8a52cbe1f1e/badge.svg)](https://brick.blue/agent/42cff8a52cbe1f1e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.