Yesterdays Number vs Linkedin Humblebrag

In-depth architectural comparison of the Yesterdays Number and Linkedin Humblebrag MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Y

Choose Yesterdays Number when:

• You need dedicated capabilities in the Social Media domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: yesterdays_number_get.

Explore Yesterdays Number Details

Choose Linkedin Humblebrag when:

• You need dedicated capabilities in the Social Media domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Linkedin Humblebrag Details

Feature & Specification Comparison

Specification	Y Yesterdays Number Social Media	Linkedin Humblebrag Social Media
Summary	yesterdays-number MCP — wraps StupidAPIs (requires X-API-Key)	linkedin-humblebrag MCP — wraps StupidAPIs (requires X-API-Key)
Category & Scope	Social Media	Social Media
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "yesterdays-number": {
      "command": "npx",
      "args": [
        "-y",
        "yesterdays-number"
      ]
    }
  }
}

{
  "mcpServers": {
    "linkedin-humblebrag": {
      "command": "npx",
      "args": [
        "-y",
        "linkedin-humblebrag"
      ]
    }
  }
}

Related MCP Server Comparisons