dev.seblabs/seblabs · v1.1.0 · agents-and-memory
Seb Labs is healthy: it completed an MCP handshake in 1656 ms and exposes 5 tools.
Typed AI decisions for agents: classify, route, screen evidence, score and batch-label text.
Endpoint: https://mcp.seblabs.dev/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 5 |
| Latency | 1656 ms |
| Last checked (UTC) | 2026-10-26T06:00:17.865Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-26T06:00:17.865Z | Healthy | 1656 | |
| 2026-10-26T06:00:17.593Z | Healthy | 1468 |
seb_demo | Use for a free connection/interface check or a fixed example of enterprise, finance, robotics or handoff decisions. Returns labeled illustrative probabilities, never live inference. No account token is required. Use a paid tool to judge your own input. |
seb_decide | Use for evidence/claim support checks, binary screening, rubric scoring, or several related judgments on one text state. Supply 1–10 named questions: choice has 2–20 option keys mapped to descriptions (or null); noul asks a precisely worded positive/yes proposition and returns its probability in [0, |
seb_fin_analyze | Use only for entitled accounts with an enabled dedicated Seb-9B-Fin backend, to judge financial language or supplied point-in-time market context with the same choice/noul/score schema. The public general-model endpoint does not currently enable this specialist. Returns typed model estimates, not in |
seb_route | Use for fast single-label classification or routing: ticket triage, intent/topic/sentiment labels, selecting a tool or workflow, guardrail categories or an escalation decision. Supply the relevant context and 2–20 unique option labels (up to 80 characters each); add an unclear/escalate label if appr |
seb_batch_decide | Use to classify, screen, triage, rank by an explicit rubric, or bulk-label up to 100 independent text states with the same 1–10 typed questions. Each result retains its input index and its own success/error; up to four items run concurrently. Inspect all per-item errors and retry failed items only, |