# yellide (remote · yellide.com)

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

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `yellide.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/sathya-sankaran-yellide/yellide.md), [page](https://verifymcp.io/servers/sathya-sankaran-yellide/yellide)

## Channel facts

- Endpoint: `https://yellide.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 36/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http sathya-sankaran-yellide 'https://yellide.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "sathya-sankaran-yellide": {
      "url": "https://yellide.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sathya-sankaran-yellide": {
      "type": "http",
      "url": "https://yellide.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sathya-sankaran-yellide]
url = "https://yellide.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add sathya-sankaran-yellide --url 'https://yellide.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sathya-sankaran-yellide:
    url: "https://yellide.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "sathya-sankaran-yellide": {
      "Transport": "http",
      "Url": "https://yellide.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sathya-sankaran-yellide -t streamable-http -u 'https://yellide.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "sathya-sankaran-yellide": {
      "type": "http",
      "url": "https://yellide.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-11-21 (score 67, +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-11-19 (score 66, +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.

### 2026-11-17 (score 65, +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.

### 2026-11-16 (score 64, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-11-15 (score 64, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1636 → 1910
- [functional] New resource “districts”
- [cosmetic] “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”

### 2026-11-14 (score 64, +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.

### 2026-11-13 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 63)

First indexed and scored.

## MCP tools (5)

### `find_species` (~80 tokens)

Find a species by name

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.

Input parameters:

- `name` (string, required): A Latin or English name, or its start.

### `get_species` (~116 tokens)

One species in full

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.

Input parameters:

- `key` (string, required): The species key, such as "GCMS".

### `count_species` (~543 tokens)

Count species

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

Input parameters:

- `described_since` (integer): 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…
- `endemic` (boolean): 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).
- `family` (string): A family (Latin): "Elapidae", "Orchidaceae".
- `group` (string): A group of the list, or a word of it: "Birds", "butterflies", "mammals" (all mammal groups), "orchids". See yellide://groups.
- `iucn` (array): IUCN Red List categories: CR, EN, VU, NT, LC, DD, NE (not assessed), or "threatened" (CR, EN, VU).
- `open_record` (boolean): true: species with an open record from India; false: species known only from checklists and papers.
- `order` (string): An order (Latin): "Squamata", "Anura" (frogs), "Lepidoptera".
- `recorded_since` (integer): Species with an open record placed in a state in this year or later; with a district, a GBIF record placed in the district.
- `region` (string): A WII biogeographic zone ("Western Ghats", "Himalaya", "North-East", "Islands"), a province ("Western Ghats: Mountains") or a province code ("5B"). See yellide://regions.
- `state` (string): A state or union territory of India: "Karnataka". See yellide://states.
- `suborder` (string): For order Squamata: "snakes" (Serpentes) or "lizards" (Sauria).

### `list_species` (~572 tokens)

List species

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.

Input parameters:

- `cursor` (string): next_cursor from the previous page.
- `described_since` (integer): 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…
- `endemic` (boolean): 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).
- `family` (string): A family (Latin): "Elapidae", "Orchidaceae".
- `group` (string): A group of the list, or a word of it: "Birds", "butterflies", "mammals" (all mammal groups), "orchids". See yellide://groups.
- `iucn` (array): IUCN Red List categories: CR, EN, VU, NT, LC, DD, NE (not assessed), or "threatened" (CR, EN, VU).
- `limit` (integer): Rows per page, 1 to 100 (default 50).
- `open_record` (boolean): true: species with an open record from India; false: species known only from checklists and papers.
- `order` (string): An order (Latin): "Squamata", "Anura" (frogs), "Lepidoptera".
- `recorded_since` (integer): Species with an open record placed in a state in this year or later; with a district, a GBIF record placed in the district.
- `region` (string): A WII biogeographic zone ("Western Ghats", "Himalaya", "North-East", "Islands"), a province ("Western Ghats: Mountains") or a province code ("5B"). See yellide://regions.
- `state` (string): A state or union territory of India: "Karnataka". See yellide://states.
- `suborder` (string): For order Squamata: "snakes" (Serpentes) or "lizards" (Sauria).

### `new_species` (~199 tokens)

New species described from India

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

Input parameters:

- `cursor` (string): next_cursor from the previous page.
- `group` (string): A group of the list, or a word of it: "Birds", "butterflies", "mammals" (all mammal groups), "orchids". See yellide://groups.
- `limit` (integer): Rows per page, 1 to 100 (default 50).
- `since` (integer, required): Described in this year or later (2007 or later).
- `state` (string): The state of the type locality.

## Diagnostics

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

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 64
- 2026-11-15: 64
- 2026-11-14: 64
- 2026-11-13: 63
- 2026-11-12: 63

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

## Links

- Remote endpoint: https://yellide.com/mcp
- Repository: https://github.com/urbanmorph/overlooked
- Website: https://yellide.com/
- Changelog RSS feed: https://verifymcp.io/servers/sathya-sankaran-yellide/yellide.xml
- Changelog JSON feed: https://verifymcp.io/servers/sathya-sankaran-yellide/yellide/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/sathya-sankaran-yellide/yellide.json
- HTML version of this page: https://verifymcp.io/servers/sathya-sankaran-yellide/yellide
