# Malinica (remote · api.malinica.rs)

Search classified listings on Malinica, a Serbian free serbian classifieds marketplace.

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

## Components

- remote · `api.malinica.rs`: 87/100 (this document), [markdown](https://verifymcp.io/servers/rs-malinica-classifieds/api.md), [page](https://verifymcp.io/servers/rs-malinica-classifieds/api)

## Channel facts

- Endpoint: `https://api.malinica.rs/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**: 80/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 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**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 981 tokens (~163/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Malinica MCP server?

Malinica is a hosted endpoint at https://api.malinica.rs/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 rs-malinica-classifieds 'https://api.malinica.rs/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "rs-malinica-classifieds": {
      "url": "https://api.malinica.rs/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "rs-malinica-classifieds": {
      "type": "http",
      "url": "https://api.malinica.rs/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.rs-malinica-classifieds]
url = "https://api.malinica.rs/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rs-malinica-classifieds": {
      "type": "remote",
      "url": "https://api.malinica.rs/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rs-malinica-classifieds --url 'https://api.malinica.rs/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  rs-malinica-classifieds:
    url: "https://api.malinica.rs/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "rs-malinica-classifieds": {
      "Transport": "http",
      "Url": "https://api.malinica.rs/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add rs-malinica-classifieds -t streamable-http -u 'https://api.malinica.rs/mcp'
```

### Other

```json
{
  "mcpServers": {
    "rs-malinica-classifieds": {
      "type": "http",
      "url": "https://api.malinica.rs/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-21 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-09-20 (score 87, +1)

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

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

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

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

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

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

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

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

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

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

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

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

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

## MCP tools (6)

### `get_categories` (~86 tokens)

List every active listing category as a flat catalog. Each entry has a numeric id, a dot-separated path encoding its place in the hierarchy (for example vozila.automobili is a child of vozila), and a human-readable title in Serbian. Call this first to translate what a user is looking for into a category id, then call get_category to learn which attributes that category supports.

### `get_category` (~148 tokens)

Describe one category and the attributes listings in it can be filtered by. Each attribute has a name (the key to use when filtering), a label, and a type giving the JSON value a filter must supply: string, number, boolean or date (ISO 8601). An attribute may also carry options, which are the only accepted values for it; value_type with min and max, bounding what numbers are accepted; or a picklist_path, whose accepted values are not listed here and must be fetched with get_picklist_values. A picklist_depends_on names another attribute whose value narrows this one.

Input parameters:

- `categoryId` (integer, required): Numeric category id, as returned by get_categories

### `get_listing` (~130 tokens)

Fetch one published listing by id, including its full description, price, location, category and stored attribute values. Attribute keys match the names reported by get_category for that listing's category, and attributes holds the raw stored values. Under the same key, attribute_labels gives that attribute's display label, plus a value label where the value comes from a fixed set such as a picklist or enum — use the labels when describing the listing to a user, and the raw values when filtering. Only public listings can be fetched.

Input parameters:

- `listingId` (integer, required): Numeric listing id, as returned by search_listings

### `search_locations` (~143 tokens)

Find Serbian locations by name and return their numeric ids, which is how listings are filtered by place. Matching is fuzzy and tolerates missing diacritics. Results carry a level (COUNTRY, MUNICIPALITY, CITY, CITY_MUNICIPALITY, SETTLEMENT, NEIGHBOURHOOD) and a path showing where the place sits in the hierarchy; use both to pick between same-named places, and prefer asking the user rather than guessing when several look plausible.

Input parameters:

- `limit` (integer): Maximum results to return (1-25, default 10)
- `query` (string, required): Place name to search for, for example 'Novi Sad'

### `get_picklist_values` (~126 tokens)

List the accepted values for an attribute whose get_category entry carries a picklist_path. These value sets are hierarchical and too large to inline, so they are fetched one level at a time. A picklist_path may contain a placeholder in braces naming another attribute, as in 'vehicles.car.{make}'; replace the placeholder with that attribute's chosen value before calling, so picking make 'toyota' means requesting 'vehicles.car.toyota' to get the models for it.

Input parameters:

- `path` (string, required): Fully resolved dot-separated picklist path, with any placeholder already substituted

### `search_listings` (~348 tokens)

Search published listings by free text, category and location. Every argument is optional but at least one must be given; supplying several narrows the result the way a user ticking filters would.

category_id and location_id are hierarchical and match the whole subtree beneath them, so the category 'Mobilni telefoni i oprema' also returns listings filed under its child categories, and Beograd also returns listings in Novi Beograd, Zemun and every other place under it. Filter at the broadest level the user actually meant, and only narrow when they named a specific place or category. Get ids from get_categories and search_locations.

q is an ordinary keyword search, not semantic or vector search: it matches words the listing actually contains, so synonyms and paraphrases will not find anything. It matches broadly across titles, descriptions, attribute values and the listing's category and location names, but ranks titles and descriptions highest. Prefer q for what an item is, and the id filters for where it is and what it is filed under — 'stan Beograd' works, but a location_id for Beograd works better.

Only the first few best matches are returned and there is no way to page past them. If the result looks too broad, narrow the search and call again rather than asking for more.

Input parameters:

- `categoryId` (integer): Numeric category id from get_categories; matches this category and everything under it
- `limit` (integer): Maximum results to return (1-10, default 10)
- `locationId` (integer): Numeric location id from search_locations; matches this place and everything under it
- `q` (string): Keywords to match, for example 'iphone 15 pro'

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/rs-malinica-classifieds/api#diagnostics

## Score history

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

## Common questions

### What is the Malinica MCP server?

Malinica is an MCP server listed in the public MCP registry as rs.malinica/classifieds. Search classified listings on Malinica, a Serbian free serbian classifieds marketplace. This page covers its hosted endpoint (https://api.malinica.rs/mcp).

### Is the Malinica MCP server safe to use?

Malinica scores 87 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 Malinica MCP server expose?

Malinica exposes 6 tools: get_categories, get_category, get_listing, search_locations, get_picklist_values, search_listings. Their descriptions and schemas cost roughly 981 tokens of context every time the server is loaded.

### Does the Malinica MCP server require authentication?

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

### Is the Malinica MCP server still maintained?

Malinica 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://api.malinica.rs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/rs-malinica-classifieds/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/rs-malinica-classifieds/api.json
- HTML version of this page: https://verifymcp.io/servers/rs-malinica-classifieds/api