de.profilfoto-ki/headshot-check
Headshot Photo Check
Is the Headshot Photo Check MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-09.
Technical checks and crop recommendations for professional profile and application photos.
alive probed 2026-11-15 · unchanged since 2026-11-09 · HTTP 200
- Endpoint
- https://mcp.profilfoto-ki.de/mcp (streamable-http)
- Host
- mcp.profilfoto-ki.de
- Protocol
- 2025-11-25
- Reports itself as
- bewerbungsfoto-check 0.1.2
- Capabilities
- tools
- Instructions
- 73 characters
- Of a 1M window
- ≈ <0.1 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: tools.1.custom.input_schema: input_schema does not support oneOf, allOf, or anyOf at the top level. The estimate stands in.
- Website
- https://profilfoto-ki.de
- Registry
- active, updated 2026-11-09 · registry entry
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| check_headshot_photo | 502 | 72 % |
| get_headshot_photo_requirements | 198 | 28 % |
Compare this server with others.
More servers
Servers that mention headshot or check or photo.
- MyBestAngle com.mybestangle/mybestangle · needs auth
- ProfessionalHeadshot.io io.professionalheadshot/professionalheadshot · alive
- Business Contact Finder agency.ottobot/business-contact-finder · alive
- groTAX by Grovisor ae.grovisor/grotax · alive
- Agentic Fabrication Network (AFN) ai.agenticfabricationnetwork/ufp · alive
- Plumbline - Contractor License Checks ai.agentlookups/plumbline · alive
- ai.agentlookups/overassessed · alive
- Alpic ai.alpic.mcp/alpic-mcp · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The Anthropic count_tokens endpoint refused the tool schemas (tools.1.custom.input_schema: input_schema does not support oneOf, allOf, or anyOf at the top level). A client that validates schemas can refuse them too.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.