Headshot Photo Check
REMOTE · MCP.PROFILFOTO-KI.DE
Technical checks and crop recommendations for professional profile and application photos.
Available components
Last scanned (16 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Design and Media
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 537 tokens (~268/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 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.
- 16 Nov 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.
- 14 Nov 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.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 70
First indexed and scored.
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 21 Nov 2026 · Probed https://mcp.profilfoto-ki.de/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.profilfoto-ki.de | CN=YE2,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 50cc4cabdf7c49db2e667da3ffd3aae4620 |
| SANs: mcp.profilfoto-ki.de | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.profilfoto-ki.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| de. | DS published | 26755 | 8 | Verified |
| profilfoto-ki.de. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.profilfoto-ki.de/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.profilfoto-ki.de/mcp | HTTPS enforced | 301 | https://mcp.profilfoto-ki.de/mcp |
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 →
check_headshot_photo Check headshot photo ~365
Use this when the user wants technical checks of one professional profile or job-application photo from a public HTTPS URL or base64. Maximum 8 MB; image_url is recommended. Base64 above roughly 150 KB may exceed the Worker CPU budget. Auto mode resizes through an optional Images binding for pixel metrics, including WebP. Without it, only small JPEG/PNG inputs receive pixel checks; other inputs receive explicit header-only results. Sharpness detects coarse blur only. Face framing is not checked. URL fetching contacts user-selected external hosts and is limited to 8 seconds and 3 redirects. Cloudflare Images may internally resize the input for metrics; no edited image is returned. Operational call metadata is logged. Do not use for image creation, editing, personal-attribute judgments or identity verification. The image is analysed in memory and not stored. It does not generate images, video or audio or return edited images. It does not judge attractiveness, identity, age, gender, ethnicity or any other personal attribute; no face recognition or biometric identification.
| Name | Type | Req | Description |
|---|---|---|---|
| image_base64 | string | – | One JPEG, PNG or WebP encoded as base64, optionally prefixed by data:image/...;base64,. At most 8,000,000 decoded bytes. Prefer image_url; base64 payloads above roughly 150 KB may exceed the Worker C… |
| image_url | string | – | Public HTTPS image URL without credentials or custom port. IP literals and internal hostnames are blocked. Fetching contacts the user-selected external image host and validated redirect hosts; those… |
| target | string | – | Destination for crop recommendations: linkedin, xing, application or all (default). Example: linkedin. All includes every destination. |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_mode | string | yes | – |
| criteria | array | yes | – |
| improvement_tips | array | yes | – |
| notes | array | yes | – |
| overall_score | integer | yes | – |
| recommended_crops | object | yes | – |
| score_scope | string | yes | – |
| target | string | yes | Destination for crop recommendations: linkedin, xing, application or all (default). Example: linkedin. All includes every destination. |
| verdict | string | yes | – |
No examples provided.
get_headshot_photo_requirements Get headshot requirements ~158
Use this when the user wants a technical headshot checklist and crop recommendations for LinkedIn, XING or job applications. Returns static recommendations, not official platform upload limits; no image input or external network access. No persistent changes; operational call metadata is logged. Do not use for assessing an actual image or confirming platform acceptance. The image is analysed in memory and not stored. It does not generate images, video or audio or return edited images. It does not judge attractiveness, identity, age, gender, ethnicity or any other personal attribute; no face recognition or biometric identification.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | – | Destination for crop recommendations: linkedin, xing, application or all (default). Example: linkedin. All includes every destination. |
| Name | Type | Req | Description |
|---|---|---|---|
| checklist | array | yes | – |
| note | string | yes | – |
| recommendations | object | yes | – |
| target | string | yes | Destination for crop recommendations: linkedin, xing, application or all (default). Example: linkedin. All includes every destination. |
No examples provided.
How do I install the Headshot Photo Check MCP server?
Headshot Photo Check is a hosted endpoint at https://mcp.profilfoto-ki.de/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 · mcp.profilfoto-ki.de
claude mcp add --transport http de-profilfoto-ki-headshot-check 'https://mcp.profilfoto-ki.de/mcp'
What is the Headshot Photo Check MCP server?
Headshot Photo Check is an MCP server listed in the public MCP registry as de.profilfoto-ki/headshot-check. Technical checks and crop recommendations for professional profile and application photos. This page covers its hosted endpoint (https://mcp.profilfoto-ki.de/mcp).
Is the Headshot Photo Check MCP server safe to use?
Headshot Photo Check scores 76 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 Headshot Photo Check MCP server expose?
Headshot Photo Check exposes 2 tools: check_headshot_photo, get_headshot_photo_requirements. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.
Does the Headshot Photo Check MCP server require authentication?
No. We connected to Headshot Photo Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Headshot Photo Check MCP server still maintained?
Headshot Photo Check is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Headshot Photo Check MCP server?
VerifyMCP ran 13 checks on Headshot Photo Check, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.