Skip to main content
Glama

Linkedin Humblebrag

Server Details

linkedin-humblebrag MCP — wraps StupidAPIs (keyless — no credential needed)

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-linkedin-humblebrag
GitHub Stars
0
Server Listing
linkedin-humblebrag
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 45 tools

Disambiguation2/5

Several clusters of tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded and deep_research all answer questions over the same catalog, and the polymarket family (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread, bet_research) plus entity_profile/company_facts/compare_entities/recent_changes/resolve_entity all target the same company-data domain. The verbose descriptions do argue for their own use, but with 45 tools an agent faces real misselection risk, and the server name ('Linkedin Humblebrag') gives no hint that this is a general data gateway.

Naming Consistency3/5

Everything is snake_case and most names are verb_noun (resolve_entity, validate_claim, compare_entities, scan_dependency, remember/recall/forget), but there are many noun-first exceptions (entity_profile, company_facts, prediction_calibration, resolution_audit/diff, kalshi_weather_edge) and inconsistent vendor prefixes (pipeworx_, polymarket_, updown_). Readable, but the pattern is mixed rather than predictable.

Tool Count2/5

45 tools is well past the 25+ threshold and the surface is a grab-bag spanning SEC financials, prediction-market arbitrage, web archives, LLM visibility probes, npm dependency scans, and memory/subscription plumbing. Individual tools may earn their place, but as a set it is bloated and forces the agent to select among many partially redundant options.

Completeness3/5

Within the apparent 'universal data gateway' domain, coverage is broad: entity resolution, research, monitoring subscriptions, prediction-market analytics, memory, and feedback all exist as full CRUD-ish lifecycles. However, the advertised purpose (LinkedIn humblebrag generation) is covered by a single tool, and gaps like no batch/cancel operations for research rows and court-calendar explicitly unsupported leave notable holes.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Local-first MCP server using LinkedIn's official OAuth and REST APIs to connect a member account, read profile, and publish text posts.
      4
      156 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that posts PDF/carousel content to a personal LinkedIn profile via LinkedIn's official REST API. It handles OAuth and provides tools to upload documents and publish posts.
      156 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      A production-ready MCP server for interacting with the LinkedIn API, enabling profile lookup, post creation and deletion, image posting, and organization page management through a secure tool-based interface.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.