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.

yellide

REMOTE · YELLIDE.COM

Species of India: find a species; count or list species by group, state, district, region or threat.

Available components

+3 this week 67 Trust /100

Last scanned (22 hours ago)

Scores higher than 52% 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 Security74
  • 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
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability36
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1938 tokens (~193/item across 10 items; 5 tools + 5 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 Management30
  • Stability observed for 9 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
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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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
    • Server version: 1.0.0 → 1.1.0 functional
  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1636 → 1910 ▼ functional
    • New resource “districts” functional
    • “count_species” added an optional parameter “district” cosmetic
    • “list_species” added an optional parameter “district” cosmetic
    • “count_species” reworded the description of “recorded_since” cosmetic
    • “list_species” reworded the description of “recorded_since” cosmetic
  • 14 Nov 26 +1

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

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 63

    First indexed and scored.

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://yellide.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=yellide.com CN=WE1,O=Google Trust Services,C=US 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA256 725150171ac654e80e90be1d6f75905a
SANs: yellide.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of yellide.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
yellide.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://yellide.com/mcp Verified 200
http (plaintext) http://yellide.com/mcp HTTPS enforced 301 https://yellide.com/mcp
MCP tools · 5 exposed · ~1,510 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
count_species ~543

How many species of India: documented, with an open record, threatened (IUCN CR, EN, VU), recorded in the last 10 years, endemic, and per IUCN category. All filters are optional and combine: "how many butterflies in India", "threatened birds in Kerala", "endemic frogs of the Western Ghats".

NameTypeReqDescription
described_sinceinteger–Species described in this year or later.
district––A district (LGD): its name, "Wayanad", or its LGD code; or a list of districts for an area that is made of districts (the Mahanadi delta: ["Cuttack", "Jagatsinghapur", "Kendrapara", "Puri"]), where e…
endemicboolean–true: only species a source marks as endemic to India; false: only species not marked. Some groups have no marks yet (the answer names them).
familystring–A family (Latin): "Elapidae", "Orchidaceae".
groupstring–A group of the list, or a word of it: "Birds", "butterflies", "mammals" (all mammal groups), "orchids". See yellide://groups.
iucnarray–IUCN Red List categories: CR, EN, VU, NT, LC, DD, NE (not assessed), or "threatened" (CR, EN, VU).
open_recordboolean–true: species with an open record from India; false: species known only from checklists and papers.
orderstring–An order (Latin): "Squamata", "Anura" (frogs), "Lepidoptera".
recorded_sinceinteger–Species with an open record placed in a state in this year or later; with a district, a GBIF record placed in the district.
regionstring–A WII biogeographic zone ("Western Ghats", "Himalaya", "North-East", "Islands"), a province ("Western Ghats: Mountains") or a province code ("5B"). See yellide://regions.
statestring–A state or union territory of India: "Karnataka". See yellide://states.
suborderstring–For order Squamata: "snakes" (Serpentes) or "lizards" (Sauria).

No output schema declared.

No examples provided.

find_species ~80

Find species of India by Latin name or English common name (any word of it, from its start: "great indian bustard", "naja", "cobra"). Returns up to 10 species with their key for get_species, group, IUCN category and status.

NameTypeReqDescription
namestringyesA Latin or English name, or its start.

No output schema declared.

No examples provided.

get_species ~116

One species of India by its key (from find_species or list_species): sources that list it, open record, states with an open record, WII regions, IUCN category with the year, DOI and trend of the assessment, endemic, year described and authority, family and order, evidence (type specimens, photos, DNA barcodes), names in Indian languages, a photo with its credit, and iNaturalist observations that wait for a name.

NameTypeReqDescription
keystringyesThe species key, such as "GCMS".

No output schema declared.

No examples provided.

list_species ~572

List species of India with optional filters that combine: "critically endangered species in India", "endangered animals in Karnataka", "snakes of the Western Ghats", "birds of Goa recorded since 2020". Rows by group, then Latin name; up to 100 per page, with the total and a cursor for the next page.

NameTypeReqDescription
cursorstring–next_cursor from the previous page.
described_sinceinteger–Species described in this year or later.
district––A district (LGD): its name, "Wayanad", or its LGD code; or a list of districts for an area that is made of districts (the Mahanadi delta: ["Cuttack", "Jagatsinghapur", "Kendrapara", "Puri"]), where e…
endemicboolean–true: only species a source marks as endemic to India; false: only species not marked. Some groups have no marks yet (the answer names them).
familystring–A family (Latin): "Elapidae", "Orchidaceae".
groupstring–A group of the list, or a word of it: "Birds", "butterflies", "mammals" (all mammal groups), "orchids". See yellide://groups.
iucnarray–IUCN Red List categories: CR, EN, VU, NT, LC, DD, NE (not assessed), or "threatened" (CR, EN, VU).
limitinteger–Rows per page, 1 to 100 (default 50).
open_recordboolean–true: species with an open record from India; false: species known only from checklists and papers.
orderstring–An order (Latin): "Squamata", "Anura" (frogs), "Lepidoptera".
recorded_sinceinteger–Species with an open record placed in a state in this year or later; with a district, a GBIF record placed in the district.
regionstring–A WII biogeographic zone ("Western Ghats", "Himalaya", "North-East", "Islands"), a province ("Western Ghats: Mountains") or a province code ("5B"). See yellide://regions.
statestring–A state or union territory of India: "Karnataka". See yellide://states.
suborderstring–For order Squamata: "snakes" (Serpentes) or "lizards" (Sauria).

No output schema declared.

No examples provided.

new_species ~199

Species described from India since a year (2007 or later), from Plazi, the BSI Plant Discoveries and the ZSI Animal Discoveries: the year, the group, the state of the type locality, the journal and a link to the paper, and whether it has been recorded since. "new species discovered in India 2025", "new frog species from India".

NameTypeReqDescription
cursorstring–next_cursor from the previous page.
groupstring–A group of the list, or a word of it: "Birds", "butterflies", "mammals" (all mammal groups), "orchids". See yellide://groups.
limitinteger–Rows per page, 1 to 100 (default 50).
sinceintegeryesDescribed in this year or later (2007 or later).
statestring–The state of the type locality.

No output schema declared.

No examples provided.

Install

How do I install the yellide MCP server?

yellide is a hosted endpoint at https://yellide.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 · yellide.com

# add to Claude Code
claude mcp add --transport http sathya-sankaran-yellide 'https://yellide.com/mcp'
Common questions

What is the yellide MCP server?

yellide is an MCP server listed in the public MCP registry as io.github.sathya-sankaran/yellide. Species of India: find a species; count or list species by group, state, district, region or threat. This page covers its hosted endpoint (https://yellide.com/mcp).

Is the yellide MCP server safe to use?

yellide scores 67 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 yellide MCP server expose?

yellide exposes 5 tools: find_species, get_species, count_species, list_species, new_species. Their descriptions and schemas cost roughly 1,510 tokens of context every time the server is loaded.

Does the yellide MCP server require authentication?

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

Is the yellide MCP server still maintained?

yellide 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 yellide MCP server?

VerifyMCP ran 13 checks on yellide, 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.