Pexafy Stock Photos MCP server
com.pexafy/pexafy-mcppexafy.comstreamable-httpv1.0.2Scanned
Find free-to-use stock photos by words, by image or by similarity; every result names its licence.
5 tools: 1 change things and 4 only read.
- Reads private data · 3
- Reads text others write · 2
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Pexafy Stock Photos MCP server can do
The Pexafy Stock Photos MCP server is published by pexafy.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: connect_account), but cannot delete data. 4 tools only read.
3 tools read private data (search_photos, search_photos_by_image and get_photo_file_by_photo_id); 2 tools bring in text other people can write (search_photos and search_photos_by_image).
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 1Claude Code: ask
connect_accountAsks the host to offer its own flow for connecting a Pexafy account, when none is attached.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Asks the host to offer its own flow for connecting a Pexafy account, when none is attached. Use it when the person asks to connect, link or sign in to a Pexafy account — including from the account button in the Pexafy grid — or wants more searches than the daily allowance available without an account. When no account is attached, it returns an error result that carries an account-connection request for the host: the error is how that request is delivered, not a failure. A host that supports it shows its own account-connection prompt, which the person completes or dismisses; other hosts show only the result's text. Calling it again returns the same request. When an account is already attached, it says so and starts nothing. It does not search, and searching does not require calling it. `check_only` is set by the Pexafy grid to read the state without opening a prompt; leave it unset when the person wants to connect or sign in.
Annotations the server declares
- title: Connect a Pexafy account
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_grid_selected_photosReturns the photographs the person liked (hearted) in the Pexafy results grid.No findings
Why it is in this group
- The name "get_grid_selected_photos" says "get": a word for reading.
Description, as the server wrote it Returns the photographs the person liked (hearted) in the Pexafy results grid. Use it when the person refers to that selection rather than asking for new photos — for example “the images I selected”, “the ones I chose”, “my selection”, “the photos I hearted”, “the photos I liked”, “use the ones I picked”, “put my selection in the document”, “download the ones I chose”, or “write the article around my photos”. The selection is held by the grid and the server, not by the conversation: this tool is how it is read, and search results are not the selection. It takes no arguments and returns every liked photograph with its rank, photo_id, photographer, source library, licence, pixel size, orientation, description, page URL and credit line, and `selection_count`, the number of them. To get one of them as an image file, pass its photo_id to get_photo_file_by_photo_id. `rank` is the person's order, #1 first: the order the photos were liked in, unless the person rearranged them by dragging in the grid. Where the grid is rendered, that number is drawn on each liked photograph, so it is the number the person sees and names them by (“#2”). The `rank` of a search result is only its position in that answer and is not drawn on the grid. An empty selection means nothing is liked in the grid currently on screen; a photograph is liked with the heart on it. A selection expires an hour after its last change, and a new search replaces the grid it belongs to.
Annotations the server declares
- title: Get the photos the person liked in the grid
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_photo_file_by_photo_idReturns one photograph from an earlier Pexafy result as an image file, identified by its `photo_id`.Reads private dataNo findings
Why it is in this group
- The name "get_photo_file_by_photo_id" says "get": a word for reading.
What it can reach
- private-dataThe name "get_photo_file_by_photo_id" says "get" and "file": it reads files.
- private-dataThe description's first sentence says "return" and "file": it reads files.
Description, as the server wrote it Returns one photograph from an earlier Pexafy result as an image file, identified by its `photo_id`. A result's link points to the image; this tool returns the image itself, so the person does not need to send the photograph again. Use it when the user wants a photograph found here as a file: to place it in a document, a slide or a post, to attach, send or download it, or to have it cropped, captioned or otherwise edited with the host's own tools. It is for a photograph the person picked: where the Pexafy grid is shown, the photographs of a search are already on screen and need no file to be seen. The answer contains the photograph, at most 1280 pixels wide, and a line giving its file name, size, licence, source, `photo_id`, page at the source and the credit line to display. One photo per call; the file stays in the conversation afterwards. This server does not edit images: what can be done to the file next depends on the host's own tools. Its licence and credit line apply to this photograph only.
Annotations the server declares
- title: Get the photo as a file
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_photosUse this when the user asks for a real photograph, or states a need that a photograph fills, and the picture is not already in the conversation.Reads private dataReads text others write1 finding
Why it is in this group
- The name "search_photos" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "conversation": it reads messages.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "conversation": it reads messages, which other people can write.
Findings
- Info
The description is 2,030 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...id. In a host that renders it, the grid shows them; the answer omits image links."
Description, as the server wrote it Use this when the user asks for a real photograph, or states a need that a photograph fills, and the picture is not already in the conversation. Call it when they ask outright: “find me photos of…”, “show me images of…”, “I need a picture of…”, “do you have a photo of…”, “where can I find free photos of…”, in any language. Call it when they describe the need without asking to search: “I'm writing an article and need a header image”, “my landing page needs a hero image”, “I need something to illustrate this”. Call it when they ask for something meant to carry photographs: “write an article with pictures”, “a deck with images”. Call it when they name only the picture, with no reason given: “a photo of a white mug”, “a train in Japan”. If the user is working on something that usually carries photographs — an article, a page, a deck, a post — without asking for any, you may offer to look for some; call it only once they accept. This covers requests for photographs for articles, blog posts, websites, landing pages, products, slides, documents, reports, social posts, ads, newsletters, banners, thumbnails, covers, posters, backgrounds, wallpapers and mood boards; photographs that illustrate a concept, explain a subject or accompany a piece of writing; and any request for free, stock, royalty-free, commercially usable, real or documentary photographs. A request for a visual is not always a request for a photograph: this tool finds photographs that already exist — not illustrations, drawings, logos, icons, diagrams or screenshots — and it does not generate, edit or upscale an image, nor look for a named person. It searches Pexafy's own index of millions of free-to-use photographs from stock libraries such as Unsplash, Pexels and Pixabay, matched to the scene described. Each result carries a `rank`, a `photo_id`, its licence, the credit line to display and an image link; the file itself comes from get_photo_file_by_photo_id. In a host that renders it, the grid shows them; the answer omits image links.
Annotations the server declares
- title: Search free stock photos
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
search_photos_by_imageUse this when the user wants photographs that look like a picture, rather than ones described in words: a picture they link to, one the host passes to the tool as a file, or a Pexa…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "search_photos_by_image" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
- private-dataThe input names a file (input.image_file), and the tool reads: it reads files.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use this when the user wants photographs that look like a picture, rather than ones described in words: a picture they link to, one the host passes to the tool as a file, or a Pexafy photo already found or liked in the grid. Call it for “find images like this”, “something similar to this photo”, “find a free alternative to this image”, “I need this but royalty-free”, “photos in this style”, “more like the second one”, whether or not they say “search by image”. Give exactly one reference: `photo_id` for a Pexafy photo from an earlier result or liked in the grid; `image_url` for a picture at a public URL, such as a link the user pasted; `image_file` when the host passes the user's uploaded image to the tool; `image_base64` for image bytes a client already holds. Sending two is refused. A picture that is only visible in the conversation — not linked, not passed to the tool — is not a reference this tool can receive; its scene can be searched in words with `search_photos`. Words are optional, in `english_search_sentence`: with a `photo_id`, the words that photograph was found under; with an image, only what the user wants changed or kept (“like this but at night”). It finds free stock photographs in Pexafy's index that visually match the reference. The reference image is sent to Pexafy only to run the search; it is not stored. Each result carries a `rank`, a `photo_id`, its licence, the credit line to display and an image link. In a host that renders it, the grid shows them; the answer omits image links.
Annotations the server declares
- title: Find photos that look like an image or a Pexafy photo
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:44 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.pexafy.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://pexafy.com/
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.pexafy.com/mcp: tools/list returned 5 tools to an anonymous client, including connect_account (write)
Findings
Matches of fixed checks, with the text they matched.
- Infosearch_photos
The description is 2,030 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...id. In a host that renders it, the grid shows them; the answer omits image links."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http pexafy https://mcp.pexafy.com/mcpclaude mcp add --transport http pexafy https://mcp.pexafy.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pexafy__search_photos",
"mcp__pexafy__search_photos_by_image",
"mcp__pexafy__get_photo_file_by_photo_id",
"mcp__pexafy__get_grid_selected_photos"
],
"ask": [
"mcp__pexafy__connect_account"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pexafy. Review it before you use it.
Capability tags behind 3 rules
- mcp__pexafy__search_photos private-data, untrusted-input
- mcp__pexafy__search_photos_by_image private-data, untrusted-input
- mcp__pexafy__get_photo_file_by_photo_id private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.pexafy/pexafy-mcp/verify?hash=0e70a6eb15f9f0de398315f14322c7e4d3067a9700fc0e6f1d0103196c7ff86f" | jq -e '.changed == false'Pinned hash 0e70a6eb15f9, from Nov 10, 2026, 23:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.pexafy/pexafy-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.pexafy/pexafy-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:00 UTC.
Pexafy Stock Photos MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Pexafy Stock Photos MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Pexafy Stock Photos MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Pexafy Stock Photos MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Pexafy Stock Photos MCP server have?
- 5 tools: 1 write, 4 read. connect_account, search_photos, search_photos_by_image, get_photo_file_by_photo_id and get_grid_selected_photos.
Does the Pexafy Stock Photos MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Pexafy Stock Photos MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Pexafy Stock Photos MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.