Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kweku Anansi Herbarium

REMOTE · KWEKUANANSI.AI

What the Kweku Anansi herbarium records about plants of West and Central Africa. Never a dose.

Available components

+4 this week 80 Trust /100

Last scanned (17 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 482 tokens (~160/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 16 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “herbarium.about” rewrote its description, which is the text the model reads security
    • Tool “herbarium.find” rewrote its description, which is the text the model reads security
    • Tool “herbarium.about” changed its title: About the Kweku Anansi herbarium → About the KwekuAnansi herbarium cosmetic
    • Tool “herbarium.find” changed its title: Find a plant in the Kweku Anansi herbarium → Find a plant in the KwekuAnansi herbarium cosmetic
  • 15 Nov 26 +1

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

  • 14 Nov 26 +1
    • DNSSEC: fail → pass ▲ security
  • 13 Nov 26 +1
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.07 ▲ functional
  • 12 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://kwekuanansi.ai/mcp/herbarium

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kwekuanansi.ai CN=YR1,O=Let's Encrypt,C=US 17 Oct 2026 15 Jan 2027 RSA 2048 SHA256-RSA 5a9703a2d747be131c28ec7c7c14426de31
SANs: kwekuanansi.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of kwekuanansi.ai. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
kwekuanansi.ai. DS published 2371 13 Verified
kwekuanansi.ai. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; img-src 'self' data: https://fal.media https://*.fal.media; media-src 'self' data: blob:; font-src 'self' data:; style-src 'self'; script-src 'self'; connect-src 'self' https://anansi.cashplanet.io https://fal.media https://*.fal.media; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://kwekuanansi.ai/mcp/herbarium Verified 200
http (plaintext) http://kwekuanansi.ai/mcp/herbarium HTTPS enforced 308 https://kwekuanansi.ai/mcp/herbarium
MCP tools · 3 exposed · ~371 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
herbarium.about ~61

Use this when someone asks what the KwekuAnansi herbarium is, how many plants it holds, where its records come from or what it leaves out. Do not use it to look up a plant: use herbarium.find or herbarium.card.

Input schema present but exposes no named parameters.

NameTypeReqDescription
cardsintegeryes–
community_knowledgestringyes–
creditsstringyes–
disclaimerstringyes–
does_not_coverstringyes–
explore_urlstring––
held_backstringyes–
herbarium_builtstring––
herbarium_urlstringyes–
high_riskinteger––
one_speciesinteger––
with_a_use_on_recordinteger––
with_a_warninginteger––

No examples provided.

herbarium.card ~147

Use this when someone asks what is recorded about one named plant of West or Central Africa: its names, family, warnings, the uses a collector or a desk note recorded, and how many notes are held back. Give the warnings first and say where each row comes from. Do not use it to recommend a remedy, and do not add an amount, how often, how long or a way to prepare one: the herbarium holds such notes back, and a use on record is not evidence that it works or that it is safe.

NameTypeReqDescription
plantstringyesThe plant's scientific name, a common name the herbarium lists for it, or the slug herbarium.find returned.
NameTypeReqDescription
card_urlstring––
creditsstring––
disclaimerstring––
explore_urlstring––
familystring––
foundbooleanyes–
high_riskboolean––
namesarray––
notes_heldobject––
other_notes_on_sheetinteger––
plantstring––
rankstring––
recorded_as_harmarray––
saysstring––
scientific_namestring––
serious_illness_notestring––
slugstring––
tested_not_supportedarray––
usesarray––
warningsarray––

No examples provided.

herbarium.find ~163

Use this when someone names a plant of West or Central Africa by its scientific name or a common name (for example "Azadirachta indica", "sobolo" or "prekese") and you need to know whether the KwekuAnansi herbarium has a card for it. It returns the matching cards with family and rank, and says plainly when a plant is not in the herbarium yet. Do not use it to identify a plant from a description or a photograph, or for a plant from outside Africa: it matches names as written, and a plant that is not found may be there under another name.

NameTypeReqDescription
namestringyesThe plant's scientific name ("Vernonia amygdalina") or a common name ("bitter leaf").
NameTypeReqDescription
cards_in_herbariuminteger––
explore_urlstring––
flags_notestring––
herbarium_builtstring––
matchedstringyes–
matchesarrayyes–
namestringyes–
saysstringyes–

No examples provided.

Install

How do I install the Kweku Anansi Herbarium MCP server?

Kweku Anansi Herbarium is a hosted endpoint at https://kwekuanansi.ai/mcp/herbarium, 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.

remote · kwekuanansi.ai

# add to Claude Code
claude mcp add --transport http ai-kwekuanansi-herbarium 'https://kwekuanansi.ai/mcp/herbarium'
Common questions

What is the Kweku Anansi Herbarium MCP server?

Kweku Anansi Herbarium is an MCP server listed in the public MCP registry as ai.kwekuanansi/herbarium. What the Kweku Anansi herbarium records about plants of West and Central Africa. Never a dose. This page covers its hosted endpoint (https://kwekuanansi.ai/mcp/herbarium).

Is the Kweku Anansi Herbarium MCP server safe to use?

Kweku Anansi Herbarium scores 80 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 Kweku Anansi Herbarium MCP server expose?

Kweku Anansi Herbarium exposes 3 tools: herbarium.find, herbarium.card, herbarium.about. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.

Does the Kweku Anansi Herbarium MCP server require authentication?

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

Is the Kweku Anansi Herbarium MCP server still maintained?

Kweku Anansi Herbarium 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 Kweku Anansi Herbarium MCP server?

VerifyMCP ran 13 checks on Kweku Anansi Herbarium, 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.