Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Atisbo

REMOTE · APP.ATISBO.DEV

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

Available components

0 this week 36 Trust /100

Last scanned (10 hours ago)

Scores higher than 19% of remote servers

Unreachable for 2 days in a row. Last reached 3 Nov 2026.

Category Project Management

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security14
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (3)

  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Endpoint reachability: not serving MCP → unreachable ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
  • 29 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • Tool “atisbo_connect” rewrote its description, which is the text the model reads security
    • Tool “atisbo_decide” rewrote its description, which is the text the model reads security
    • Tool “atisbo_map” rewrote its description, which is the text the model reads security
    • “atisbo_lookup” added an optional parameter “content_limit” cosmetic
    • “atisbo_lookup” added an optional parameter “content_offset” cosmetic
    • “atisbo_analyze” reworded the description of “limit” cosmetic
    • “atisbo_capture” reworded the description of “coverage_updates” cosmetic
    • “atisbo_capture” reworded the description of “note” cosmetic
    • “atisbo_capture” reworded the description of “source” cosmetic
    • “atisbo_connect” reworded the description of “collection_path” cosmetic
    • “atisbo_connect” reworded the description of “connection_id” cosmetic
    • “atisbo_connect” reworded the description of “pull_arguments” cosmetic
    • “atisbo_decide” reworded the description of “category” cosmetic
    • “atisbo_decide” reworded the description of “covered_claims” cosmetic
    • “atisbo_decide” reworded the description of “covered_ideas” cosmetic
    • “atisbo_decide” reworded the description of “criteria_left_out_reason” cosmetic
    • “atisbo_decide” reworded the description of “description” cosmetic
    • “atisbo_decide” reworded the description of “effort” cosmetic
    • “atisbo_decide” reworded the description of “expected_behavior” cosmetic
    • “atisbo_decide” reworded the description of “matrix” cosmetic
    • “atisbo_decide” reworded the description of “out_of_scope” cosmetic
    • “atisbo_decide” reworded the description of “pm_exception_reason” cosmetic
    • “atisbo_decide” reworded the description of “priority_boost” cosmetic
    • “atisbo_decide” reworded the description of “risk_notes” cosmetic
    • “atisbo_decide” reworded the description of “verification_method” cosmetic
    • “atisbo_lookup” reworded the description of “category” cosmetic
    • “atisbo_lookup” reworded the description of “command_id” cosmetic
    • “atisbo_lookup” reworded the description of “entity” cosmetic
    • “atisbo_lookup” reworded the description of “limit” cosmetic
    • “atisbo_lookup” reworded the description of “status” cosmetic
    • “atisbo_map” reworded the description of “binding_id” cosmetic
    • “atisbo_map” reworded the description of “description” cosmetic
    • “atisbo_map” reworded the description of “direction” cosmetic
    • “atisbo_map” reworded the description of “historical_data” cosmetic
    • “atisbo_map” reworded the description of “name” cosmetic
    • “atisbo_map” reworded the description of “regroup_level” cosmetic
    • “atisbo_map” reworded the description of “target_threshold” cosmetic
    • “atisbo_map” reworded the description of “updated_at” cosmetic
    • “atisbo_orient” reworded the description of “since_checkpoint” cosmetic
  • 26 Sept 26 0
    • “atisbo_capture” added an optional parameter “client_request_id” cosmetic
    • “atisbo_capture” added an optional parameter “ops” cosmetic
    • “atisbo_capture” added an optional parameter “patchOps” cosmetic
    • “atisbo_capture” added an optional parameter “patches” cosmetic
    • “atisbo_lookup” added an optional parameter “scope_type” cosmetic
    • “atisbo_capture” reworded the description of “agent_name” cosmetic
    • “atisbo_capture” reworded the description of “category” cosmetic
    • “atisbo_capture” reworded the description of “claim_id” cosmetic
    • “atisbo_capture” reworded the description of “content” cosmetic
    • “atisbo_capture” reworded the description of “coverage_updates” cosmetic
    • “atisbo_capture” reworded the description of “document_id” cosmetic
    • “atisbo_capture” reworded the description of “evidence” cosmetic
    • “atisbo_capture” reworded the description of “expected_content_hash” cosmetic
    • “atisbo_capture” reworded the description of “modality” cosmetic
    • “atisbo_capture” reworded the description of “node_id” cosmetic
    • “atisbo_capture” reworded the description of “note” cosmetic
    • “atisbo_capture” reworded the description of “scope_id” cosmetic
    • “atisbo_capture” reworded the description of “scope_type” cosmetic
    • “atisbo_capture” reworded the description of “solution_id” cosmetic
    • “atisbo_capture” reworded the description of “source” cosmetic
    • “atisbo_capture” reworded the description of “title” cosmetic
    • “atisbo_decide” reworded the description of “lifecycle” cosmetic
    • “atisbo_lookup” reworded the description of “claim_state” cosmetic
    • “atisbo_lookup” reworded the description of “command_id” cosmetic
    • “atisbo_lookup” reworded the description of “debug_score” cosmetic
    • “atisbo_lookup” reworded the description of “evidence_limit” cosmetic
    • “atisbo_lookup” reworded the description of “exception_cursor” cosmetic
    • “atisbo_lookup” reworded the description of “focus” cosmetic
    • “atisbo_lookup” reworded the description of “include_stale” cosmetic
    • “atisbo_lookup” reworded the description of “judgement_cursor” cosmetic
    • “atisbo_lookup” reworded the description of “map_id” cosmetic
    • “atisbo_lookup” reworded the description of “node_id” cosmetic
    • “atisbo_lookup” reworded the description of “query” cosmetic
    • “atisbo_lookup” reworded the description of “ref” cosmetic
    • “atisbo_lookup” reworded the description of “scope_id” cosmetic
    • “atisbo_lookup” reworded the description of “sort_by” cosmetic
    • “atisbo_lookup” reworded the description of “state” cosmetic
    • “atisbo_lookup” reworded the description of “status” cosmetic
    • “atisbo_lookup” reworded the description of “target_id” cosmetic
    • “atisbo_orient” reworded the description of “cursor” cosmetic

    40 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • “atisbo_lookup” added an optional parameter “command_id” cosmetic
    • “atisbo_capture” reworded the description of “category” cosmetic
    • “atisbo_decide” reworded the description of “criteria_left_out_reason” cosmetic
    • “atisbo_decide” reworded the description of “discard_reason” cosmetic
    • “atisbo_decide” reworded the description of “effort” cosmetic
    • “atisbo_decide” reworded the description of “force_reassign” cosmetic
    • “atisbo_decide” reworded the description of “pm_exception_reason” cosmetic
    • “atisbo_decide” reworded the description of “risk_notes” cosmetic
    • “atisbo_lookup” reworded the description of “evidence_limit” cosmetic
    • “atisbo_lookup” reworded the description of “limit” cosmetic
    • “atisbo_lookup” reworded the description of “state” cosmetic
    • “atisbo_map” reworded the description of “current_value” cosmetic
    • “atisbo_map” reworded the description of “historical_data” cosmetic
    • “atisbo_map” reworded the description of “preview” cosmetic
    • “atisbo_map” reworded the description of “provider” cosmetic
    • “atisbo_map” reworded the description of “target_threshold” cosmetic
    • “atisbo_map” reworded the description of “updated_at” cosmetic

    17 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 23 Sept 26 0
    • Tool “atisbo_analyze” rewrote its description, which is the text the model reads security
    • “atisbo_capture” added an optional parameter “claim_id” cosmetic
    • “atisbo_capture” added an optional parameter “node_id” cosmetic
    • “atisbo_capture” added an optional parameter “solution_id” cosmetic
    • “atisbo_lookup” added an optional parameter “entity” cosmetic
    • “atisbo_capture” reworded the description of “mode” cosmetic
    • “atisbo_capture” reworded the description of “scope_id” cosmetic
    • “atisbo_decide” reworded the description of “criteria_left_out_reason” cosmetic
    • “atisbo_decide” reworded the description of “mode” cosmetic
    • “atisbo_decide” reworded the description of “note” cosmetic
    • “atisbo_decide” reworded the description of “pm_exception_reason” cosmetic
    • “atisbo_lookup” reworded the description of “debug_score” cosmetic
    • “atisbo_lookup” reworded the description of “evidence_limit” cosmetic
    • “atisbo_lookup” reworded the description of “limit” cosmetic
    • “atisbo_lookup” reworded the description of “map_id” cosmetic
    • “atisbo_lookup” reworded the description of “mode” cosmetic
    • “atisbo_lookup” reworded the description of “node_id” cosmetic
    • “atisbo_map” reworded the description of “binding_id” cosmetic
    • “atisbo_map” reworded the description of “mode” cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://app.atisbo.dev/api/mcp

