Kindwise Identification MCP server
com.kindwise/agentskindwise.comstreamable-httpv1.0.0Scanned
Identify plants, crop diseases, insects, and mushrooms from photos. Free IP-limited trial.
5 tools: 1 do something that can't be undone and 4 change things.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Kindwise Identification MCP server can do
The Kindwise Identification MCP server is published by kindwise.com, a domain the MCP Registry verified. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (submit_feedback) and create or change data (4 tools: identify_plant, diagnose_crop, identify_insect and identify_mushroom), but cannot delete data. None of its tools only reads.
4 tools bring in text other people can write (identify_plant, diagnose_crop, identify_insect and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Can't be undone 1Claude Code: ask
submit_feedbackSend English feedback about this Kindwise agent trial as a product — not about a single plant/insect/mushroom identification.No findings
Why it is in this group
- The name "submit_feedback" says "submit": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- title: Submit trial feedback
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 4Claude Code: ask
diagnose_cropPass `images` as public https URLs (Kindwise product servers download; this proxy does not fetch) or as base64 JPEG/PNG/WebP.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Diagnose crop
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
identify_insectPass `images` as public https URLs (Kindwise product servers download; this proxy does not fetch) or as base64 JPEG/PNG/WebP.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Identify insect
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
identify_mushroomPass `images` as public https URLs (Kindwise product servers download; this proxy does not fetch) or as base64 JPEG/PNG/WebP.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Identify mushroom
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
identify_plantPass `images` as public https URLs (Kindwise product servers download; this proxy does not fetch) or as base64 JPEG/PNG/WebP.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Identify plant
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://agents.kindwise.com/mcp: tools/list returned 5 tools to an anonymous client, including submit_feedback (irreversible), identify_plant (write), diagnose_crop (write), identify_insect (write), identify_mushroom (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http agents https://agents.kindwise.com/mcpclaude mcp add --transport http agents https://agents.kindwise.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__agents__identify_plant",
"mcp__agents__diagnose_crop",
"mcp__agents__identify_insect",
"mcp__agents__identify_mushroom",
"mcp__agents__submit_feedback"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agents. Review it before you use it.
Capability tags behind 4 rules
- mcp__agents__identify_plant untrusted-input
- mcp__agents__diagnose_crop untrusted-input
- mcp__agents__identify_insect untrusted-input
- mcp__agents__identify_mushroom untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.kindwise/agents/verify?hash=992c925eb1ad403f4c8009427ab1e0e8c0ff284352a7da3e2d0efbb2e5fe0602" | jq -e '.changed == false'Pinned hash 992c925eb1ad, from Nov 13, 2026, 15:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.kindwise/agents/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.kindwise/agents)Source: MCP Registry. Synced Oct 21, 2026, 17:57 UTC.
Kindwise Identification MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Kindwise Identification MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Kindwise Identification MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Kindwise Identification MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: submit_feedback.
What tools does the Kindwise Identification MCP server have?
- 5 tools: 1 irreversible, 4 write. submit_feedback, identify_plant, diagnose_crop, identify_insect and identify_mushroom.
Does the Kindwise Identification MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Kindwise Identification MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Kindwise Identification MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.