Flux LinkedIn MCP
MCP server · www.fluxgraph.app · found in a public list · checked since 2026-11-02
Live, handshake completed · latest check
Analyses LinkedIn post performance and research for public profiles and company pages.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Read posts and profiles: Search and fetch public posts, profiles, comments, followers and videos from social platforms.
https://www.fluxgraph.app/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 2 checks, oldest to newest; room for 28 more
2 passed, 0 failed, 28 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-11-02 | 2 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-11-02 | 2 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
add_campaign_accountsadd_to_collectionadd_to_segmentclaim_previewcreate_campaigncreate_collectioncreate_segmentcreate_streamdelete_streamfind_similar_postsget_alertsget_alumni_engagersget_campaign_statsget_company_engagement_overlapget_cost_estimateget_credit_balanceget_engagement_briefget_engagement_industry_breakdownget_engagement_trendsget_engager_position_historyget_outreach_pathget_outreach_queueget_post_engagers_by_companyget_post_set_engagersget_posting_insightsget_postsget_profile_summaryget_stream_feedget_target_warmth_briefget_topic_insightsget_usage_historylinkedin_ad_searchlinkedin_company_postslinkedin_company_searchlinkedin_job_searchlinkedin_people_searchlinkedin_post_commentslinkedin_post_reactionslinkedin_post_searchlinkedin_profile_comments+27
- Tools
- 67
- This list since
- 2026-11-03
- First listed to us
- 2026-11-02
- List changes, 90 days
- 1
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- tools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
list_profilespreview_profile linkedin_url*preview_posting_insights preview_id*preview_search_posts preview_id* query*claim_preview preview_id*get_posts profile_id* scope date_from date_to post_type min_engagement search sort_by sort_dir page page_sizeget_profile_summary profile_id*get_posting_insights profile_id* scope date_from date_toget_topic_insights profile_id* n bigrams scope date_from date_toget_engagement_trends profile_id* scope granularity date_from date_to rolling_windowsearch_posts profile_id* query* scope mode limitget_credit_balance
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Search and information / Social media / Read posts and profiles (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-11-02. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 386 ms |
cloudflare:MIA |
Live, handshake completed HTTP 200 | 384 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_276872a4a78d66a6