Atisbo

io.github.brian8a1/atisbo · v1.0.0 · productivity

Atisbo is healthy: it completed an MCP handshake in 5259 ms and exposes 8 tools. It scores 57/100.

MCP tools over one Atisbo workspace: Signals, Opportunities, Backlog, Decisions, Living Documents.

Endpoint: https://app.atisbo.dev/api/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Score 57/100

health17 / 25
authEase15 / 15
toolQuality15 / 15
maintenance5 / 15
adoption0 / 10
usage0 / 10
security5 / 10

Scoring v0.3, computed 2026-10-15T03:06:03.659Z.

Health history

Checked (UTC)StatusLatencyError
2026-10-15T03:05:52.107ZHealthy5259

Tools (8)

atisbo_orientWorkspace orientation. Modes: snapshot, whats_new, strategy, integrations. Continue the user's existing workflow; never create a parallel backlog. Living docs cite snippet:// refs — open with atisbo_lookup mode=open, full corpus via claim depth=work, aggregates via atisbo_analyze. Edit via atisbo_lo
atisbo_lookupFind or open Atisbo entities: snippets, queues, outcomes and implementation context across modes.
atisbo_captureCapture Signals or knowledge; update, patch or add evidence to artefacts.
atisbo_decidePM decision facade. CURATE: evidence review/grouping, deal-breakers. EXECUTE: create, update, dispatch or delete Solutions, record Outcomes. DOCUMENT/GOVERN: living docs, coverage, schedules, knowledge, strategy. log_decision is only for external decisions; mutations log themselves. Writes require U
atisbo_mapMap facade: create/apply maps, generate/edit nodes and edges, anchor claims/snippets, bind metrics, manage claim-snipe maps, regroup (merge/split). Prefer mode=apply for full MECE categorization. TWO WAYS TO PUT A CLAIM ON A NODE, not interchangeable: mode=anchor sets the TAXONOMY category (auto_nod
atisbo_connectWHERE Atisbo gets its signals. Modes: list, catalog, create (returns endpoint), configure, pause, resume, sync_now, delete (soft-disconnect). THE CATALOG IS NOT THE BOUNDARY: almost anything connects (push app, daily-pull app, raw webhook/email) — call catalog and read `fallback` before ever saying
atisbo_analyzeBroad analytical query over claims, solutions, or activity: time filters, grouping, metrics, ready-to-render chart artifact. Use FIRST for analytical questions spanning entities or time windows; a single-entity drill-down is atisbo_lookup mode=get with the entity id.
atisbo_supportDiagnose Atisbo, including "I connected a source and nothing appeared", "I sent text and no opportunity formed", or "my data is missing". Checks integrations, ingestion, clustering, gates and key scope, then returns a playbook. share_report files only diagnostics + your text. Use atisbo_lookup/atisb