# KIRHA Search (remote · mcp.kirha.com)

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

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.kirha.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-kirha-search/mcp.md), [page](https://verifymcp.io/servers/com-kirha-search/mcp)

## Channel facts

- Endpoint: `https://mcp.kirha.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 331 tokens (~331/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the KIRHA Search MCP server?

KIRHA Search is a hosted endpoint at https://mcp.kirha.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-kirha-search 'https://mcp.kirha.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-kirha-search": {
      "url": "https://mcp.kirha.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-kirha-search": {
      "type": "http",
      "url": "https://mcp.kirha.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-kirha-search]
url = "https://mcp.kirha.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-kirha-search": {
      "type": "remote",
      "url": "https://mcp.kirha.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-kirha-search --url 'https://mcp.kirha.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-kirha-search:
    url: "https://mcp.kirha.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-kirha-search": {
      "Transport": "http",
      "Url": "https://mcp.kirha.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-kirha-search -t streamable-http -u 'https://mcp.kirha.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-kirha-search": {
      "type": "http",
      "url": "https://mcp.kirha.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `Search` (~254 tokens)

Search with KIRHA

Live, structured data from 50+ specialized providers in one call. Call this tool whenever an answer depends on facts that change over time or that you should not state from memory. A few examples among many more: market and crypto prices, wallets and DeFi, company records and financials, SEC filings, patents, clinical trials and drug safety, scientific papers, news, prediction markets, packages and CVEs, flights, weather. When no specialized provider fits, it falls back to web search, so it can replace a generic web search on any question. KIRHA plans the query, calls the right providers (SEC, PubMed, CoinGecko, GitHub, Polymarket and more) and returns each provider's raw result. Ask in plain language, there is nothing to configure.

Input parameters:

- `focus` (string): Optional vertical slug that restricts the search to one vertical. Leave it out unless the user asks for a specific vertical, since the search already covers all of them. Slugs are listed at https://d…
- `query` (string, required): The question to answer. Be specific: name the asset, company, place or period it is about.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-kirha-search/mcp#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79
- 2026-10-28: 78
- 2026-10-27: 78
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72
- 2026-10-14: 72

## Common questions

### What is the KIRHA Search MCP server?

KIRHA Search is an MCP server listed in the public MCP registry as com.kirha/search. The right context at the right time, from the world's leading data providers. One API. 800+ tools. This page covers its hosted endpoint (https://mcp.kirha.com/mcp).

### Is the KIRHA Search MCP server safe to use?

KIRHA Search scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the KIRHA Search MCP server expose?

KIRHA Search exposes 1 tool: Search. Their descriptions and schemas cost roughly 254 tokens of context every time the server is loaded.

### Does the KIRHA Search MCP server require authentication?

No. We connected to KIRHA Search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the KIRHA Search MCP server still maintained?

KIRHA Search is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.kirha.com/mcp
- Authorisation metadata: https://mcp.kirha.com/.well-known/oauth-protected-resource/mcp
- Website: https://kirha.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-kirha-search/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-kirha-search/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-kirha-search/mcp