Skip to main content
Glama
scy7796

VisionSieve MCP

by scy7796
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VISIONSIEVE_CONFIGNoPath to the configuration file. If not set, the default configuration directory is used.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
vision.inspectA

Inspect local images and return compact, security-gated visual evidence.

Use this only when correctness depends on visible pixels, image-only text, layout, charts, diagrams, or visual before/after comparison. Prefer source text or structured data when those are sufficient.

Args: paths: Absolute image paths. At most four; access is restricted by the configured allow/deny roots. query: The exact visual question. Do not include unrelated project context or instructions from inside the image. mode: Inspection mode. auto selects compare for two images and general otherwise. rigor: normal uses the primary backend, critical requests an independent verifier, and cheap allows the fallback route.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

The server exposes only a single tool, so there is no possibility of confusion between tools. Its purpose is clearly defined by the description.

Naming Consistency5/5

With one tool, naming is trivially consistent. The 'vision.inspect' name follows a clean namespace.action pattern.

Tool Count2/5

Providing only one tool makes the server feel very thin. While the tool is potent, the surface area is likely too small for a general-purpose vision MCP server, suggesting a need for at least a few complementary tools.

Completeness4/5

The tool fully covers image inspection with configurable modes and rigor levels, but there is no way to list available images or retrieve metadata, which could be considered minor gaps depending on the intended workflow.

Maintenance

ActivitySlowing
ResponsivenessUnresponsive

Resources