KIRHA Search

com.kirhaPublished by kirha.comOfficial publisherv1.0.0Updated Oct 24, 2026

The right context at the right time, from the world's leading data providers. One API. 800+ tools.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingFinance

Overview

AI-generated overview

KIRHA Search is a remote MCP server that gives an assistant one search tool for live, structured data from many specialized providers.

What you can do
Run a single search that returns live, structured data from a large set of specialized providers in one call, covering topics such as market and crypto prices, wallets and DeFi, company records and financials, and regulatory filings.
When to use it
Useful when answers depend on facts that change over time or that the assistant should not state from memory, such as prices, company records or filings, and you want one search entry point instead of many separate data integrations.
Requirements
Remote endpoint at mcp.kirha.com over streamable HTTP. A KIRHA API key is required, sent in the Authorization header as a Bearer token; the Bearer prefix is optional. Tool listing works without the key, but searches require it.
Before you install
The API key is a secret sent in the Authorization header; keep it private and revoke it if exposed. Search queries and their parameters are sent to KIRHA and its third-party data providers, so avoid including confidential information in queries.

Installation

In SourceWeft

  1. Open KIRHA Search 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.kirha%2Fsearch/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": {
    "kirha-search": {
      "type": "http",
      "url": "https://mcp.kirha.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

1

Version history

1
  1. v1.0.0LatestOct 14, 2026

Score

83% 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 listedRequired15 pts
  • 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.