# Kindwise Identification (remote · agents.kindwise.com)

Identify plants, crop diseases, insects, and mushrooms from photos. Free IP-limited trial.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `agents.kindwise.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-kindwise-agents/agents.md), [page](https://verifymcp.io/servers/com-kindwise-agents/agents)

## Channel facts

- Endpoint: `https://agents.kindwise.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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 5 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 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.

### Claude

```bash
claude mcp add --transport http com-kindwise-agents 'https://agents.kindwise.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-kindwise-agents": {
      "url": "https://agents.kindwise.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-kindwise-agents": {
      "type": "http",
      "url": "https://agents.kindwise.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-kindwise-agents]
url = "https://agents.kindwise.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-kindwise-agents": {
      "type": "remote",
      "url": "https://agents.kindwise.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-kindwise-agents --url 'https://agents.kindwise.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-kindwise-agents:
    url: "https://agents.kindwise.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-kindwise-agents": {
      "Transport": "http",
      "Url": "https://agents.kindwise.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-kindwise-agents -t streamable-http -u 'https://agents.kindwise.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-kindwise-agents": {
      "type": "http",
      "url": "https://agents.kindwise.com/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-09-19 (score 85, +1)

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

### 2026-09-17 (score 84, +1)

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

### 2026-09-15 (score 83, +1)

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

### 2026-09-13 (score 82, +1)

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

### 2026-09-11 (score 81, +1)

- [security] 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
- [functional improvement] Schema quality: 472 → 414
- [cosmetic] “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”

### 2026-09-09 (score 80, +1)

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

### 2026-09-07 (score 79, +1)

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

### 2026-09-05 (score 78, +1)

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

## MCP tools (5)

### `identify_plant` (~664 tokens)

Identify plant

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.

Input parameters:

- `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.

### `diagnose_crop` (~522 tokens)

Diagnose crop

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.

Input parameters:

- `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.

### `identify_insect` (~505 tokens)

Identify insect

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.

Input parameters:

- `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.

### `identify_mushroom` (~532 tokens)

Identify mushroom

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.

Input parameters:

- `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.

### `submit_feedback` (~405 tokens)

Submit trial feedback

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.

Input parameters:

- `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, required): 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, required): 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…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-kindwise-agents/agents#diagnostics

## Score history

- 2026-09-21: 85
- 2026-09-20: 85
- 2026-09-19: 85
- 2026-09-18: 84
- 2026-09-17: 84
- 2026-09-16: 83
- 2026-09-15: 83
- 2026-09-14: 82
- 2026-09-13: 82
- 2026-09-12: 81
- 2026-09-11: 81
- 2026-09-10: 80
- 2026-09-09: 80
- 2026-09-08: 79
- 2026-09-07: 79
- 2026-09-06: 78
- 2026-09-05: 78
- 2026-09-04: 77
- 2026-09-03: 77
- 2026-09-02: 77
- 2026-09-01: 76
- 2026-08-31: 73
- 2026-08-30: 72
- 2026-08-29: 72

## Common questions

### 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 85 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agents.kindwise.com/mcp
- Website: https://agents.kindwise.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-kindwise-agents/agents.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-kindwise-agents/agents.json
- HTML version of this page: https://verifymcp.io/servers/com-kindwise-agents/agents