Skip to content

ProfessionalHeadshot.io

by professionalheadshot.io · remote · no sign-in to list tools · v0.1.0 · published by io.professionalheadshot

LinkedIn, Slack and GitHub profile photo specs, headshot style guides and a free headshot audit.

Changes · 1
CompareRegistry entry

3 tools: 1 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http professionalheadshot https://professionalheadshot.io/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 1Claude Code: ask
  • audit_headshotScore one photo 0-100 as a professional headshot and list concrete issues and fixes (lighting, framing, face visibility, background, attire).Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Claude Code: allow
  • get_headshot_guideHow 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,…Reads text others writeNo findings

    Why it is in this group

    • The name "get_headshot_guide" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_profile_photo_specsOfficial profile and cover photo requirements (pixel limits, file size, formats, content rules) for LinkedIn personal profiles, LinkedIn company Pages, Slack and GitHub, quoted fro…Reads private dataNo findings

    Why it is in this group

    • The name "get_profile_photo_specs" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 data1
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.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http professionalheadshot https://professionalheadshot.io/api/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__professionalheadshot__get_profile_photo_specs",
      "mcp__professionalheadshot__get_headshot_guide"
    ],
    "ask": [
      "mcp__professionalheadshot__audit_headshot"
    ],
    "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 professionalheadshot. Review it before you use it.

Capability tags behind 3 rules
  • mcp__professionalheadshot__get_profile_photo_specs private-data
  • mcp__professionalheadshot__get_headshot_guide untrusted-input
  • mcp__professionalheadshot__audit_headshot untrusted-input