TLS unreached
DNSSEC secure

Validation of app.atisbo.dev. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
atisbo.dev. DS published 45139 13 Verified
app.atisbo.dev. Verified address RRset verified with the apex keys
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.atisbo.dev/api/mcp Unreachable
http (plaintext) http://app.atisbo.dev/api/mcp HTTPS enforced
MCP tools · 8 exposed · ~4,189 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
atisbo_analyze ~243

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.

NameTypeReqDescription
analysisstring–summary (prose), table, or chart kind (bar/line/scatter); trend aliases line.
cursorstring–From stream.next_cursor — pages grouped rows beyond `limit`.
domainstring–Free-text product area, resolved to map nodes.
filtersobject–Filters: AND across fields, OR within a field.
group_byarray–Row grouping dimensions (1-2).
limitnumber– Max grouped rows; over-asks clamp.
metricsarray–Aggregate metrics per group (1-4).
subjectstring–Dataset: claims (opportunities), solutions, or activity (decisions + events).
time_rangeobject–Preset (7d/30d/90d) or explicit from/to ISO dates. Defaults to 30d.
NameTypeReqDescription
dataobjectyes–
metaobjectyes–

No examples provided.

atisbo_capture ~501

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

NameTypeReqDescription
agent_namestring––
attachmentsarray–1-5 files; 3 MB combined.
body–––
capture_modestring–Knowledge routing; default signals_only.
captured_fromstring––
categorystring–knowledge: free-form category label ≤60 chars.
change_summarystring–Artefact change summary.
claim_idstring–knowledge: alias for scope_id (scope_type=claim).
classificationstring–Signal classification hint.
client_request_idstring–signal: retry key; resend the SAME key to retry.
contentstring–Knowledge content.
corrects_prior_evidenceboolean–signal: CORRECTS prior evidence, not repeats it. Records WHICH evidence it corrects (echoed as corrects) and attaches the snippet to that claim.
coverage_updates––buckets snippets/ideas/claims; snippets[].{snippet_id, status, rationale}
dirty_event_idstring–Dirty event resolved on success
document_idstring–Living document UUID (artefact modes).
evidenceobject–Evidence fields; document_id top-level.
expected_content_hashstring–doc_patch_context content_hash
file_namestring––
itemsarray–signal_batch, max 100.
knowledge_kindstring––
message–––
mime_typestring––
modalitystring–Q=Quote, O=Observation, M=Metric; inferred if omitted.
modestringyesCapture mode. Notes per mode in meta.guidance.
node_idstring–knowledge: alias for scope_id (scope_type=node).
notestring–Why it matters (signal).
ops–––
patchOps–––
patch_opsarray––
patches–––
scope_idstring–Target scope UUID; required for node/claim/solution/map.
scope_typestring–Scope kind; company = active workspace.
solution_idstring–knowledge: alias for scope_id (scope_type=solution).
sourcestring–Signal source.
textstring–Signal text.
titlestring–Knowledge title.

