details.page MCP Server

by details Your server? Claim it

answering

details.page is answering right now. Last checked 13 min ago.

Manage your details.page link-in-bio from Claude: edit details, post updates, read analytics.

Uptime history 47 days of history · worst day 99%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

163 ms

Response time

average over 24h

API key

Access

streamable-http

details.page missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add details-page --transport http https://details.page/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "details-page": {
      "url": "https://details.page/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.details-page]
url = "https://details.page/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "details-page": {
      "url": "https://details.page/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "details-page": {
      "url": "https://details.page/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://details.page/mcp	streamable-http	needs key	296 ms	13 min ago

Alternatives to details.page

same job, measured the same way

BioFlow

by getbioflow

Manage BioFlow link-in-bio pages, blocks, leads, and analytics from AI agents.

answering

Snapto

by snapto

Manage your Snapto link-in-bio page: links, social icons, and visit and click analytics.

answering

Helloaigent Publisher

by helloaigent-dev

Run a Hello Aigent feed from your agent: create feeds, publish signed updates, read analytics.

30 installs/wk local only

Helloaigent Publisher

by akillam

Run a Hello Aigent feed from your agent: create feeds, publish signed updates, read analytics.

local only

Swonkie

by swonkie

Manage social media from your AI client: analytics, posts, scheduling, media, and AI images.

answering

CodeQR

by codeqr

Create and manage CodeQR short links, QR codes, and analytics from any MCP client.

answering

Marketscore Direct MCP

by marketscore

MCP for Yandex Direct: manage ad campaigns & analytics from Claude or ChatGPT

answering

Vidalytics

by vidalytics

Manage your Vidalytics videos and analytics from your AI assistant.

answering

details.page — questions

Answers built from our own checks of this server.

Why is there no tool list for details.page?

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 details.page working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 163 ms. The bar chart above shows every period we have measured.

How do I connect details.page?

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 will need your own key: it refuses anonymous clients.

Does details.page need an API key?

Yes. Every time we knock, details.page answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is details.page?

It answers our handshake in 163 ms on average, which is faster than 74% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.