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.

io.github.devrobinransom/baos-mcp

NPM · BAOS-HARNESS

Read-only MCP access to a BAOS workspace: product graphs, requirements, evidence, research.

Available components

+3 this week 65 Trust /100

Last scanned (4 hours ago)

Scores higher than 33% of npm servers

Category Memory and Knowledge

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 16 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability46
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 1254 tokens (~27/item across 45 items; 45 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 45 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 46 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

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 · Analysed npm/baos-harness@0.7.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 45 exposed · ~1,231 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
change_impact ~39

Read-only BAOS change_impact

NameTypeReqDescription
depthinteger––
idsarrayyes–
maxNodesinteger––

No output schema declared.

No examples provided.

check_freshness ~26

Read-only BAOS check_freshness

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

explain_semantic_node ~26

Read-only BAOS explain_semantic_node

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_assertion ~24

Read-only BAOS get_assertion

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_capability_reality ~42

Read-only BAOS get_capability_reality

NameTypeReqDescription
idstringyes–
policyobject––
viewstring––

No output schema declared.

No examples provided.

get_claim ~22

Read-only BAOS get_claim

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_claim_evidence ~26

Read-only BAOS get_claim_evidence

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_collaboration_identity ~43

Read-only BAOS get_collaboration_identity

NameTypeReqDescription
projectIdstringyes–
tenantIdstringyes–
workspaceIdstringyes–

No output schema declared.

No examples provided.

get_contradictions ~26

Read-only BAOS get_contradictions

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_cycle_status ~17

Read-only BAOS get_cycle_status

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_environment_intake ~19

Read-only BAOS get_environment_intake

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_evidence_reference ~26

Read-only BAOS get_evidence_reference

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_flow_delivery_trace ~26

Read-only BAOS get_flow_delivery_trace

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

get_flow_reality ~26

Read-only BAOS get_flow_reality

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

get_human_view ~33

Read-only BAOS get_human_view

NameTypeReqDescription
limitinteger––
viewstringyes–

No output schema declared.

No examples provided.

get_neighbors ~22

Read-only BAOS get_neighbors

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_permission ~22

Read-only BAOS get_permission

NameTypeReqDescription
idstring––

No output schema declared.

No examples provided.

get_problem_outcome ~26

Read-only BAOS get_problem_outcome

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

get_product_implications ~26

Read-only BAOS get_product_implications

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_pulse ~17

Read-only BAOS get_pulse

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_read_model ~52

Read-only BAOS get_read_model

NameTypeReqDescription
idstring––
idsarray––
limitinteger––
modelstringyes–
sincestring––

No output schema declared.

No examples provided.

get_readout ~17

Read-only BAOS get_readout

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_reality_change ~42

Read-only BAOS get_reality_change

NameTypeReqDescription
baseTypestringyes–
headTypestringyes–
idstringyes–

No output schema declared.

No examples provided.

get_reality_revision ~19

Read-only BAOS get_reality_revision

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_research_case ~26

Read-only BAOS get_research_case

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_research_plan ~26

Read-only BAOS get_research_plan

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_research_readout ~28

Read-only BAOS get_research_readout

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_search_observation ~26

Read-only BAOS get_search_observation

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_semantic_node ~26

Read-only BAOS get_semantic_node

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_source ~22

Read-only BAOS get_source

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_unknowns ~24

Read-only BAOS get_unknowns

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_workflow ~24

Read-only BAOS get_workflow

NameTypeReqDescription
idstring––

No output schema declared.

No examples provided.

inspect_agent_run ~25

Read-only BAOS inspect_agent_run

NameTypeReqDescription
runIdstring––

No output schema declared.

No examples provided.

list_assertions ~17

Read-only BAOS list_assertions

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_decision_contracts ~21

Read-only BAOS list_decision_contracts

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_decisions ~17

Read-only BAOS list_decisions

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_questions ~15

Read-only BAOS list_questions

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_requirements ~17

Read-only BAOS list_requirements

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_decision_case ~41

Read-only BAOS prepare_decision_case

NameTypeReqDescription
contractstringyes–
evidenceIdsarray––
stateobjectyes–

No output schema declared.

No examples provided.

project_overview ~17

Read-only BAOS project_overview

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

query ~48

Read-only BAOS query

NameTypeReqDescription
idstring––
idsarray––
limitinteger––
modelstringyes–
sincestring––

No output schema declared.

No examples provided.

search_semantics ~31

Read-only BAOS search_semantics

NameTypeReqDescription
limitinteger––
querystring––

No output schema declared.

No examples provided.

semantic_diff ~53

Read-only BAOS semantic_diff

NameTypeReqDescription
acceptedPatchobject––
baseobject––
baseTypestring––
headobject––
headTypestring––

No output schema declared.

No examples provided.

trace_semantic_path ~48

Read-only BAOS trace_semantic_path

NameTypeReqDescription
fromstring––
idstring––
maxNodesinteger––
tostring––

No output schema declared.

No examples provided.

verify_project ~15

Read-only BAOS verify_project

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.devrobinransom/baos-mcp server?

io.github.devrobinransom/baos-mcp runs locally as an npm package, launched with npx -y baos-harness. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · baos-harness

# add to Claude Code
claude mcp add devrobinransom-baos-mcp -- npx -y baos-harness
Common questions

What is the io.github.devrobinransom/baos-mcp server?

io.github.devrobinransom/baos-mcp is listed in the public MCP registry as io.github.devrobinransom/baos-mcp. Read-only MCP access to a BAOS workspace: product graphs, requirements, evidence, research. This page covers its npm package (baos-harness).

Is the io.github.devrobinransom/baos-mcp server safe to use?

io.github.devrobinransom/baos-mcp scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.devrobinransom/baos-mcp server expose?

io.github.devrobinransom/baos-mcp exposes 45 tools: change_impact, check_freshness, explain_semantic_node, get_assertion, get_capability_reality, and 40 more. Their descriptions and schemas cost roughly 1,231 tokens of context every time the server is loaded.

Is the io.github.devrobinransom/baos-mcp server still maintained?

io.github.devrobinransom/baos-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.devrobinransom/baos-mcp server under?

io.github.devrobinransom/baos-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.