No output schema declared.

No examples provided.

atisbo_connect ~502

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.

NameTypeReqDescription
collection_pathstring–composio_create with pull_tool: dotted path to the record array if not inferable.
configobject–mode=create with provider: catalog required_fields. Stored encrypted, never readable again.
connection_idstring–Connection id from mode=list; required for configure/pause/resume/sync_now/delete.
json_pathsobject–create/configure: dotted paths into the POSTed payload's JSON body.
kindstring–mode=create: "email" provisions the ingest address; default webhook.
labelstring–create/configure: human name for the source, e.g. "Freshdesk".
modestring–list/catalog need no ids; others need connection_id or create fields.
providerstring–mode=create: NATIVE provider from catalog native_providers. Pair with config.
pull_argumentsobject–composio_create with pull_tool: action arguments.
pull_toolstring–composio_create, DAILY apps: read-only action from composio_actions.
querystring–mode=catalog only: filter by name, category or description.
rate_limitnumber–create/configure: max requests per minute accepted. Default 100.
recipe_idstring–mode=create: catalog recipe id — applies its curated mapping.
skip_attributionboolean–mode=create: true for anonymous public-forum sources with no attributable customer.
source_categorystring–mode=create with your own mapping: what the payload carries.
sync_everystring–PULL sources only: cadence. Default daily.
toolkitstring–composio_actions / composio_create: Composio app slug (e.g. "freshdesk", "jira").
trigger_slugstring–composio_create, INSTANT apps: trigger from composio_catalog.

