Skip to content

Atisbo MCP server

io.github.brian8a1/atisbobrian8a1streamable-httpv1.0.0Scanned

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

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

Tools: 4 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

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 Radar 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 →

What the Atisbo MCP server can do

The Atisbo MCP server is published by the GitHub account brian8a1. It has 8 tools. It can delete or cancel things (4 tools: atisbo_capture, atisbo_decide, atisbo_map and atisbo_connect) and create or change data (2 tools: atisbo_orient and atisbo_support). 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Deletes or cancels 4Claude 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 — call catalog and read `fallback` before saying "Atisbo cannot ingest that". Atisbo only READS a connected system. create returns the 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_decideCURATE: evidence review/grouping, deal-breakers.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
    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_mapCreate/apply maps, generate/edit nodes and edges, anchor claims/snippets, bind metrics, manage claim-snipe maps, regroup (merge/split), build_macros (macros, preview first).No findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create/apply maps, generate/edit nodes and edges, anchor claims/snippets, bind metrics, manage claim-snipe maps, regroup (merge/split), build_macros (macros, preview first). Prefer mode=apply for MECE grouping. Anchor and link_claims put a claim on a node differently and both refuse the wrong map kind: anchor sets the TAXONOMY category (auto_node_id); link_claims adds STRUCTURAL-map membership.

    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 2Claude 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 atisbo_lookup mode=open; corpus via claim depth=work; aggregates via atisbo_analyze; edit via atisbo_lookup mode=doc_patch_context then atisbo_capture mode=patch_artefact (living documents; manual Knowledge documents are edited in place with atisbo_capture mode=update_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, key scope and migrations, 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 2Show 2 read-only tools
  • 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:02 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://app.atisbo.dev/.well-known/oauth-protected-resource
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (4 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://app.atisbo.dev/api/mcp: tools/list returned 8 tools to an anonymous client, including atisbo_capture (destructive), atisbo_decide (destructive), atisbo_map (destructive), atisbo_connect (destructive), atisbo_orient (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 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
  • 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

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools8 changed.~8 changedView diff
  2. Tools7 changed.~7 changedView diff

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>'
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as atisbo. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.brian8a1/atisbo/verify?hash=702975652b2e92ee887b94c659f1d5597bc6bec307ccd6f4df0253d06d9d76c4" | jq -e '.changed == false'

Pinned hash 702975652b2e, from Nov 16, 2026, 23:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

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

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

Badge

Anlyon Radar badge for io.github.brian8a1/atisbo
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.brian8a1/atisbo.svg)](https://radar.anlyon.com/servers/io.github.brian8a1/atisbo)

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

Atisbo MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Atisbo MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Atisbo MCP server delete data?

Yes. 4 tools can delete, cancel or revoke something: atisbo_capture, atisbo_decide, atisbo_map and atisbo_connect.

Can the Atisbo MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Atisbo MCP server have?

8 tools: 4 destructive, 2 write, 2 read. atisbo_capture, atisbo_decide, atisbo_map, atisbo_connect, atisbo_orient, atisbo_support, atisbo_lookup and atisbo_analyze.

Does the Atisbo MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Atisbo MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Atisbo MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.