Coaia Sequential Thinking MCP Server

mcp-coaia-sequential-thinking PyPI v0.3.13

Published by miadisabelle — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

CoAiA's Structural Core: Guiding Intelligent Agents with Foundational Creative Thinking

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 4

high Shell/command execution in server code (debug_mcp_connection.py)MTC-SRC-002

In the server's implementation (`debug_mcp_connection.py:11`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: r process process = subprocess.Popen( [sys.executable, "-u", server_path], # -u for unbuffered output

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server debug_mcp_connection.py

high Shell/command execution in server code (llms/sync_llms_ordered.py)MTC-SRC-002

In the server's implementation (`llms/sync_llms_ordered.py:26`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: . """ process = subprocess.run( ["python3", os.path.join(LLMS_DIR, "transform_llms_content.py")],

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server llms/sync_llms_ordered.py

high Shell/command execution in server code (mcp_coaia_sequential_thinking/wrapper.py)MTC-SRC-002

In the server's implementation (`mcp_coaia_sequential_thinking/wrapper.py:28`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: args try: subprocess.run(command, check=True) except subprocess.CalledProcessError as e: print

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server mcp_coaia_sequential_thinking/wrapper.py

high Shell/command execution in server code (test_creative_orientation.py)MTC-SRC-002

In the server's implementation (`test_creative_orientation.py:83`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: result = subprocess.run(cmd, capture_output=True, text=True, cwd=".") if result.

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server test_creative_orientation.py

Tools 38

Each tool and what it can reach — statically extracted from the published source.

  • adjust_exploration_balanceno sensitive capability
  • advance_creative_emergenceno sensitive capability
  • advance_thinking_chainno sensitive capability
  • check_agent_creative_orientationno sensitive capability
  • check_integration_statusno sensitive capability
  • clear_historyno sensitive capability
  • conduct_novelty_searchno sensitive capability
  • create_agent_collaborationno sensitive capability
  • create_consensus_decisionno sensitive capability
  • discover_emergent_opportunitiesno sensitive capability
Show 28 more tools ↓
  • establish_system_goalno sensitive capability
  • evaluate_resilient_connectionno sensitive capability
  • export_sessionno sensitive capability
  • generate_active_pause_draftsno sensitive capability
  • generate_summaryno sensitive capability
  • get_active_thinking_chainsno sensitive capability
  • get_consensus_decision_statusno sensitive capability
  • get_constitutional_audit_trailno sensitive capability
  • get_goal_progressno sensitive capability
  • get_lattice_statusno sensitive capability
  • get_task_statusno sensitive capability
  • get_thinking_chain_statusno sensitive capability
  • import_sessionno sensitive capability
  • initialize_polycentric_latticeno sensitive capability
  • initiate_creative_emergenceno sensitive capability
  • initiate_sequential_thinkingno sensitive capability
  • integrate_emergent_possibilityno sensitive capability
  • list_constitutional_principlesno sensitive capability
  • make_constitutional_decisionno sensitive capability
  • process_thoughtno sensitive capability
  • provide_human_responseno sensitive capability
  • query_agent_capabilitiesno sensitive capability
  • request_human_consultationno sensitive capability
  • run_full_analysis_chainno sensitive capability
  • submit_agent_taskno sensitive capability
  • synthesize_thinking_chainno sensitive capability
  • validate_constitutional_complianceno sensitive capability
  • validate_thought_contentno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.3.13 latest A 93/100 4 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-coaia-sequential-thinking/badge.svg)](https://mcptrustchecker.com/registry/mcp-coaia-sequential-thinking)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-coaia-sequential-thinking"><img src="https://mcptrustchecker.com/registry/mcp-coaia-sequential-thinking/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-coaia-sequential-thinking/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-coaia-sequential-thinking --online --registry pypi

Use the free API → How scoring works

More in Learning & Documentation