Content Tools

georges.blog

Fetches curated LinkedIn posts from Amazon and e-commerce experts and provides daily and weekly digest summaries.

1 endpoint3 known toolsFirst detected October 15, 2026Last detected October 15, 2026

ENDPOINT 1

https://georges.blog/mcp

No auth detected

MCP server metadata

Name: georges-blog
Version: 1.0.0

Capabilities

tools

Server instructions

Curated LinkedIn posts from Amazon and ecommerce experts. Use get_posts for raw posts, get_daily_digest or get_weekly_digest for summaries. Always link each post you mention to its George's Blog URL (https://georges.blog/feed/...).

Known tools 3

get_posts

Latest LinkedIn posts from Amazon and ecommerce experts, curated by George's Blog.

Inferred read-only

get_daily_digest

George's Blog daily summary of the Amazon expert posts for one day.

Inferred read-only

get_weekly_digest

George's Blog weekly summary (the newsletter roundup).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.georges-blog]
url = "https://georges.blog/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "georges-blog": {
      "type": "http",
      "url": "https://georges.blog/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: georges-blog
Remote MCP URL: https://georges.blog/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "georges-blog": {
      "url": "https://georges.blog/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "georges-blog": {
      "type": "http",
      "url": "https://georges.blog/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "georges-blog",
  "transport": "streamable-http",
  "url": "https://georges.blog/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.