Zencap

ai.zencapPublished by zencap.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Institutional financial data with SEC filing citations, for every AI agent. OAuth 2.1.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Zencap is a remote MCP server that gives AI assistants institutional financial data with SEC filing citations, connected over OAuth.

What you can do
Provides institutional financial data to the assistant, with citations pointing back to SEC filings. Connects as a hosted remote endpoint rather than a local package. Access is gated by OAuth 2.1 sign-in. No individual tools are listed in the supplied material, so the exact operations are not documented here.
When to use it
Useful when an assistant needs financial figures that can be traced to SEC filings, for example research or analysis where source citations matter. It is a hosted service, so it suits users who prefer not to run a local server.
Requirements
A remote MCP connection to the provider's hosted endpoint, plus an OAuth 2.1 sign-in with the provider. No environment variables or headers are declared. Network access is required.
Before you install
Authentication is required through OAuth, so the assistant is granted access to a provider account; review what that account exposes before connecting. Queries and any account data go to the third-party provider. The supplied material does not describe write actions or payments.

Installation

In SourceWeft

  1. Open Zencap 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/ai.zencap%2Fzencap/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": {
    "zencap": {
      "type": "http",
      "url": "https://mcp.zencap.ai/mcp"
    }
  }
}

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

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.