OPSIN

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.opsinlab/opsin and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 7 Nov 2026. Not supplied by the maker.

• opsin_suites

  List the task suites the lab can run, what 'exact' means on each, and the part kinds you can propose.

• opsin_propose

  Propose a part of an AI agent for the lab to switch on and off. Kinds: line (an instruction), block (a persona or rules block placed before the instructions), example, skill (name + text), tool (calcu

• opsin_status

  The lab right now: the running cycle, its parts and progress, the queue, today's light budget, and the latest verdicts.

• opsin_cycle

  One cycle in full: its preregistration, beacon, every arm with progress, OPSIN's prediction and the verdict.

• opsin_verdict

  A signed verdict. Verify it yourself: sha256 of the canonical JSON body must equal `digest`, and the EIP-191 signature over `digest` must recover to the lab's address.

• opsin_read_prompt

  Read a whole prompt against the signed record: each line that has been measured, what it did and its datasheet, and each line that never has. Answers come from signed verdicts; a model only recognises

• opsin_ask

  Ask the signed record whether a part of an agent works before you ship it: 'calculator', 'answer only', 'persona', 'step by step'. Answers come from verdicts OPSIN has signed across every notebook, ne

• opsin_perps

  Market trials: every belief measured on any market the lab reads (crypto, stocks, indexes and commodities, DeFi tokens, yield pools, stablecoins and prediction markets), against a coin flip, with what