mcp-registry/hr.trazimstan/nekretnine · v0.2.0
As of 2026-10-26 16:37 UTC, the Trazimstan Nekretnine MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 4 minutes.
Pretraga provjerenih oglasa za prodaju i najam nekretnina u Hrvatskoj na trazimstan.hr.
Point your MCP client at this streamable-http endpoint: https://mcp.trazimstan.hr/mcp
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fhr.trazimstan%2Fnekretnine/fixes
{
"name": "fetch",
"description": "Retrieves the full text of a single trazimstan.hr listing by its ID, as returned by the `search` tool. Use it to read details before citing a listing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Listing ID returned by `search` (UUID)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Fetch a trazimstan.hr listing"
}{
"name": "get_listing",
"description": "Dohvaća detalje pojedinog oglasa po ID-u (UUID) s trazimstan.hr.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "UUID oglasa, npr. a78c749c-a361-449c-b913-d11e21b1f2cc"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Detalji oglasa"
}{
"name": "get_price_stats",
"description": "Vraća medijan cijene i cijenu po m² za vrstu nekretnine (opcionalno po gradu), izračunato iz AKTUALNIH oglasa na trazimstan.hr. Korisno npr. za \"koliko košta zemljište u Istri\" ili \"cijene stanova u Zagrebu\". VAŽNO: ovo je presjek ponude na trazimstan.hr, a ne službena tržišna statistika — uvijek navedi veličinu uzorka.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"city": {
"type": "string",
"description": "Grad (opcionalno), npr. Zagreb"
},
"transactionType": {
"enum": [
"RENT",
"SALE"
],
"type": "string",
"default": "SALE"
},
"propertyCategory": {
"enum": [
"APARTMENT",
"HOUSE",
"WG_ROOM",
"COMMERCIAL",
"OFFICE",
"RETAIL",
"LAND",
"STUDENT",
"TOURISM"
],
"type": "string",
"default": "APARTMENT",
"description": "Vrsta nekretnine"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Cijene nekretnina na trazimstan.hr"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/hr.trazimstan/nekretnine"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/hr.trazimstan/nekretnine"}) over MCP.
search_listings ~442 tokensget_price_stats ~232 tokenssearch ~146 tokensfetch ~114 tokensget_listing ~96 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fhr.trazimstan%2Fnekretnine?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fhr.trazimstan%2Fnekretnine?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fhr.trazimstan%2Fnekretnine.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fhr.trazimstan%2Fnekretnine.svg :target: https://glimind.com/server/mcp-registry%2Fhr.trazimstan%2Fnekretnine?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:dcec2de9ebf3a3c9…, first seen 2026-10-17, included at leaf 910 of 74,160. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable web servers · most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 16:37 UTC, the Trazimstan Nekretnine MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 4 minutes.
Trazimstan Nekretnine MCP server advertises 5 tools, including fetch, get_listing, get_price_stats, search, search_listings.
Point your MCP client at this streamable-http endpoint: https://mcp.trazimstan.hr/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.