# Apex Tatva — Botanical Provenance for AI Agents (remote · www.apex-tat-va.store)

Four-tier botanical provenance with SHA-256 seals. Not medical advice.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.apex-tat-va.store`: 75/100 (this document), [markdown](https://verifymcp.io/servers/store-apex-tat-va-www-apex-tatva/www.md), [page](https://verifymcp.io/servers/store-apex-tat-va-www-apex-tatva/www)

## Channel facts

- Endpoint: `https://www.apex-tat-va.store/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.1.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-21.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 673 tokens (~112/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Apex Tatva — Botanical Provenance for AI Agents MCP server?

Apex Tatva — Botanical Provenance for AI Agents is a hosted endpoint at https://www.apex-tat-va.store/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 store-apex-tat-va-www-apex-tatva 'https://www.apex-tat-va.store/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "store-apex-tat-va-www-apex-tatva": {
      "url": "https://www.apex-tat-va.store/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "store-apex-tat-va-www-apex-tatva": {
      "type": "http",
      "url": "https://www.apex-tat-va.store/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.store-apex-tat-va-www-apex-tatva]
url = "https://www.apex-tat-va.store/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "store-apex-tat-va-www-apex-tatva": {
      "type": "remote",
      "url": "https://www.apex-tat-va.store/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add store-apex-tat-va-www-apex-tatva --url 'https://www.apex-tat-va.store/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  store-apex-tat-va-www-apex-tatva:
    url: "https://www.apex-tat-va.store/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "store-apex-tat-va-www-apex-tatva": {
      "Transport": "http",
      "Url": "https://www.apex-tat-va.store/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add store-apex-tat-va-www-apex-tatva -t streamable-http -u 'https://www.apex-tat-va.store/mcp'
```

### Other

```json
{
  "mcpServers": {
    "store-apex-tat-va-www-apex-tatva": {
      "type": "http",
      "url": "https://www.apex-tat-va.store/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-20 (score 75, +1)

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

### 2026-11-19 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-18 (score 74)

First indexed and scored.

## MCP tools (6)

### `search_provenance` (~92 tokens)

Search provenance records

Search botanical provenance records by herb name, category or a traditionally described use. Each record has four tiers (manuscript source, research status, recorded cautions, disagreements) and a SHA-256 seal.

Input parameters:

- `limit` (integer): Maximum number of records to return.
- `query` (string, required): Herb name, category or traditional use, e.g. 'ashwagandha' or 'sleep'.

### `get_provenance_record` (~57 tokens)

Get provenance record

Fetch one provenance record by its id (from search_provenance or list_records), with its four tiers and SHA-256 seal.

Input parameters:

- `id` (string, required): Record id, e.g. 'ashw-kshira'.

### `list_records` (~24 tokens)

List records

List the id, name and category of every provenance record currently in the corpus.

### `verify_record_seal` (~69 tokens)

Verify record seal

Check a SHA-256 seal you stored earlier against the current record. Tells you whether the record is unchanged since that hash was taken.

Input parameters:

- `hash` (string, required): The 64-character SHA-256 seal hash you stored.
- `id` (string, required): Record id the hash belongs to.

### `search_canon` (~116 tokens)

Search the canonical corpus

Search the 150-text canonical corpus of classical botanical and medical traditions. Returns the source texts behind the provenance records: title, author, era, tradition or pillar, synopsis, a defining quoted line, and topic domains. Use this to locate the manuscript a claim originates in.

Input parameters:

- `limit` (integer): Maximum number of canon entries to return.
- `query` (string, required): Text title, author, tradition, pillar or topic, e.g. 'Charaka', 'Tibetan', 'Pulse' or 'Nighantu'.

### `get_canon_text` (~81 tokens)

Get a canonical source text

Fetch one canonical source text by id (from search_canon). Returns its full record: title and native title, author, era, tradition or pillar, language, chapter and verse counts, synopsis, defining quoted line, and topic domains.

Input parameters:

- `id` (string, required): Canon text id, e.g. 'charaka' or 'gyuzhi'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/store-apex-tat-va-www-apex-tatva/www#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74

## Common questions

### What is the Apex Tatva — Botanical Provenance for AI Agents MCP server?

Apex Tatva — Botanical Provenance for AI Agents is an MCP server listed in the public MCP registry as store.apex-tat-va.www/apex-tatva. Four-tier botanical provenance with SHA-256 seals. Not medical advice. This page covers its hosted endpoint (https://www.apex-tat-va.store/mcp).

### Is the Apex Tatva — Botanical Provenance for AI Agents MCP server safe to use?

Apex Tatva — Botanical Provenance for AI Agents scores 75 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 Apex Tatva — Botanical Provenance for AI Agents MCP server expose?

Apex Tatva — Botanical Provenance for AI Agents exposes 6 tools: search_provenance, get_provenance_record, list_records, verify_record_seal, search_canon, get_canon_text. Their descriptions and schemas cost roughly 439 tokens of context every time the server is loaded.

### Does the Apex Tatva — Botanical Provenance for AI Agents MCP server require authentication?

No. We connected to Apex Tatva — Botanical Provenance for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Apex Tatva — Botanical Provenance for AI Agents MCP server still maintained?

Apex Tatva — Botanical Provenance for AI Agents is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Apex Tatva — Botanical Provenance for AI Agents MCP server?

VerifyMCP ran 13 checks on Apex Tatva — Botanical Provenance for AI Agents, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.apex-tat-va.store/mcp
- Repository: https://github.com/kawal393/apex-tatva-guardian
- Website: https://www.apex-tat-va.store/developers
- Changelog RSS feed: https://verifymcp.io/servers/store-apex-tat-va-www-apex-tatva/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/store-apex-tat-va-www-apex-tatva/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/store-apex-tat-va-www-apex-tatva/www.json
- HTML version of this page: https://verifymcp.io/servers/store-apex-tat-va-www-apex-tatva/www
