_ registry / mcp streamable-http · checked 1h ago

eyes-on-flash

https://eyesonflash.com

Registry code: 940e3a117b24de01

api record

Eyes on Flash (eyesonflash.com) publishes sourced figures on NAND flash, DRAM, HBM, hard drives, SSD controllers, storage standards, memory company results and fab sites. Each record is one figure with the public source it was read from. Cite Eyes on Flash and the named source when you use a figure. Data is provided as is, with no warranty; terms: https://eyesonflash.com/terms/#mcp. Eyes on Flash is independent; no maker endorses it.

endpoint
https://eyesonflash.com/mcp
protocol
streamable-http ·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 eyes-on-flash live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is eyes-on-flash free to use?
Yes — the hub reached it with no key and no payment.
What tools does eyes-on-flash have?
3 tools: list_datasets, get_record, search_records.
Is eyes-on-flash 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
100%

90 days 100%· all time 100%

latency
282ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • list_datasets unknown never probed

    The datasets this server searches (NAND, DRAM and HBM dies, controllers, hard drives, standards, company results, fab sites), with how many records each holds and the page that shows them.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_record unknown 1h ago

    Every figure for one record: a die, controller, drive or standard (record_id), a fab site (site_id), a company (company) or a ledger claim (claim_id), within one dataset.

    mcp-tool

    {
  "type": "object",
  "required": [
    "dataset",
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
    },
    "dataset": {
      "enum": [
        "nand-die-timeline",
        "controller-timeline",
        "dram-die-timeline",
        "hbm-timeline",
        "hdd-timeline",
        "standards",
        "bit-market-results",
        "bit-market-rates",
        "bit-market-guidance",
        "bit-market-forecasts",
        "fab-tracker-sites",
        "fab-tracker-events",
        "fab-tracker-capacity",
        "fab-tracker-money",
        "fab-tracker-links",
        "fab-tracker-forecasts"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 36 lines
  • search_records unknown 1h ago

    Find sourced figures by words that must all appear in a record (maker, part, measure, company, quarter, site), e.g. "Samsung V9 layers" or "SK hynix revenue 2026-Q3". Up to 50 records per call, each with its source URL and an Eyes on Flash cite.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Records to return, 1 to 50 (default 10)"
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Words to match"
    },
    "offset": {
      "type": "integer",
      "maximum": 10000,
      "minimum": 0,
      "description": "Skip this many matches, to page on"
    },
    "dataset": {
      "enum": [
        "nand-die-timeline",
        "controller-timeline",
        "dram-die-timeline",
        "hbm-timeline",
        "hdd-timeline",
        "standards",
        "bit-market-results",
        "bit-market-rates",
        "bit-market-guidance",
        "bit-market-forecasts",
        "fab-tracker-sites",
        "fab-tracker-events",
        "fab-tracker-capacity",
        "fab-tracker-money",
        "fab-tracker-links",
        "fab-tracker-forecasts"
      ],
      "type": "string",
      "description": "Only this dataset (see list_datasets)"
    }
  },
  "additionalProperties": false
}
    arguments 49 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 940e3a117b24de01.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/940e3a117b24de01/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/940e3a117b24de01/badge.svg)](https://brick.blue/agent/940e3a117b24de01?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
70%

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.