F
licenseNot graded
qualityB
maintenanceEnables users to compare images for visual similarity, detect exact and near-duplicates, and obtain similarity scores and perceptual hash distances via a plain HTTP API.
-
joj-image-search
by com.jojapi
Server Details
Image Search: Fast and Simple Image Search API. You can get 100+ search results in one query!.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over 42 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
TDQS
C2.6/5.0
Scored across 1 tool
Disambiguation5/5
With only a single tool, there is no possibility of confusion or overlap, so the tool is trivially distinguishable.
Naming Consistency4/5
The tool name 'get_v2' uses a consistent lowercase with underscore style, but it lacks a descriptive term like 'search_images' and the 'v2' suffix is unclear. However, since it's the only tool, there's no inconsistency to penalize heavily.
Tool Count3/5
A single tool for an image search service is minimal and feels thin. While it may be appropriate for a narrow API, it falls below the typical 3-15 range for a well-scoped server.
Completeness2/5
The tool only provides search functionality. A complete image search API would likely include operations like retrieving image details, uploading, or managing collections, so significant gaps exist in the surface.
Available Tools
1 toolget_v2Search V2CInspect
Search V2 Group: Image Search. Billing per call: 1 Credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search query. You can use search parameters. e.g. `adele site:youtube.com` e.g. `query -exclude` | |
| hl | No | Language code for search. Default: en | |
| tbs | No | Search filters. | |
| nfpr | No | ||
| safe | No | If you want safe search, set it to `active` | |
| cursor | No | Cursor for next results. | |
| filter | No | ||
| suggestion_query | No | Suggestion query (must be taken from response suggestions). |
TDQS
C2.2/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description bears full responsibility for disclosing behavior. It only mentions search and billing, but does not describe return formats, pagination, authentication, side effects, or any operational constraints. This is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, compact sentence that efficiently conveys the primary function and a cost detail. It is not overly verbose, though it sacrifices substance for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 8 parameters, no output schema, and no sibling context, yet the description provides no information about return values, pagination, error handling, or how results are presented. It is far from sufficient for an agent to use without external knowledge.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds zero information about parameters. Although the input schema has descriptions for 6 of 8 parameters (75% coverage), this is not high enough to fully rely on schema alone. The description does not compensate for the two undocumented parameters (nfpr, filter) or clarify usage intent.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states 'Image Search', providing a clear verb and resource. It indicates it is a search tool for images, which is distinct from generic web search, even though no sibling tools are listed for comparison. However, it does not elaborate beyond that.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The description only includes a billing note, which does not help an agent decide when to invoke it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
get_v2
Related MCP Connectors
Google Image Search: Fast and Simple Google Images Search API. You can get 100+ search results in.
Search over 1.85 million captioned images using text, a reference image, or both. Upload a JPEG, PNG, or WebP image as base64, or provide a public HTTPS image URL. Find similar images from a Lightdrift asset ID and retrieve hosted file URLs, source licenses, and attribution. Connect with OAuth or an API key. Searches cost $0.005 ($5 per 1,000); image details are free. Setup: https://docs.lightdrift.ai/guides/images-mcp
Google Web Search: Google Web Search API. Search the world’s information, including webpages.
Google, Bing, DuckDuckGo and Google Maps search results, free without an API key.
Related MCP Servers
OpenSERP Cloudofficial
AlicenseBqualityCmaintenanceSearch API for AI, SEO & automation. Browser-rendered Google, Bing, Yandex, Baidu, DuckDuckGo and Ecosia results with URL extraction (+image search and engine metadata tools)953 npm2MIT- AlicenseAqualityAmaintenanceEnables image search on Google Images with size, color, and type filters, returning up to 100 results per call including source pages and full-resolution URLs.132 npm153 PyPI8MIT
- AlicenseNot gradedqualityDmaintenanceA search service based on multiple image APIs and icon generation capabilities, specifically designed for integration with Cursor MCP service. Supports image search, download, and AI-generated icons.16MIT
Try in Browser
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
Glama MCP Gateway
Add one secure layer between your agents and this server.