Home / MCP registry index / app.fluxgraph/linkedin

Flux LinkedIn MCP

app.fluxgraph/linkedin in the official MCP registry. Endpoint https://www.fluxgraph.app/mcp.

The registry describes it as: LinkedIn intelligence: post analytics and research for public profiles and company pages.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http linkedin https://www.fluxgraph.app/mcp

{
  "mcpServers": {
    "linkedin": {
      "url": "https://www.fluxgraph.app/mcp"
    }
  }
}

code --add-mcp '{"name":"linkedin","type":"http","url":"https://www.fluxgraph.app/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_profiles preview_profile preview_posting_insights preview_search_posts claim_preview get_posts get_profile_summary get_posting_insights get_topic_insights get_engagement_trends search_posts get_credit_balance get_usage_history get_cost_estimate create_stream list_streams get_stream_feed pause_stream resume_stream delete_stream run_stream_now linkedin_profile_info linkedin_profile_posts linkedin_company_posts linkedin_post_search linkedin_profile_reactions linkedin_profile_comments linkedin_job_search linkedin_ad_search linkedin_people_search linkedin_company_search linkedin_post_reactions linkedin_post_comments find_similar_posts score_draft suggest_angles list_segments create_segment add_to_segment remove_from_segment resolve_segment list_segment_templates get_alerts create_collection add_to_collection remove_from_collection list_collections resolve_collection create_campaign add_campaign_accounts map_constellation score_connections get_outreach_queue get_engagement_brief log_outcome get_campaign_stats save_post get_post_engagers_by_company get_engagement_industry_breakdown get_alumni_engagers and 7 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-02): a099e0f73a59ae86. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/app-fluxgraph-linkedin/badge.svg)](https://lazaretto.dev/mcp-registry/app-fluxgraph-linkedin)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Social media MCP servers · Image generation MCP servers · Analytics and SEO MCP servers