councilof_mcp

io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv1.0.1Updated Oct 24, 2026

CouncilOf.AI MCP — the UK sovereign defence BFT council orchestrator. UK MOD + AUKUS Pillar 2 procur

The publisher's own server: Council of AI GSPC

VerifiedSTDIODesktop only

Overview

AI-generated overview

A local MCP server described as a UK sovereign defence BFT council orchestrator, with no documented tools or usage details.

What you can do
The registry description identifies this as "CouncilOf.AI MCP — the UK sovereign defence BFT council orchestrator" and mentions "UK MOD + AUKUS Pillar 2 procur". No README, tool list, or capability documentation is provided, so the concrete tools it exposes to an assistant cannot be determined from the available material.
When to use it
There is not enough documented information to say when this server is worth adding. It appears aimed at defence-sector council or procurement orchestration, but no workflows, tools, or outputs are described.
Requirements
Runs as a local process on the user's machine via the PyPI package councilof_mcp, launched with uvx, over stdio. Desktop only; no web executable. No authentication, environment variables, or headers are declared.
Before you install
No tools, data flows, or credentials are documented, so what the server reads, writes, or sends cannot be assessed before installing. The description references UK defence and AUKUS procurement contexts, which may involve sensitive or restricted material; treat any such use as requiring its own authorisation. The package is third-party and undocumented here.

Installation

In SourceWeft

  1. Open councilof_mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Councilof integrations