Skip to main content
Glama

Apex Tatva — Botanical Provenance for AI Agents

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation4/5

The canon-vs-provenance split gives each search/get pair a clearly distinct target resource, and verify_record_seal is unmistakably different from the retrieval tools. The only soft spot is list_records, whose name does not say it enumerates provenance records specifically (not canon texts), though the description resolves it.

Naming Consistency5/5

Every tool follows a strict snake_case verb_noun pattern (get_, list_, search_, verify_) with the noun consistently naming the resource. The parallel get_canon_text/get_provenance_record and search_canon/search_provenance pairs read as a coherent family.

Tool Count5/5

Six tools is well-scoped for a read-only corpus server: two search entry points, two record fetchers, an enumeration, and an integrity check. No filler or vanity tools are present.

Completeness4/5

The lifecycle for a read-only provenance corpus is essentially covered: locate via search, retrieve by id, enumerate all records, and verify integrity via SHA-256. Minor gaps remain, such as listing or paging the full 150-text canon corpus without a search term, or fetching the provenance records that cite a given canon text.

Available Tools

6 tools
get_canon_textGet a canonical source textA
Read-onlyIdempotent
Inspect

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.

Inputs: id (required).

get_provenance_recordGet provenance recordA
Read-onlyIdempotent
Inspect

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

Inputs: id (required).

list_recordsList recordsA
Read-onlyIdempotent
Inspect

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

Inputs: no named parameters.

search_canonSearch the canonical corpusA
Read-onlyIdempotent
Inspect

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.

Inputs: query (required), limit.

search_provenanceSearch provenance recordsA
Read-onlyIdempotent
Inspect

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.

Inputs: query (required), limit.

verify_record_sealVerify record sealA
Read-onlyIdempotent
Inspect

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

Inputs: id (required), hash (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Post-quantum document anchoring for AI agents. Anchor any SHA-256 hash to Algorand mainnet with ML-DSA-65 (NIST FIPS-204) signatures and receive a self-contained proof bundle verifiable offline — decades from now, without trusting any vendor.
      13 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Verifies blockchain-anchored timestamp proofs entirely on the user's machine, with five tools: hash a file, verify a file against a proof, verify a known hash against inline proof data, explain what a proof asserts, and create a new proof through ProofLedger. Verification recomputes the SHA-256 and walks the Merkle path locally instead of asking the issuer; only create uses the network.
      5
      68 PyPI
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources