Apex Tatva — Botanical Provenance for AI Agents

store.apex-tat-va.www/apex-tatva

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

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "apex-tatva": {
      "url": "https://www.apex-tat-va.store/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http apex-tatva https://www.apex-tat-va.store/mcp
VS Code
code --add-mcp '{"name":"apex-tatva","type":"http","url":"https://www.apex-tat-va.store/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Health & Science
Version
2.1.0
Registry
active
Published
11/17/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: Apex Tatva — Botanical Provenance for AI Agents is hosted endpoint answering without a key.

Maintained
No commit data
The repository has not been read yet, so the last-commit date is unknown.
Official registry
Active
Published as store.apex-tat-va.www/apex-tatva in the official MCP registry, version 2.1.0.
Source
No licence found
Public repository, but GitHub reports no recognised licence. Check the README before shipping it in a product.
Runs
Hosted by the publisher
Your client talks to www.apex-tat-va.store: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 00:07 UTCStatus history & uptime →
● Working674 msprotocol 2025-06-18v2.1.0tools

The endpoint answered the MCP handshake as "Apex tat-va" and listed 6 tools. Answering since Nov 18, 2026.

Context cost ≈ 980 tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 6 tools.

Tools (6)

  • search_provenance2 params

    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.

    Show parameters
    • querystringrequiredHerb name, category or traditional use, e.g. 'ashwagandha' or 'sleep'.
    • limitintegerMaximum number of records to return.
  • get_provenance_record1 param

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

    Show parameters
    • idstringrequiredRecord id, e.g. 'ashw-kshira'.
  • list_records

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

  • verify_record_seal2 params

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

    Show parameters
    • idstringrequiredRecord id the hash belongs to.
    • hashstringrequiredThe 64-character SHA-256 seal hash you stored.
  • search_canon2 params

    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.

    Show parameters
    • querystringrequiredText title, author, tradition, pillar or topic, e.g. 'Charaka', 'Tibetan', 'Pulse' or 'Nighantu'.
    • limitintegerMaximum number of canon entries to return.
  • get_canon_text1 param

    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.

    Show parameters
    • idstringrequiredCanon text id, e.g. 'charaka' or 'gyuzhi'.

Checked by Serverdex with a plain initialize + tools/list call to www.apex-tat-va.store/mcp, no credentials, about once a day. A failed check is never a removal.

Remotes

  • streamable-httphttps://www.apex-tat-va.store/mcp

The most-starred Health & Science servers in the index, with their live-check result.

ServerStarsLast pushLive check
Arxiv MCP Server3,284Nov 2026Local / not checked
com.medplum MCP2,802Nov 2026Needs sign-in
Tooluniverse1,791Nov 2026Local / not checked
Mirobody1,639Nov 2026Local / not checked
Tavotto712Nov 2026Local / not checked

Apex Tatva — Botanical Provenance for AI Agents: questions people ask

Is Apex Tatva — Botanical Provenance for AI Agents a remote or a local MCP server?
According to its entry in the official MCP registry, Apex Tatva — Botanical Provenance for AI Agents ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Apex Tatva — Botanical Provenance for AI Agents need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Apex Tatva — Botanical Provenance for AI Agents safe to use?
Mostly fine: Apex Tatva — Botanical Provenance for AI Agents is hosted endpoint answering without a key. In detail — maintained: No commit data; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
What tools does Apex Tatva — Botanical Provenance for AI Agents expose?
6 tools as listed by the server itself during the live check, including search_provenance, get_provenance_record, list_records, verify_record_seal, search_canon. The full list with parameters is in the Live check section above.
How do I add Apex Tatva — Botanical Provenance for AI Agents to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. APEX PSIAppend-only evidence receipts for AI records: seal, verify, cite, chain-check, anchor status.★ 1
  2. Apex Tatva — Ayurveda, Herbal & Botanical Provenance with Manuscript Citations4-tier provenance and SHA-256 seals for ayurvedic, herbal, botanical records. Not medical advice.
Browse all Health & Science →

Add the badge to your site

Show visitors that Apex Tatva — Botanical Provenance for AI Agents is listed here — it’s also the link we check for a free listing.

Apex Tatva — Botanical Provenance for AI Agents — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/store-apex-tat-va-www-apex-tatva?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Apex Tatva — Botanical Provenance for AI Agents — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Apex Tatva — Botanical Provenance for AI Agents — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/store-apex-tat-va-www-apex-tatva?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/store-apex-tat-va-www-apex-tatva) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/store-apex-tat-va-www-apex-tatva) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/store-apex-tat-va-www-apex-tatva)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/store-apex-tat-va-www-apex-tatva"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/store-apex-tat-va-www-apex-tatva"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/store-apex-tat-va-www-apex-tatva"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).