No output schema declared.

No examples provided.

atisbo_decide ~1,169

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.

NameTypeReqDescription
agent_namestring–Signs comments/assignments/decisions. Default "Agent".
alternativesarray––
assign_node_idstring–update_solution: taxonomy node.
assign_to_agentboolean–update_solution: take ownership.
attach_claim_idsarray––
briefstring–dispatch_solution: agent brief.
categorystring–set_knowledge_category: free-form label; pass null to clear.
chosen_solution_idstring–update_solution: the winning sibling.
claim_idstring–Claim UUID — resolve names with atisbo_lookup mode=resolve first
claim_idsarray––
clear_discardboolean––
clear_operational_blockboolean––
clear_pm_exceptionboolean––
commentstring–update_solution: thread report as the agent.
contradictions_foundboolean–record_outcome (automated): attest a contradiction sweep.
covered_claimsarray–check_coverage: claim ids this work implements.
covered_ideasarray–check_coverage: idea ids from the coverage map.
criteria_left_outarray–update_solution: criteria left OUT (ADR-234); only with LAUNCHED.
criteria_left_out_reasonstring–Why each criterion is out; required with criteria_left_out.
decisionstring––
decision_typestring–log_decision: e.g. product_decision, note (full list in the error).
descriptionstring––
design_contextstring––
detach_claim_idsarray––
discard_reasonstring–update_solution: divergence loser (ADR-224); needs CANCELED.
document_idstring––
effortnumber–Size estimate, person-weeks. Sizing only, never affects order.
evidence_refsarray–record_outcome: durable evidence refs.
expected_behaviorarray–check_coverage: observable behavior delivered.
forceboolean–Confirms a source-deleting reassignment; omit = CONFIRMATION_REQUIRED.
force_reassignboolean–dispatch_solution: audited takeover of an in-progress Solution; omit refuses contested dispatch.
idstring–delete_knowledge / set_knowledge_category: doc id.
instructionstring––
is_deal_breakerboolean–deal_breaker: true = confirm/flag, false = reject/unflag.
kpi_afterstring––
kpi_beforestring––
lifecyclestring–IDEA|DESIGNING|IN_DEVELOPMENT; LAUNCHED only via update_solution.
main_featuresarray––
matrixarray–validate_delivery: one entry per success criterion.
metric_currentnumber–record_outcome (automated): fresh metric reading.
missionstring–update_strategy: informational only. ≤2000.
modestringyesResolve names to UUIDs before mutating; notes per mode in meta.guidance.
node_idstring––
notestring–record_outcome narrative max 5000; triage/log_decision rationale max 2000.
observed_atstring––
operational_block_categorystring––
operational_block_reasonstring–update_solution: operational blocker; not a decision.
out_of_scopearray–check_coverage: ids intentionally NOT addressed.
outcomestring–record_outcome: launch impact.
outcome_confidencestring––
pm_exception_reasonstring–update_solution / declare_pm_exception: needs a PERSON decision; not ops (use operational_block_reason).
pr_urlstring––
priority_boostnumber–update_solution: PM multiplier over evidence-weighted priority.
product_namestring––
refresh_schedulestring––
replace_confirmedboolean–validate_delivery: true ONLY to confirm deliberately replacing a longer recorded matrix with a shorter one.
review_kindstring––
risk_notesarray–check_coverage: unresolved contradictions acknowledged by id.
roadmapstring–update_strategy: informational only. ≤5000.
snippet_idstring––
snooze_clearboolean––
snooze_daysnumber––
solution_idstring–Solution UUID — resolve names with atisbo_lookup mode=resolve first
specobject––
statusstring–Target classification.
strategystring–update_strategy: the only functional field.
target_claim_idstring–Claim UUID — resolve names with atisbo_lookup mode=resolve first
target_idstring––
target_typestring––
titlestring––
unassignboolean––
updated_atstring–Optimistic lock; stale edits fail STALE_DATA.
verdictstring–mode=triage: BOTH values close the claim — see guidance.
verification_methodstring–record_outcome: how verified (max 500 chars).

