Client Posture

com.clientposturePublished by clientposture.comOfficial publisherv1.0.0Updated Nov 1, 2026

Client Posture scans, findings, prospect deal stages, pipeline summary, and quote drafts for MSPs.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that gives an assistant access to Client Posture scans, findings, prospect deal stages, pipeline summaries and quote drafts for MSPs.

What you can do
  • Review security scans and their findings
  • Track prospect deal stages and summarize the sales pipeline
  • Draft quotes for prospects
  • All actions run against the user's Client Posture account through a hosted endpoint
When to use it
Useful for managed service providers who already run Client Posture and want an assistant to pull scan results, check pipeline status or prepare quote drafts without switching tools.
Requirements
A remote streamable HTTP endpoint at the provider's site; no local install. Requires a Client Posture account with a per-person API key created in Settings under AI assistants, available on Pro or Founding Partner plans, sent as a bearer token in the Authorization header.
Before you install
The API key is a secret sent in the Authorization header and grants access to your account data; keep it private and revoke it if exposed. The server can create quote drafts, so check generated content before sending it to clients. Scan, prospect and pipeline data is shared with the assistant through the provider's hosted service.

Installation

In SourceWeft

  1. Open Client Posture in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.clientposture%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "client-posture": {
      "type": "http",
      "url": "https://www.clientposture.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 1, 2026

Score

56% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.