Caplia

io.github.Caplia-TechPublished by GitHub account Caplia-Techv1.0.0Updated Oct 24, 2026

MCP server for VC pitch-deck scoring, thesis-fit matching, and deal-flow management.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote MCP server that lets an assistant score VC pitch decks, match them to an investment thesis, and manage deal flow in Caplia.

What you can do
Caplia exposes its venture platform to an assistant over a remote streamable HTTP endpoint. According to the registry description, it covers VC pitch-deck scoring, thesis-fit matching, and deal-flow management. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Worth adding when an assistant should work inside a Caplia venture workspace, for example to evaluate incoming pitch decks, check how a company fits a fund's thesis, or keep deal-flow records up to date.
Requirements
A remote endpoint at mcp.venture.caplia.ai over streamable HTTP. Authentication is OAuth and required; requests carry an Authorization header holding a bearer token taken from Settings → API Keys in the Caplia portal. No local runtime or environment variables are declared.
Before you install
The Authorization header carries a secret API key; treat it as a credential and do not expose it. Production keys are identifiable by the cap_in_live_ prefix. Scoring and deal-flow tools may write or change records in your Caplia workspace, so review actions before they run.

Installation

In SourceWeft

  1. Open Caplia in the dashboard and add it to a workspace.
  2. Connect the required 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/io.github.Caplia-Tech%2Fcaplia/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "caplia": {
      "type": "http",
      "url": "https://mcp.venture.caplia.ai/"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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
  • 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.