No output schema declared.

No examples provided.

atisbo_lookup ~704

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

NameTypeReqDescription
action_cursorstring–work_queue action_queue cursor; restart at page 1 after a mutation.
anchoredstring–Claim list anchoring filter.
categorystring–knowledge: exact category filter.
claim_idstring–Claim UUID — resolve names with atisbo_lookup mode=resolve first
claim_statestring–Claim state; open=untouched.
command_idstring–receipts: probe ONE write — the exact key on a listed receipt; omit for your 25 latest.
content_limitnumber––
content_offsetnumber––
cursorstring–Pagination cursor from a previous response.
debug_scoreboolean–get claim: PowerScore breakdown.
depthstring–summary (alias: brief) = compact fields; work = full context (default).
dirty_event_idstring–doc_patch_context: loads this event's snippets.
document_idstring–Living document UUID.
entitystring–get: which entity kind the id field carries. Omit — the id field names the entity.
evidence_limitnumber–get entity=claim: evidence rows on page one (1–25); cursor reaches the rest.
exception_cursorstring–pages pm_exceptions.
focusstring–claims: agent_work | all.
include_staleboolean–claims: include stale claims.
judgement_cursorstring–pages needs_judgement.
lifecyclearray–Solution lifecycle filters.
limitnumber–Max results; delegates clamp per page. Page with next_cursor.
map_idstring–Map UUID (mode=get).
modestringyesNamed by its enum value; notes per mode in meta.guidance.
node_idstring–Node UUID (get; claims/solutions filter).
operational_block_cursorstring–work_queue: pages operational_blocks.
querystring–Topic search: claims/solutions/knowledge/context; resolve: name→id.
refstring–open: a handle ref (claim:UUID, snippet://UUID).
refsarray–open: several refs (max 10).
review_kindstring–unreviewed only (see atisbo_decide mode=mark_reviewed).
scopestring–Scope for context / living_doc list.
scope_idstring–Scope UUID unless scope/scope_type is company/workspace.
scope_typestring–Alias of scope (either name works); workspace is treated as company.
solution_idstring–Solution UUID — resolve names with atisbo_lookup mode=resolve first
sort_bystring–Solution order (priority = evidence-weighted × boost).
statestring–work tokens (todo=DESIGNING, active=agent-consumable) or post-launch kinds.
statusstring–Status filter.
target_idstring–UUID for claim/solution/node/map/doc.
typestring–claims: classification.
typesarray–resolve: entity kinds.
viewstring–work_queue: one whole bucket by whose move it is.

No output schema declared.

No examples provided.

atisbo_map ~649

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 (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.

NameTypeReqDescription
anchorsarray–Batch claim anchors.
assignmentsarray––
binding_idstring–metric_update: binding to update (atisbo_lookup mode=get, metrics[].id).
branch_optionsarray––
branchesarray–Branches for apply mode.
claim_idstring–Claim UUID — resolve names with atisbo_lookup mode=resolve first
claim_idsarray–link_claims: claims to place under node_id.
context_answersobject–Grounding answers for AI map generation.
current_valuenumber–metric_update: today's value; same-day re-entry replaces it.
descriptionstring–Map/node/branch description.
directionstring–regroup: broader merges similar claims; specific splits them.
edge_idstring–Edge UUID for delete_edge mode.
edge_typestring––
event_namestring––
grouping_modestring––
historical_dataarray–metric_update: full series REPLACEMENT (omit to append current_value).
labelstring––
levelnumber–Node hierarchy depth.
map_idstring–Map UUID.
map_typestring––
metric_namestring––
metric_typestring––
modestringyesNotes per mode in meta.guidance.
namestring–Map, node, or metric name.
new_levelnumber–New depth after a move.
new_parent_idstring–Move target parent; null promotes to root.
node_idstring–Node UUID.
notestring–link_claims: why these claims sit under this driver; stored on every link.
parent_idstring–Parent node UUID.
previewboolean–regroup: read-only preview. ALWAYS preview before executing.
providerstring–Metric provider: posthog, amplitude, stripe, manual…
regroup_levelstring–regroup direction=broader: merge aggressiveness.
snippet_idstring––
source_map_idstring––
source_node_idstring––
target_node_idstring––
target_thresholdnumber–regroup direction=specific: split similarity threshold.
target_valuenumber––
templatestring––
time_range_daysnumber––
updated_atstring–metric_update: binding updated_at from your last read (stale edits fail).

No output schema declared.

No examples provided.

atisbo_orient ~224

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.

NameTypeReqDescription
cursorstring–Pagination cursor.
depthstring–summary (alias: brief) = compact fields; work = full context (default).
limitnumber–Max items. snapshot clamps to 20; whats_new to 50.
modestring–snapshot (alias: workspace) uses task; whats_new uses since_checkpoint; strategy/integrations need no IDs.
since_checkpointstring–ISO 8601 checkpoint for delta reads.
taskstring–triage = untriaged inbox; planning = confirmed opportunities by priority; operations = signals & integrations; executive = KPIs & strategy.

No output schema declared.

No examples provided.

atisbo_support ~197

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.

NameTypeReqDescription
areastring–Narrows which checks run. Omit when unsure — the full set costs the same round-trip.
observed_errorstring–The failing error string VERBATIM — diagnostics cannot see the failed call, so this is often the only evidence.
problemstringyesWhat went wrong, in your words. Do NOT paste customer feedback, document bodies or credentials — this string IS filed if a report is created.
share_reportboolean–File a verdict-only report when the problem is not caller-side; false = diagnose only.
NameTypeReqDescription
dataobjectyes–
metaobjectyes–

No examples provided.

Install

How do I install the Atisbo MCP server?

Atisbo is a hosted endpoint at https://app.atisbo.dev/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.atisbo.dev

# add to Claude Code
claude mcp add --transport http brian8a1-atisbo 'https://app.atisbo.dev/api/mcp'
Common questions

What is the Atisbo MCP server?

Atisbo is an MCP server listed in the public MCP registry as io.github.brian8a1/atisbo. MCP tools over one Atisbo workspace: Signals, Opportunities, Backlog, Decisions, Living Documents. This page covers its hosted endpoint (https://app.atisbo.dev/api/mcp).

Is the Atisbo MCP server safe to use?

Atisbo scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Atisbo MCP server expose?

Atisbo exposes 8 tools: atisbo_orient, atisbo_lookup, atisbo_capture, atisbo_decide, atisbo_map, and 3 more. Their descriptions and schemas cost roughly 4,189 tokens of context every time the server is loaded.

Does the Atisbo MCP server require authentication?

Its publisher declares that Atisbo requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

Is the Atisbo MCP server still maintained?

Atisbo is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Atisbo MCP server?

VerifyMCP ran 3 checks on Atisbo, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Atisbo: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.