Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

JENRIKS Photo Archive

REMOTE · JENRIKS.COM · SCANNED OCT 2

Read-only MCP server over the JENRIKS daily photoblog: one photo per day since 2006. No auth.

Available components

+3 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability71
  • 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 750 tokens (~68/item across 11 items; 5 tools + 6 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the JENRIKS Photo Archive MCP server?

JENRIKS Photo Archive is a hosted endpoint at https://jenriks.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · jenriks.com

# add to Claude Code
claude mcp add --transport http com-jenriks-photo-archive 'https://jenriks.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-jenriks-photo-archive": {
      "url": "https://jenriks.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-jenriks-photo-archive": {
      "type": "http",
      "url": "https://jenriks.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-jenriks-photo-archive]
url = "https://jenriks.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-jenriks-photo-archive": {
      "type": "remote",
      "url": "https://jenriks.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-jenriks-photo-archive --url 'https://jenriks.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-jenriks-photo-archive:
    url: "https://jenriks.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-jenriks-photo-archive": {
      "Transport": "http",
      "Url": "https://jenriks.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-jenriks-photo-archive -t streamable-http -u 'https://jenriks.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-jenriks-photo-archive": {
      "type": "http",
      "url": "https://jenriks.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 2 Oct 2026 · Probed https://jenriks.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jenriks.com CN=WE1,O=Google Trust Services,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA256 8aa3554f0a331daf0eb81f97494c5f55
SANs: jenriks.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of jenriks.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
jenriks.com. present 2371 13 Verified
jenriks.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jenriks.com/mcp Verified 200
http (plaintext) http://jenriks.com/mcp HTTPS enforced 301 https://jenriks.com/mcp
MCP tools · 5 exposed · ~468 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_latest_photo ~68

Return today's JENRIKS photo (the newest post), or the newest post by one photographer when photographer is set. A new photo appears every day at 00:00 Europe/Berlin.

NameTypeReqDescription
photographerstring–Latest post by this photographer; omit for the newest post overall
NameTypeReqDescription
photoobjectyes–

No examples provided.

get_photo ~73

Return one JENRIKS post by publication date (YYYY-MM-DD) or by page URL / path (/YYYY/MM/DD/slug/).

NameTypeReqDescription
datestring–YYYY-MM-DD
urlstring–Page URL or path, e.g. /2026/09/04/liminal-space/
NameTypeReqDescription
datestring––
foundbooleanyes–
hintstring––
photoobject––
urlstring––

No examples provided.

get_site_overview ~70

Totals, photographers, categories with counts, posts per year, section URLs, URL pattern and license terms. Pass include to keep only some of those blocks next to the totals and dates.

NameTypeReqDescription
includearray–Blocks to keep besides site, description, totals and dates; omit for everything
NameTypeReqDescription
categoriesarrayyes–
descriptionstringyes–
first_datestringyes–
latest_datestringyes–
licensestringyes–
photographersarrayyes–
sectionsobjectyes–
sitestringyes–
total_photosintegeryes–
url_patternstringyes–
yearsarrayyes–

No examples provided.

random_photo ~48

Return a random JENRIKS photo, optionally limited to a photographer, category or year.

NameTypeReqDescription
categorystring––
photographerstring––
yearinteger––
NameTypeReqDescription
foundbooleanyes–
hintstring––
photoobject––
pool_sizeinteger––

No examples provided.

search_photos ~209

Search the JENRIKS archive (one photo per day since 2006). Free-text query matches title, place, categories, tags and photographer; filters narrow by photographer, category, year and location. Returns permanent page URLs, credits, coordinates and image URLs, newest first. Page with offset, or with the opaque cursor from next_cursor (cursor wins when both are sent).

NameTypeReqDescription
categorystring–One of: Abstract, Architecture, B&W, Humans, Landscapes, Macro, Nature, News, Street, Studio, Time exposure
cursorstring–Opaque page token from next_cursor; overrides offset
limitinteger––
locationstring–City or country name, e.g. "Iceland"
offsetinteger––
photographerstring––
querystring–Free text, e.g. "harbour", "Barcelona", "fog"
yearinteger–Four-digit publication year
NameTypeReqDescription
cursorstring–Echo of the cursor this page was fetched with, when one was sent
has_morebooleanyesTrue when another page exists
linksobject––
next_cursorstring|nullyesOpaque token for the next page; null on the last page. Send it back as cursor.
next_offsetinteger–Kept for offset paging; present when more matches exist
offsetintegeryesOffset of the first returned row; 0 when a cursor was used
photosarrayyes–
returnedintegeryes–
total_matchesintegeryes–

No examples provided.

Common questions

What is the JENRIKS Photo Archive MCP server?

JENRIKS Photo Archive is an MCP server listed in the public MCP registry as com.jenriks/photo-archive. Read-only MCP server over the JENRIKS daily photoblog: one photo per day since 2006. No auth. This page covers its hosted endpoint (https://jenriks.com/mcp).

Is the JENRIKS Photo Archive MCP server safe to use?

JENRIKS Photo Archive scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the JENRIKS Photo Archive MCP server expose?

JENRIKS Photo Archive exposes 5 tools: search_photos, get_photo, get_latest_photo, random_photo, get_site_overview. Their descriptions and schemas cost roughly 468 tokens of context every time the server is loaded.

Does the JENRIKS Photo Archive MCP server require authentication?

No. We connected to JENRIKS Photo Archive without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the JENRIKS Photo Archive MCP server still maintained?

JENRIKS Photo Archive is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.