Is the Vistoya Market MCP server down?

mcp-registry/io.github.vistoya/market · v1.0.0

grade B

unknown

Last checked 2026-10-22 13:50 UTC · handshake 505ms

As of 2026-10-22 13:50 UTC, the Vistoya Market MCP server is unknown with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)

99.8%

checks observed

4,256

outages (90d)

tools

Search and get fashion products recommendations across multiple e-ecom stores

Point your MCP client at this streamable-http endpoint: https://api.vistoya.com/mcp

Agent-readiness: B (83/100)

grade B

B (83/100): 1 error(s), 3 warning(s) across 6 tool(s); ~4,269 tokens of tool definitions.

Scores higher than 41% of 15,543 MCP servers Glimind has audited.

Its tool list costs an agent ~4,269 tokens per session — more than 60% of servers.

91 → 91 since 2026-10-17

no tool-poisoning patterns

Schemas100

Descriptions78

Safety hints100

Token cost82

Client compatibility100

Protocol100

Reliability0

Stability96

What to fix (5)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

1 tool definition(s) exceed ~1,200 tokens each (largest: discover_products, ~2,008).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,408 tokens every session. How to fix →

Tools: discover_products · saves ~1,408 tokens/session

1 parameter(s) across 1 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 →

Tools: find_similar_brands

Handshake + tools/list takes ~2,343 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

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/io.github.vistoya/market"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.vistoya/market"}) over MCP.

Passed

Every tool has a well-formed, typed input schema.
Every tool declares whether it is read-only or destructive.
No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
Tool names are unique and portable across clients.
Speaks MCP 2025-06-18.
99.79% uptime over 30 days.

Largest tool definitions

discover_products ~2,008 tokens
discover_brands ~831 tokens
get_filters ~492 tokens
find_similar_products ~400 tokens
get_product ~294 tokens

Static 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:

Markdown

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.vistoya%2Fmarket.svg)](https://glimind.com/server/mcp-registry%2Fio.github.vistoya%2Fmarket?ref=badge)

HTML

<a href="https://glimind.com/server/mcp-registry%2Fio.github.vistoya%2Fmarket?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.vistoya%2Fmarket.svg" alt="MCP agent-readiness"></a>

reStructuredText

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.vistoya%2Fmarket.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.vistoya%2Fmarket?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1133f4be29462419…, first seen 2026-10-17, included at leaf 4530 of 46,591. Version history · verify what your client received.

Tools (6)

Compare: most reliable search servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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

FAQ

Is the Vistoya Market MCP server down right now?

How many tools does Vistoya Market MCP server provide?

Vistoya Market MCP server advertises 6 tools, including discover_brands, discover_products, find_similar_brands, find_similar_products, get_filters.

How do I install Vistoya Market MCP server?

Point your MCP client at this streamable-http endpoint: https://api.vistoya.com/mcp

Is the Vistoya Market MCP server safe to connect to an AI agent?

Glimind scanned all 6 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.

Operator of Vistoya Market MCP server?

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.