# Atisbo

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

- name: io.github.brian8a1/atisbo
- version: 1.0.0
- connection class: R1 (autonomous)
- trust: 77/100 flags: no-repository
- quality: 77/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.brian8a1%2Fatisbo
- tools: https://api.protogrid.dev/v1/servers/io.github.brian8a1%2Fatisbo/tools

**An agent can connect on its own if it already holds `atisbo_mcp_key`.** Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "atisbo": {
      "type": "http",
      "url": "https://app.atisbo.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer ${atisbo_mcp_key}"
      }
    }
  }
}
```

Placeholders to fill: `${atisbo_mcp_key}`.

## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 45
- drivers: +website +reachable +uptime-100% ~updated-57d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 77/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 79 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 8 of 8 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: atisbo_orient (idempotentHint, openWorldHint); atisbo_map (idempotentHint, openWorldHint); atisbo_connect (idempotentHint, openWorldHint); …
- warn `tools.token_cost`: about 9,504 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 75 (weight 15)

- warn `stability.changes`: 48 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 8, about 9,504 tokens to load them all
- tool set hash: 3dc1c24ff98eb1f251061e3df5417aa2
- tools last changed: 2026-10-16T14:34:29.089Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.brian8a1/atisbo.svg)](https://protogrid.dev/servers/io.github.brian8a1/atisbo)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-16 `atisbo_lookup` changed (inputSchema)
- 2026-10-15 `atisbo_decide` changed (inputSchema)
- 2026-10-15 `atisbo_decide` changed (inputSchema)
- 2026-10-15 `atisbo_lookup` changed (description, inputSchema)
  - before: Find or open Atisbo entities. Modes expose snippet text + attachment URLs, queues, outcomes and implementation context.
  - after: Find or open Atisbo entities: snippets, queues, outcomes and implementation context across modes.
- 2026-10-14 `atisbo_support` changed (inputSchema)
- 2026-10-14 `atisbo_analyze` changed (inputSchema, outputSchema)
- 2026-10-14 `atisbo_connect` changed (inputSchema)
- 2026-10-14 `atisbo_map` changed (inputSchema)
- 2026-10-14 `atisbo_decide` changed (inputSchema)
- 2026-10-14 `atisbo_capture` changed (inputSchema)

Full history: https://api.protogrid.dev/v1/servers/io.github.brian8a1%2Fatisbo/changes

## Remotes

- https://app.atisbo.dev/api/mcp (streamable-http, auth api_key ${atisbo_mcp_key}, reachable true, uptime30d 1)

## Packages

_none_

## Tools (8)

- `atisbo_analyze`: 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; a single-entity drill-down is atisbo_lookup mode=get with the entity id.
- `atisbo_capture`: Capture Signals or knowledge; update, patch or add evidence to artefacts.
- `atisbo_connect`: WHERE 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 cannot ingest that". Atisbo only READS a connected system. create returns endpoint + signing secret shown ONCE — relay to the human immediately.
- `atisbo_decide`: 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.
- `atisbo_lookup`: Find or open Atisbo entities: snippets, queues, outcomes and implementation context across modes.
- `atisbo_map`: Map 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_node_id; refuses non-taxonomy maps); mode=link_claims adds STRUCTURAL-map membership (claim keeps its category; refuses taxonomy maps).
- `atisbo_orient`: 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_support`: 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.