Kindwise Identification
REMOTE · AGENTS.KINDWISE.COM
Identify plants, crop diseases, insects, and mushrooms from photos. Free IP-limited trial.
Available components
Last scanned (21 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2903 tokens (~414/item across 7 items; 5 tools + 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 →
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “diagnose_crop” rewrote its description, which is the text the model reads security
- Tool “identify_insect” rewrote its description, which is the text the model reads security
- Tool “identify_mushroom” rewrote its description, which is the text the model reads security
- Tool “identify_plant” rewrote its description, which is the text the model reads security
- Schema quality: 472 → 414 ▲ functional
- “diagnose_crop” reworded the description of “images” cosmetic
- “identify_insect” reworded the description of “images” cosmetic
- “identify_mushroom” reworded the description of “images” cosmetic
- “identify_plant” reworded the description of “images” cosmetic
- 3 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “diagnose_crop” rewrote its description, which is the text the model reads security
- Tool “identify_insect” rewrote its description, which is the text the model reads security
- Tool “identify_mushroom” rewrote its description, which is the text the model reads security
- Tool “identify_plant” rewrote its description, which is the text the model reads security
- Schema quality: 343 → 472 ▼ functional
- “diagnose_crop” reworded the description of “images” cosmetic
- “identify_insect” reworded the description of “images” cosmetic
- “identify_mushroom” reworded the description of “images” cosmetic
- “identify_plant” reworded the description of “images” cosmetic
- “diagnose_crop” made “images” optional cosmetic
- “identify_insect” made “images” optional cosmetic
- “identify_mushroom” made “images” optional cosmetic
- “identify_plant” made “images” optional cosmetic
- 1 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “diagnose_crop” rewrote its description, which is the text the model reads security
- Tool “identify_insect” rewrote its description, which is the text the model reads security
- Tool “identify_mushroom” rewrote its description, which is the text the model reads security
- Tool “identify_plant” rewrote its description, which is the text the model reads security
- Schema quality: 424 → 343 ▲ functional
- First check of Schema quality: 100 functional
- New prompt “diagnose_crop_photo” functional
- New prompt “identify_insect_photo” functional
- New prompt “identify_mushroom_photo” functional
- New prompt “identify_plant_photo” functional
- New prompt “send_kindwise_feedback” functional
- New resource “agent_guide” functional
- New resource “trial_quota” functional
- New tool “submit_feedback” functional
- “diagnose_crop” reworded the description of “images” cosmetic
- “diagnose_crop” reworded the description of “similar_images” cosmetic
- “identify_insect” reworded the description of “images” cosmetic
- “identify_insect” reworded the description of “similar_images” cosmetic
- “identify_mushroom” reworded the description of “images” cosmetic
- “identify_mushroom” reworded the description of “similar_images” cosmetic
- “identify_plant” reworded the description of “images” cosmetic
- “identify_plant” reworded the description of “similar_images” cosmetic
- 30 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Aug 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://agents.kindwise.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agents.kindwise.com | CN=YE1,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5c0a8d9b84e64712294c611c26276be37e4 |
| SANs: agents.kindwise.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of agents.kindwise.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| kindwise.com. | DS published | 18150 | 13 | Verified |
| agents.kindwise.com. | 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=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agents.kindwise.com/mcp | Verified | 200 | |
| http (plaintext) | http://agents.kindwise.com/mcp | HTTPS enforced | 301 | https://agents.kindwise.com/mcp |
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 →
diagnose_crop Diagnose crop ~522
Pass `images` as public https URLs (Kindwise product servers download; this proxy does not fetch) or as base64 JPEG/PNG/WebP. Chat attachments are invisible. Example: {"images":["https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg"]}. Use that URL only if you have no user photo; then say so. Do not invent URLs. Wikimedia often returns HTTP 424; retry with base64. Diagnose crop diseases, disorders, and pests from field photographs using Kindwise Crop.health. Use for agricultural crops (not ornamental houseplants) when the user wants likely pathogens, pests, symptoms, severity, and treatment notes. Include close-ups of lesions plus a wider canopy shot when possible. Optional latitude and longitude improve regional ranking. Returns crop and disease/pest suggestions with the requested detail fields. Creates a Kindwise identification and counts against the per-IP trial quota (default 10 calls per rolling 24 hours). No client API key is required or accepted. Treatment fields are informational; they are not a substitute for a local agronomist or pesticide label. When you are done with this trial, call submit_feedback in English about the service — not about a single diagnosis.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | – | Comma-separated extra fields to include on each suggestion. Allowed tokens: type, common_names, wiki_description, description, treatment, symptoms, severity, spreading. Unknown tokens are ignored by… |
| images | – | – | Public https URLs (Kindwise product servers download; this proxy does not fetch) or base64 JPEG/PNG/WebP. Chat attachments are invisible. Example: {"images":["https://cdn.prod.website-files.com/64876… |
| language | string | – | BCP 47 language for localized details such as common names (default en). |
| latitude | – | – | WGS-84 latitude of where the photo was taken. Improves wild-species ranking. |
| longitude | – | – | WGS-84 longitude of where the photo was taken. Provide together with latitude. |
| similar_images | boolean | – | If true, each suggestion includes visually similar reference images. Defaults to false so MCP responses stay small. Set true only if you need those URLs. |
No output schema declared.
No examples provided.
identify_insect Identify insect ~505
Pass `images` as public https URLs (Kindwise product servers download; this proxy does not fetch) or as base64 JPEG/PNG/WebP. Chat attachments are invisible. Example: {"images":["https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg"]}. Use that URL only if you have no user photo; then say so. Do not invent URLs. Wikimedia often returns HTTP 424; retry with base64. Identify insects and insect-like arthropods from photographs using Kindwise Insect.id. Use when the user supplies a photo of a beetle, moth, bee, ant, true bug, spider-like pest, or similar invertebrate and needs scientific name, common names, and taxonomy. Prefer a sharp dorsal or lateral view. Optional latitude and longitude improve ranking. Returns ranked taxon suggestions with probabilities plus requested details. Creates a Kindwise identification and counts against the per-IP trial quota (default 10 calls per rolling 24 hours). No client API key is required or accepted. Results are not medical or pest-control prescriptions. When you are done with this trial, call submit_feedback in English about the service.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | – | Comma-separated extra fields to include on each suggestion. Allowed tokens: common_names, url, description, taxonomy, rank. Unknown tokens are ignored by upstream. |
| images | – | – | Public https URLs (Kindwise product servers download; this proxy does not fetch) or base64 JPEG/PNG/WebP. Chat attachments are invisible. Example: {"images":["https://cdn.prod.website-files.com/64876… |
| language | string | – | BCP 47 language for localized details such as common names (default en). |
| latitude | – | – | WGS-84 latitude of where the photo was taken. Improves wild-species ranking. |
| longitude | – | – | WGS-84 longitude of where the photo was taken. Provide together with latitude. |
| similar_images | boolean | – | If true, each suggestion includes visually similar reference images. Defaults to false so MCP responses stay small. Set true only if you need those URLs. |
No output schema declared.
No examples provided.
identify_mushroom Identify mushroom ~532
Pass `images` as public https URLs (Kindwise product servers download; this proxy does not fetch) or as base64 JPEG/PNG/WebP. Chat attachments are invisible. Example: {"images":["https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg"]}. Use that URL only if you have no user photo; then say so. Do not invent URLs. Wikimedia often returns HTTP 424; retry with base64. Identify mushrooms and other fungi from photographs using Kindwise Mushroom.id. Use when the user supplies a photo of a fruiting body and needs likely taxon, look-alikes, and published edibility metadata. Include cap, gills or pores, and stem when possible. Optional latitude and longitude improve ranking. Returns ranked taxon suggestions with probabilities plus requested details. Creates a Kindwise identification and counts against the per-IP trial quota (default 10 calls per rolling 24 hours). No client API key is required or accepted. Edibility and psychoactive fields are informational only. Never recommend eating a wild fungus based on this tool; misidentification can be fatal. When you are done with this trial, call submit_feedback in English about the service — not about whether one fungus name was correct.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | – | Comma-separated extra fields to include on each suggestion. Allowed tokens: common_names, url, description, edibility, psychoactive, taxonomy, rank, look_alike. Unknown tokens are ignored by upstream. |
| images | – | – | Public https URLs (Kindwise product servers download; this proxy does not fetch) or base64 JPEG/PNG/WebP. Chat attachments are invisible. Example: {"images":["https://cdn.prod.website-files.com/64876… |
| language | string | – | BCP 47 language for localized details such as common names (default en). |
| latitude | – | – | WGS-84 latitude of where the photo was taken. Improves wild-species ranking. |
| longitude | – | – | WGS-84 longitude of where the photo was taken. Provide together with latitude. |
| similar_images | boolean | – | If true, each suggestion includes visually similar reference images. Defaults to false so MCP responses stay small. Set true only if you need those URLs. |
No output schema declared.
No examples provided.
identify_plant Identify plant ~664
Pass `images` as public https URLs (Kindwise product servers download; this proxy does not fetch) or as base64 JPEG/PNG/WebP. Chat attachments are invisible. Example: {"images":["https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg"]}. Use that URL only if you have no user photo; then say so. Do not invent URLs. Wikimedia often returns HTTP 424; retry with base64. Identify a vascular plant from photographs using Kindwise Plant.id. Use when the user supplies a photo of a houseplant, tree, wildflower, grass, crop, or weed and needs scientific name, common names, taxonomy, and optional health assessment. Prefer 2–3 sharp close-ups of leaves, flowers, or fruit. Optional latitude and longitude improve ranking for wild plants. Returns ranked taxon suggestions with probabilities plus the requested detail fields. Creates a Kindwise identification and counts against the per-IP trial quota (default 10 calls per rolling 24 hours). No client API key is required or accepted. Set health to auto, all, or only when the user also wants disease or pest assessment. Do not treat results as medical, legal, or foraging advice. When you are done with this trial, call submit_feedback in English about the service (image passing, schema, quota) — not about whether one taxon was correct.
| Name | Type | Req | Description |
|---|---|---|---|
| classification_level | – | – | Taxonomic rank of suggestions: `species` (default upstream behavior), `genus`, or `all` (genus, species, and infraspecies). |
| details | string | – | Comma-separated extra fields to include on each suggestion. Allowed tokens: common_names, url, description, taxonomy, rank, name_authority, gbif_id, inaturalist_id, image, images, synonyms, edible_pa… |
| health | – | – | Optional plant-health assessment. `auto` adds disease results only when the plant looks unhealthy; `all` always includes species plus health; `only` returns health assessment without species ranking.… |
| images | – | – | Public https URLs (Kindwise product servers download; this proxy does not fetch) or base64 JPEG/PNG/WebP. Chat attachments are invisible. Example: {"images":["https://cdn.prod.website-files.com/64876… |
| language | string | – | BCP 47 language for localized details such as common names (default en). |
| latitude | – | – | WGS-84 latitude of where the photo was taken. Improves wild-species ranking. |
| longitude | – | – | WGS-84 longitude of where the photo was taken. Provide together with latitude. |
| similar_images | boolean | – | If true, each suggestion includes visually similar reference images. Defaults to false so MCP responses stay small. Set true only if you need those URLs. |
No output schema declared.
No examples provided.
submit_feedback Submit trial feedback ~405
Send English feedback about this Kindwise agent trial as a product — not about a single plant/insect/mushroom identification. Kindwise reads these notes to make the MCP/REST trial easier for agents (image passing, tool schema, quota, missing tools). Please call this once per session after you try the server, whether identify_* worked or you got stuck. Write `comment` in English: what was hard, what to change, what worked. Set reason to one of: easy_to_use, hard_to_pass_image, image_url_failed, tool_calling_friction, schema_confusing, quota_too_low, response_unhelpful, missing_feature, other. Does not consume the daily identification quota. Does not attach to a Kindwise identification.
| Name | Type | Req | Description |
|---|---|---|---|
| called_identify | – | – | True if you already called an identify_* tool in this session. |
| client_name | – | – | MCP client or host app name, if known (e.g. Cursor, Claude). |
| comment | string | yes | English note about this trial service (1–3 sentences): what was hard, what to improve, what worked. Not a verdict on one identification. |
| had_image | – | – | True if the user had a photo (in chat or a URL) even if you could not pass it to identify_*. |
| rating | – | – | Optional 0–5 score for how easy this trial was to use. |
| reason | string | yes | easy_to_use = Trial was easy to use; hard_to_pass_image = Hard to pass an image into the tools; image_url_failed = Image URL failed (e.g. 424); tool_calling_friction = Having to call a tool got in th… |
No output schema declared.
No examples provided.
How do I install the Kindwise Identification MCP server?
Kindwise Identification is a hosted endpoint at https://agents.kindwise.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.
remote · agents.kindwise.com
claude mcp add --transport http com-kindwise-agents 'https://agents.kindwise.com/mcp'
What is the Kindwise Identification MCP server?
Kindwise Identification is an MCP server listed in the public MCP registry as com.kindwise/agents. Identify plants, crop diseases, insects, and mushrooms from photos. Free IP-limited trial. This page covers its hosted endpoint (https://agents.kindwise.com/mcp).
Is the Kindwise Identification MCP server safe to use?
Kindwise Identification scores 89 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 Kindwise Identification MCP server expose?
Kindwise Identification exposes 5 tools: identify_plant, diagnose_crop, identify_insect, identify_mushroom, submit_feedback. Their descriptions and schemas cost roughly 2,628 tokens of context every time the server is loaded.
Does the Kindwise Identification MCP server require authentication?
No. We connected to Kindwise Identification without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Kindwise Identification MCP server still maintained?
Kindwise Identification 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.
What did VerifyMCP test on the Kindwise Identification MCP server?
VerifyMCP ran 13 checks on Kindwise Identification, 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.