mcpbeat Sign in

Charmshots MCP Server

by charmshots Your server? Claim it
answering

Charmshots is answering right now. Last checked 8 min ago. 39 installs a week from npm. Last commit 9 Oct 2026.

Read-only MCP connector for Charmshots photoshoots, photo metadata and owner-authenticated links.

Installs per day peak 282 · avg 27 · -56% w/w
a month agotoday
Uptime history 25 days of history · worst day 93%
25 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
200 ms
Response time
average over 24h
39
Installs / week
npm and PyPI

What the code does

We read the source, 7 d ago · rules ccca72095570

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims read-only, but the code runs commands server/index.js:13, [пакет] server/index.js:13
const child=spawn(process.execPath,args,{stdio:'inherit',shell:false});
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

const child=spawn(process.execPath,args,{stdio:'inherit',shell:false});

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Charmshots and you get told the day something new turns up.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add mcp-server --transport http https://mcp.charmshots.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.charmshots.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-server]
url = "https://mcp.charmshots.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.charmshots.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.charmshots.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.charmshots.com/mcp streamable-http sign-in 201 ms 8 min ago

Alternatives to Charmshots

same job, measured the same way
Facehunch
by facehunch

Read-only MCP connector for Facehunch saved reports, access status and available source links.

41 installs/wk answering
OSF CLI Go
by edithatogo

Read-only MCP tools for authenticated Open Science Framework projects and files.

local only
Adlane App
by adlane-app

Read-only MCP connector for Adlane workspaces, Google and Meta ad accounts and campaign reports.

38 installs/wk answering
1
1845 Smoked Meat AI Gateway
by getbotlens

MCP gateway for 1845meat.com: products, prices, stock and cart links. Read-only, no auth.

11 tools answering
Straws Soda
by griffmurder

Public read-only MCP for strawssoda.com: menu, hours, and order or contact links.

5 tools answering
BITHOT
by ifcode

Read-only MCP for curated crypto, Web3, and memecoin picks and reports.

7 tools answering
CorpusIQ
by corpusiq

Authenticated, user-scoped MCP connectors for 30+ business systems.

121 tools answering
RZD Tickets MCP
by ex3lite

Read-only MCP server for RZD trains, cars, seats, adjacent pairs and car photos.

29 installs/wk local only

Charmshots — questions

Answers built from our own checks of this server.

Why is there no tool list for Charmshots?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Charmshots working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 200 ms. The bar chart above shows every period we have measured.
How do I connect Charmshots?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Charmshots?
No API key is involved. Charmshots answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Charmshots?
It answers our handshake in 200 ms on average, which is faster than 62% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Charmshots?
The npm package charmshots-mcp was installed 39 times in the last week. Week over week that is -56%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Charmshots open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.