Atisbo

by brian8a1 · remote · no sign-in to list tools · v1.0.0 · published by GitHub user brian8a1

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

Deletes · 4Changes · 2

Compare Registry entry

8 tools: 4 can delete or cancel things, 2 change things and 2 only read.

Scanned Oct 21, 2026

Deletes or cancels4Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things2Claude Code: ask: see these tools
Only reads2Claude Code: allow: see these tools

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http atisbo https://app.atisbo.dev/api/mcp --header 'Authorization: <your-authorization>'

Findings

Matches of fixed checks, with the text they matched.

2 info

Infoatisbo_decide
The input schema at properties.operational_block_category.enum[0] mentions "credentials".
Matched text
inputSchema.properties.operational_block_category.enum[0]: "credentials"
What this check looks for
Infoatisbo_support
The input schema at properties.problem.description mentions "credentials".
Matched text
inputSchema.properties.problem.description: "...ur words. No customer feedback, docs or credentials — the string IS filed in reports."
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Deletes or cancels 4Removes, cancels or revokes something.Claude Code: deny

atisbo_captureCapture Signals or knowledge; update, patch or add evidence to artefacts.No findings
Why it is in this group
- The name "atisbo_capture" says "capture": a word that usually means money moves, which cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Capture Signals or knowledge; update, patch or add evidence to artefacts.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- category: write
- requires_confirmation: false
- strict_output: false
- supports_idempotency: true
- supports_cursor: false
- supports_since_checkpoint: false
atisbo_connectWHERE Atisbo gets its signals.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- category: write
- requires_confirmation: false
- strict_output: false
- supports_idempotency: true
- supports_cursor: false
- supports_since_checkpoint: false
atisbo_decidePM decision facade.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Findings
- Info
  The input schema at properties.operational_block_category.enum[0] mentions "credentials".
  Matched text
  inputSchema.properties.operational_block_category.enum[0]: "credentials"
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- category: write
- requires_confirmation: false
- strict_output: false
- supports_idempotency: true
- supports_cursor: false
- supports_since_checkpoint: false
atisbo_mapMap facade: create/apply maps, generate/edit nodes and edges, anchor claims/snippets, bind metrics, manage claim-snipe maps, regroup (merge/split).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- category: write
- requires_confirmation: false
- strict_output: false
- supports_idempotency: true
- supports_cursor: false
- supports_since_checkpoint: false

Changes things 2Creates or changes something that can be changed back.Claude Code: ask

atisbo_orientWorkspace orientation.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- category: query
- requires_confirmation: false
- strict_output: false
- supports_idempotency: false
- supports_cursor: true
- supports_since_checkpoint: true
atisbo_supportDiagnose Atisbo, including "I connected a source and nothing appeared", "I sent text and no opportunity formed", or "my data is missing".1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
  The input schema at properties.problem.description mentions "credentials".
  Matched text
  inputSchema.properties.problem.description: "...ur words. No customer feedback, docs or credentials — the string IS filed in reports."
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- category: query
- requires_confirmation: false
- strict_output: true
- supports_idempotency: false
- supports_cursor: false
- supports_since_checkpoint: false

Only reads 2Looks things up and changes nothing.Claude Code: allow

atisbo_analyzeBroad analytical query over claims, solutions, or activity: time filters, grouping, metrics, ready-to-render chart artifact.No findings
Why it is in this group
- The name "atisbo_analyze" says "analyze": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- category: query
- requires_confirmation: false
- strict_output: true
- supports_idempotency: false
- supports_cursor: true
- supports_since_checkpoint: false
atisbo_lookupFind or open Atisbo entities: snippets, queues, outcomes and implementation context across modes.No findings
Why it is in this group
- The name "atisbo_lookup" says "lookup": a word for reading.
Description, as the server wrote it
Find or open Atisbo entities: snippets, queues, outcomes and implementation context across modes.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- category: query
- requires_confirmation: false
- strict_output: false
- supports_idempotency: false
- supports_cursor: true
- supports_since_checkpoint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http atisbo https://app.atisbo.dev/api/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__atisbo__atisbo_lookup",
      "mcp__atisbo__atisbo_analyze"
    ],
    "ask": [
      "mcp__atisbo__atisbo_orient",
      "mcp__atisbo__atisbo_support"
    ],
    "deny": [
      "mcp__atisbo__atisbo_capture",
      "mcp__atisbo__atisbo_decide",
      "mcp__atisbo__atisbo_map",
      "mcp__atisbo__atisbo_connect"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as atisbo. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.brian8a1/atisbo/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

6 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry. Synced Oct 21, 2026, 18:26 UTC.

For agents: Markdown · JSON · report this listing