ProfessionalHeadshot.io
REMOTE · PROFESSIONALHEADSHOT.IO
LinkedIn, Slack and GitHub profile photo specs, headshot style guides and a free headshot audit.
Available components
Last scanned (20 hours ago)
Scores higher than 70% of remote servers
Reachable. Last reached 16 Oct 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 282 tokens (~94/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 75
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 16 Oct 2026 · Probed https://professionalheadshot.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=professionalheadshot.io | CN=YR1,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | RSA 2048 | SHA256-RSA | 5fd4974f664662a40d2c26aefaa7c523b78 |
| SANs: professionalheadshot.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of professionalheadshot.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| professionalheadshot.io. | absent | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://professionalheadshot.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://professionalheadshot.io/api/mcp | HTTPS enforced | 308 | https://professionalheadshot.io/api/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 →
audit_headshot Headshot audit ~97
Score one photo 0-100 as a professional headshot and list concrete issues and fixes (lighting, framing, face visibility, background, attire). Takes a public https URL to a JPEG/PNG/WebP image. Free: 5 audits per day per user. The photo is analysed and not stored.
| Name | Type | Req | Description |
|---|---|---|---|
| image_url | string | yes | Public https URL of the photo (JPEG, PNG or WebP, max 10 MB) |
No output schema declared.
No examples provided.
get_headshot_guide Headshot style guide ~98
How to shoot or choose a professional headshot for a given use (LinkedIn, resume/CV, company website team page, executive bio, speaker/press kit) and industry: framing, background, attire, expression and what to avoid. Style guidance, not an official platform rule.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | Optional: the person's industry (default general) |
| use | string | yes | Where the headshot will be used |
No output schema declared.
No examples provided.
get_profile_photo_specs Profile photo specs ~87
Official profile and cover photo requirements (pixel limits, file size, formats, content rules) for LinkedIn personal profiles, LinkedIn company Pages, Slack and GitHub, quoted from each platform's help pages with source links. Values the platform does not publish are null. Omit platform to get all.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Optional: one platform; omit to list all |
No output schema declared.
No examples provided.
How do I install the ProfessionalHeadshot.io MCP server?
ProfessionalHeadshot.io is a hosted endpoint at https://professionalheadshot.io/api/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 · professionalheadshot.io
claude mcp add --transport http io-professionalheadshot-professionalheadshot 'https://professionalheadshot.io/api/mcp'
What is the ProfessionalHeadshot.io MCP server?
ProfessionalHeadshot.io is an MCP server listed in the public MCP registry as io.professionalheadshot/professionalheadshot. LinkedIn, Slack and GitHub profile photo specs, headshot style guides and a free headshot audit. This page covers its hosted endpoint (https://professionalheadshot.io/api/mcp).
Is the ProfessionalHeadshot.io MCP server safe to use?
ProfessionalHeadshot.io 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 ProfessionalHeadshot.io MCP server expose?
ProfessionalHeadshot.io exposes 3 tools: get_profile_photo_specs, get_headshot_guide, audit_headshot. Their descriptions and schemas cost roughly 282 tokens of context every time the server is loaded.
Does the ProfessionalHeadshot.io MCP server require authentication?
No. We connected to ProfessionalHeadshot.io without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ProfessionalHeadshot.io MCP server still maintained?
ProfessionalHeadshot.io is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.