Atisbo MCP server

• atisbo_analyzeFree

  Broad 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; for single-entity drill-downs atisbo_lookup mode=claim or atisbo_lookup mode=node is enough.

• atisbo_captureFree

  Capture Signals or knowledge; update, patch or add evidence to artefacts.

• atisbo_connectFree

  WHERE Atisbo gets its signals. Modes: list, catalog, create (returns endpoint), configure, pause, resume, sync_now. THE CATALOG IS NOT THE BOUNDARY: almost anything connects — push app (composio_catalog), daily-pull app (composio_actions, ~1,000 apps), raw webhook/email. Never answer "Atisbo cannot ingest that" from an empty search; call catalog and read `fallback`. Atisbo only READS a connected system. create returns endpoint + signing secret shown ONCE — relay to the human immediately.

• atisbo_decideFree

  PM 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 UUIDs. mode=declare_pm_exception marks a CLAIM as needing a human decision (SEN-180).

• atisbo_lookupFree

  Find or open Atisbo entities. Modes expose snippet text + attachment URLs, queues, outcomes and implementation context.

• atisbo_mapFree

  Map facade: create/apply maps, generate/edit nodes and edges, anchor claims/snippets, bind metrics, manage claim-snipe maps, regroup (mode=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 (claims.auto_node_id, what the Board groups by), refusing non-taxonomy maps; mode=link_claims adds membership in a STRUCTURAL map while the claim keeps its category, refusing taxonomy maps.

• atisbo_orientFree

  Workspace 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_lookup mode=doc_patch_context then atisbo_capture mode=patch_artefact.

• atisbo_supportFree

  Diagnose 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/atisbo_analyze for backlog.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 489ms20/20
• Tool poisoning8 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

Atisbo: common questions

Is Atisbo MCP server safe?

With care: it is graded C, so read the findings first (64/100). Read the Atisbo safety report

How do I install Atisbo?

It runs remotely at app.atisbo.dev. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Atisbo need an API key?

Yes. The registry entry asks for Authorization.

Is Atisbo maintained?

The latest release is v1.0.0.

Is Atisbo up?

100% of our last 20 checks got an answer. We check remote servers about four times a day.

What can I use instead of Atisbo?

Servers from other publishers that do the same job: World Monitor MCP server.