Prowl MCP

chat.prowlPublished by prowl.chatOfficial publisherv1.7.0Updated Oct 29, 2026

Real-world market data for AI agents: 444 pay-per-call tools (SEO, ads, social, trends, finance)

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Remote MCP endpoint giving AI assistants pay-per-call access to real-world market data across SEO, ads, social, trends and finance.

What you can do
  • Calls a catalog of 444 pay-per-call data tools covering SEO, advertising, social media, trend and finance data.
  • Retrieves real-world market data for an assistant to analyze or report on.
  • Connects over streamable HTTP to a hosted endpoint, authenticated with a bearer API key.
  • Applies optional scopes such as categories, spend limits and IP allowlists to the key.
When to use it
Useful when an assistant needs live market, SEO, advertising, social or financial data rather than general web search, and when per-call billing with spend limits is acceptable.
Requirements
A remote streamable HTTP endpoint at prowl.chat; no local package or runtime. An OAuth-based bearer API key sent in the Authorization header, with optional scopes for categories, spend limits and IP allowlist. Network access to the provider.
Before you install
Each tool call is billed, so usage can cost money; set spend limits on the key. The API key is a secret sent in the Authorization header and should be scoped and kept private. Queries and data requests go to a third-party service.

Installation

In SourceWeft

  1. Open Prowl MCP 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/chat.prowl%2Fprowl-mcp/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": {
    "prowl": {
      "type": "http",
      "url": "https://prowl.chat/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

2
  1. v1.7.0LatestSep 29, 2026
  2. v1.6.0Sep 16, 2026

Score

67% 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.

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

Other Prowl integrations