Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Flux LinkedIn MCP

REMOTE · WWW.FLUXGRAPH.APP

LinkedIn intelligence: post analytics and research for public profiles and company pages.

+6 this week 88 Trust /100

Last scanned (17 hours ago)

Scores higher than 95% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 14631 tokens (~203/item across 72 items; 72 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 73 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +1
    • Tool “log_outcome” rewrote its description, which is the text the model reads security
    • New tool “get_inbound_attribution” functional
    • “log_outcome” added an optional parameter “message_text” cosmetic
    • “log_outcome” added an optional parameter “occurred_at” cosmetic
    • “log_outcome” added an optional parameter “outcome_id” cosmetic
    • “log_outcome” added an optional parameter “post_url” cosmetic
    • “log_outcome” added an optional parameter “profile_id” cosmetic
    • “log_outcome” reworded the description of “action” cosmetic
    • “log_outcome” reworded the description of “campaign_id” cosmetic
    • “log_outcome” reworded the description of “linkedin_url” cosmetic
    • “log_outcome” reworded the description of “person_id” cosmetic
    • “log_outcome” made “campaign_id” optional cosmetic
    • Tool “log_outcome” changed its title: Log Outreach Outcome → Log Outcome cosmetic
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +4
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “add_campaign_accounts” rewrote its description, which is the text the model reads security
    • Tool “add_to_collection” rewrote its description, which is the text the model reads security
    • Tool “add_to_segment” rewrote its description, which is the text the model reads security
    • Tool “claim_preview” rewrote its description, which is the text the model reads security
    • Tool “create_campaign” rewrote its description, which is the text the model reads security
    • Tool “create_collection” rewrote its description, which is the text the model reads security
    • Tool “create_segment” rewrote its description, which is the text the model reads security
    • Tool “create_stream” rewrote its description, which is the text the model reads security
    • Tool “delete_stream” rewrote its description, which is the text the model reads security
    • Tool “enrich_people” rewrote its description, which is the text the model reads security
    • Tool “find_similar_posts” rewrote its description, which is the text the model reads security
    • Tool “get_alerts” rewrote its description, which is the text the model reads security
    • Tool “get_alumni_engagers” rewrote its description, which is the text the model reads security
    • Tool “get_campaign_stats” rewrote its description, which is the text the model reads security
    • Tool “get_company_engagement_overlap” rewrote its description, which is the text the model reads security
    • Tool “get_cost_estimate” rewrote its description, which is the text the model reads security
    • Tool “get_credit_balance” rewrote its description, which is the text the model reads security
    • Tool “get_engagement_brief” rewrote its description, which is the text the model reads security
    • Tool “get_engagement_industry_breakdown” rewrote its description, which is the text the model reads security
    • Tool “get_engagement_trends” rewrote its description, which is the text the model reads security
    • Tool “get_engager_position_history” rewrote its description, which is the text the model reads security
    • Tool “get_outreach_path” rewrote its description, which is the text the model reads security
    • Tool “get_outreach_queue” rewrote its description, which is the text the model reads security
    • Tool “get_post_engagers_by_company” rewrote its description, which is the text the model reads security
    • Tool “get_post_set_engagers” rewrote its description, which is the text the model reads security
    • Tool “get_posting_insights” rewrote its description, which is the text the model reads security
    • Tool “get_posts” rewrote its description, which is the text the model reads security
    • Tool “get_profile_summary” rewrote its description, which is the text the model reads security
    • Tool “get_stream_feed” rewrote its description, which is the text the model reads security
    • Tool “get_target_warmth_brief” rewrote its description, which is the text the model reads security
    • Tool “get_topic_insights” rewrote its description, which is the text the model reads security
    • Tool “get_usage_history” rewrote its description, which is the text the model reads security
    • Tool “linkedin_ad_search” rewrote its description, which is the text the model reads security
    • Tool “linkedin_company_info” rewrote its description, which is the text the model reads security
    • Tool “linkedin_company_posts” rewrote its description, which is the text the model reads security
    • Tool “linkedin_company_search” rewrote its description, which is the text the model reads security
    • Tool “linkedin_job_search” rewrote its description, which is the text the model reads security
    • Tool “linkedin_people_search” rewrote its description, which is the text the model reads security
    • Tool “linkedin_post_comments” rewrote its description, which is the text the model reads security
    • Tool “linkedin_post_reactions” rewrote its description, which is the text the model reads security
    • Tool “linkedin_post_search” rewrote its description, which is the text the model reads security
    • Tool “linkedin_profile_comments” rewrote its description, which is the text the model reads security
    • Tool “linkedin_profile_info” rewrote its description, which is the text the model reads security
    • Tool “linkedin_profile_posts” rewrote its description, which is the text the model reads security
    • Tool “linkedin_profile_reactions” rewrote its description, which is the text the model reads security
    • Tool “list_collections” rewrote its description, which is the text the model reads security
    • Tool “list_profiles” rewrote its description, which is the text the model reads security
    • Tool “list_segment_templates” rewrote its description, which is the text the model reads security
    • Tool “list_segments” rewrote its description, which is the text the model reads security
    • Tool “list_streams” rewrote its description, which is the text the model reads security
    • Tool “log_outcome” rewrote its description, which is the text the model reads security
    • Tool “map_constellation” rewrote its description, which is the text the model reads security
    • Tool “pause_stream” rewrote its description, which is the text the model reads security
    • Tool “preview_posting_insights” rewrote its description, which is the text the model reads security
    • Tool “preview_profile” rewrote its description, which is the text the model reads security
    • Tool “preview_search_posts” rewrote its description, which is the text the model reads security
    • Tool “remove_from_collection” rewrote its description, which is the text the model reads security
    • Tool “remove_from_segment” rewrote its description, which is the text the model reads security
    • Tool “resolve_collection” rewrote its description, which is the text the model reads security
    • Tool “resolve_segment” rewrote its description, which is the text the model reads security
    • Tool “resume_stream” rewrote its description, which is the text the model reads security
    • Tool “run_stream_now” rewrote its description, which is the text the model reads security
    • Tool “save_post” rewrote its description, which is the text the model reads security
    • Tool “score_connections” rewrote its description, which is the text the model reads security
    • Tool “score_draft” rewrote its description, which is the text the model reads security
    • Tool “search_posts” rewrote its description, which is the text the model reads security
    • Tool “suggest_angles” rewrote its description, which is the text the model reads security
    • Tool “traverse_graph” rewrote its description, which is the text the model reads security
    • Tool “traverse_graph_help” rewrote its description, which is the text the model reads security
    • Tool “claim_preview” is now declared destructive security
    • Tool “delete_stream” is now declared destructive security
    • Tool “remove_from_collection” is now declared destructive security
    • Tool “remove_from_segment” is now declared destructive security
    • Schema quality: 158 → 198 ▼ functional
    • The server now declares the “prompts” capability functional
    • First check of Schema quality: 100 functional
    • Destructive annotations: All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • New prompt “monthly-client-report” functional
    • New prompt “research-a-prospect” functional
    • New prompt “triage-linkedin-urls” functional
    • New prompt “warm-path-to” functional
    • New prompt “warm-way-into-account” functional
    • New prompt “what-to-post-more-of” functional
    • New prompt “who-at-company-engages” functional
    • New prompt “who-engaged” functional
    • New tool “resolve_company” functional
    • New tool “resolve_people” functional
    • “get_alumni_engagers” added an optional parameter “company_name” cosmetic
    • “get_alumni_engagers” added an optional parameter “linkedin_company_id” cosmetic
    • “get_company_engagement_overlap” added an optional parameter “company_a_linkedin_id” cosmetic
    • “get_company_engagement_overlap” added an optional parameter “company_a_name” cosmetic
    • “get_company_engagement_overlap” added an optional parameter “company_b_linkedin_id” cosmetic
    • “get_company_engagement_overlap” added an optional parameter “company_b_name” cosmetic
    • “get_post_set_engagers” added an optional parameter “post_ids” cosmetic
    • “get_post_set_engagers” added an optional parameter “post_urls” cosmetic
    • “log_outcome” added an optional parameter “linkedin_url” cosmetic
    • “create_segment” reworded the description of “config” cosmetic
    • “get_cost_estimate” reworded the description of “params” cosmetic
    • “get_cost_estimate” reworded the description of “tool_name” cosmetic
    • “get_post_set_engagers” reworded the description of “max_posts” cosmetic
    • “log_outcome” reworded the description of “person_id” cosmetic
    • “log_outcome” made “person_id” optional cosmetic
  • 14 Nov 26 0
    • Tool “add_campaign_accounts” rewrote its description, which is the text the model reads security
    • Tool “add_to_segment” rewrote its description, which is the text the model reads security
    • Tool “create_segment” rewrote its description, which is the text the model reads security
    • Tool “get_alumni_engagers” rewrote its description, which is the text the model reads security
    • Tool “get_campaign_stats” rewrote its description, which is the text the model reads security
    • Tool “get_credit_balance” rewrote its description, which is the text the model reads security
    • Tool “get_outreach_path” rewrote its description, which is the text the model reads security
    • Tool “linkedin_company_search” rewrote its description, which is the text the model reads security
    • Tool “linkedin_people_search” rewrote its description, which is the text the model reads security
    • Tool “list_segment_templates” rewrote its description, which is the text the model reads security
    • Tool “log_outcome” rewrote its description, which is the text the model reads security
    • Tool “map_constellation” rewrote its description, which is the text the model reads security
    • Tool “remove_from_segment” rewrote its description, which is the text the model reads security
    • Tool “resolve_segment” rewrote its description, which is the text the model reads security
    • Schema quality: 143 → 158 ▼ functional
    • New tool “enrich_people” functional
    • New tool “linkedin_company_info” functional
    • “linkedin_company_search” added an optional parameter “page” cosmetic
    • “linkedin_people_search” added an optional parameter “page” cosmetic
    • “create_segment” reworded the description of “config” cosmetic
    • “get_cost_estimate” reworded the description of “params” cosmetic
    • “linkedin_job_search” reworded the description of “companyId” cosmetic
    • “linkedin_people_search” reworded the description of “company” cosmetic
    • “linkedin_people_search” reworded the description of “title” cosmetic
    • “map_constellation” reworded the description of “max_targets” cosmetic
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 0
    • Tool “get_engagement_industry_breakdown” rewrote its description, which is the text the model reads security
    • Tool “get_post_set_engagers” rewrote its description, which is the text the model reads security
    • Tool “linkedin_post_comments” rewrote its description, which is the text the model reads security
    • Tool “linkedin_post_reactions” rewrote its description, which is the text the model reads security
    • “get_post_set_engagers” added an optional parameter “max_pages_per_post” cosmetic
    • “linkedin_post_comments” added an optional parameter “max_pages” cosmetic
    • “linkedin_post_reactions” added an optional parameter “max_pages” cosmetic
    • “linkedin_post_comments” reworded the description of “refresh” cosmetic
    • “linkedin_post_reactions” reworded the description of “refresh” cosmetic
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://www.fluxgraph.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fluxgraph.app CN=YR2,O=Let's Encrypt,C=US 10 Oct 2026 8 Jan 2027 RSA 2048 SHA256-RSA 5295c50efc4a846063868806d0cf31bc630
SANs: *.fluxgraph.app, fluxgraph.app
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.fluxgraph.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
fluxgraph.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", error_description="Sign in to Flux to use this tool", resource_metadata="https://www.fluxgraph.app/.well-known/oauth-protected-resource/mcp"

Bearer error="invalid_token", error_description="Sign in to Flux to use this tool", resource_metadata="https://www.fluxgraph.app/.well-known/oauth-protected-resource/mcp"
Header Value
strict-transport-security max-age=63072000

Protected resource metadata

Document https://www.fluxgraph.app/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://www.fluxgraph.app/mcp
Authorisation server https://flqwttpbzetagwisyoly.supabase.co/auth/v1

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.fluxgraph.app/mcp Verified 200
http (plaintext) http://www.fluxgraph.app/mcp HTTPS enforced 308 https://www.fluxgraph.app/mcp
MCP tools · 72 exposed · ~13,766 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_campaign_accounts ~121

[Act · writes] Add one or more target companies to a Constellation campaign. Each account is a company you want to reach; map_constellation is then run per-account. Accounts already in the campaign (same linkedin_company_id, or same case-insensitive trimmed company_name) and repeats within the same call are not re-added; they are returned under `skipped`. Free — costs 0 credits.

NameTypeReqDescription
accountsarrayyesArray of companies to add (1-500 per call)
campaign_idstringyesTarget campaign id

No output schema declared.

No examples provided.

add_to_collection ~121

[Act · writes] Pin one or more posts (by post_id) into a collection you own — works on any collection type. On a 'manual' collection this is the only membership mechanism; on a 'smart' collection it adds the posts as extras alongside whatever the rule already matches (resolve_collection returns the union). Existing members are silently ignored. Free — costs 0 credits.

NameTypeReqDescription
collection_idstringyesTarget collection id from list_collections
post_idsarrayyespost_ids to add (1-1000 per call)

No output schema declared.

No examples provided.

add_to_segment ~106

[Act · writes] Add one or more people (by person_id) to a manual audience segment. Existing members are silently ignored. Smart segments are rejected: their membership is computed from `config` by resolve_segment. Unknown person_ids are rejected as a whole (nothing is added). Free — costs 0 credits.

NameTypeReqDescription
person_idsarrayyesperson_ids to add (1-1000 per call)
segment_idstringyesTarget segment id from list_segments

No output schema declared.

No examples provided.

claim_preview ~95

[Act · writes · irreversible] Make a profile from preview_profile your own Flux dashboard. Call this only when the person says the profile is theirs: the person cannot undo a claim. Requires sign-in; creates a free dashboard showing the latest 50 posts, one per account. Refuses if the account already has a dashboard; the breakdown tools still work then.

NameTypeReqDescription
preview_idstringyespreview_id returned by preview_profile

No output schema declared.

No examples provided.

create_campaign ~75

[Act · writes] Create a Constellation outreach campaign. A campaign groups target accounts, the people you care about at those accounts, and the warm connections you could approach to reach them. Free — costs 0 credits.

NameTypeReqDescription
descriptionstring–Optional longer description
namestringyesUser-facing campaign name

No output schema declared.

No examples provided.

create_collection ~204

[Act · writes] Create a new post collection for the authenticated user. Set type='manual' to hand-curate posts with add_to_collection, or type='smart' with a `config` predicate (e.g. {format:'video',min_likes:50}) to define a dynamic collection resolved on-demand by resolve_collection. Free — costs 0 credits.

NameTypeReqDescription
configobject–Predicate for smart collections. Supported keys: format, min_likes, min_comments, date_after, date_before, topic_contains, author_profile_id, profile_ids (array — posts whose profile_id is in the set…
descriptionstring–Optional longer description
namestringyesUser-facing collection name
typestringyes'manual' = hand-curated post list. 'smart' = dynamic predicate (requires `config`).

No output schema declared.

No examples provided.

create_segment ~484

[Act · writes] Create a new audience segment (named group of people) for the authenticated user. Set type='manual' for a hand-curated list (use add_to_segment to populate it), type='smart' with a `config` predicate (e.g. {title_contains:['VP','Chief']}) to define a dynamic segment resolved on-demand by resolve_segment, or pass `template` to pre-fill `config` from a built-in template (type defaults to 'smart'). Smart segments only match people connected to you: people who engaged with posts you can see in Flux (your own profile, tracked/monitored profiles, and posts you collected) and people in your campaigns' constellations. Smart segment membership is computed, so add_to_segment / remove_from_segment do not apply to it. Free — costs 0 credits.

NameTypeReqDescription
configobject–Predicate object for smart segments. Supported keys: title_contains, company_contains. Each takes a non-empty string or an array of 1-20 non-empty strings (case-insensitive substring match; an array…
descriptionstring–Optional longer description
namestring–User-facing segment name. Optional when `template` is supplied — the template's default name is used.
source_stream_idstring–Optional stream that produced this segment (for traceability)
templatestring–Optional pre-built template id. Available: 'vp_plus' (VP+ decision-makers), 'c_suite' (C-suite executives), 'heads_of' ('Head of' leaders), 'founders' (Founders & co-founders), 'fintech_leaders' (Fin…
typestring–Segment type. 'manual' = hand-curated person list. 'smart' = dynamic predicate (requires `config`). 'auto_stream' = system-managed from a stream. Defaults to 'smart' when `template` is provided.

No output schema declared.

No examples provided.

create_stream ~413

[Act · writes · schedules paid runs] Create a new research stream (external profile, company, topic, person interests, hiring signals, or ad watch). Running the stream on its schedule costs credits (see get_cost_estimate for the per-type cost). own_profile streams are not created here — they come from subscription checkout.

NameTypeReqDescription
history_daysinteger–How far back the first run should reach, in days. Bounds the walk by TIME where initial_max_pages bounds it by COST — the run stops at whichever limit it hits first, so pair a window with enough page…
initial_max_pagesinteger–Opt-in deep first-run for external_profile, company and person_interests streams (1-5, default 1). A budget, not a price — you are billed for pages actually walked. A page is ~50 posts for profile/co…
namestringyesUser-facing label for this stream
paramsobject–Type-specific config: topic uses {query, authorsIndustryId?, contentType?, postedLimit?, sortBy?}; hiring_signals/ad_watch use {company?, keywords?, ...}
schedulestring–Run schedule. Defaults to 'weekly'. 'monthly' runs every 30 days — the cheapest recurring cadence, and the usual choice for client profiles reported on monthly.
source_urlstring–LinkedIn URL for external_profile / company / person_interests streams
typestringyesStream type

No output schema declared.

No examples provided.

delete_stream ~94

[Act · writes · destructive] Delete a stream and its stream_runs. Posts collected by the stream stay in your library (stream_id is set to NULL via ON DELETE SET NULL) so historical data isn't lost. Auto-collection is deleted with the stream. own_profile streams cannot be deleted through this tool; the own profile is managed from Settings and billing.

NameTypeReqDescription
stream_idstringyesStream ID from list_streams

No output schema declared.

No examples provided.

enrich_people ~324

[Acquire · 3 credits/person enriched] Look up full LinkedIn profiles for up to 100 people and store their current title, company, headline and job history (every position). Job history is what get_outreach_path (coworker / alumni paths) and get_alumni_engagers search, and engagers collected from reactions/comments have none until enriched — when those tools report missing coverage they return a _meta.next_step with the exact person_ids to pass here. Pass person_ids (people.id from any engager / path tool) and/or linkedin_urls. Costs 3 credits per person successfully enriched. People you already have (connected to you: they engaged with your posts, are in your campaigns or segments, or you pulled or enriched them) who were enriched in the last 90 days are skipped for free unless refresh=true; anyone else is looked up and charged normally; failed or not-found lookups are free. The balance must cover 3 × the people to be looked up (after skips and max_credits) before anything runs; you are charged only for successes.

NameTypeReqDescription
linkedin_urlsarray–LinkedIn profile URLs to enrich; people not yet in the graph are added
max_creditsinteger–Spend cap. At most floor(max_credits / 3) people are looked up; the rest come back skipped_budget.
person_idsarray–people.id UUIDs to enrich (1-100)
refreshboolean–Re-enrich people enriched within the last 90 days (bypasses the cache)

No output schema declared.

No examples provided.

find_similar_posts ~202

[Read · free] Find persisted posts whose embeddings are nearest to a free-text query — pgvector cosine over the local post library, no LinkedIn pull, free. Use when you have a *block of text* (a draft, a paragraph, a competitor's post) and want similar posts you've already collected. For keyword search prefer `search_posts`; for fresh LinkedIn keyword pulls use `linkedin_post_search`. Pass `profile_id` to scope to a tracked profile, `collection_id` to scope to a collection, or neither to search the entire library.

NameTypeReqDescription
collection_idstring–Optional post_collections.id (scopes search to this collection's members)
limitnumber–Max results to return (1-50, default 5)
profile_idstring–Optional tracked profile ID from list_profiles (scopes search to this profile's posts)
textstringyesText to find similar posts for

No output schema declared.

No examples provided.

get_alerts ~92

[Read · free] Return recent alerts for the authenticated user's streams. An alert is emitted whenever a scheduled stream run surfaces new items. Pass `unread_only=true` to skip alerts the user has already marked read. Free — costs 0 credits.

NameTypeReqDescription
limitinteger–Max alerts to return (default 50)
unread_onlyboolean–Return only alerts that have not been marked read

No output schema declared.

No examples provided.

get_alumni_engagers ~359

[Read · free] Given a company (company_url, LinkedIn's numeric linkedin_company_id as linkedin_company_info returns it, an exact company_name, or a companies.id UUID), return engagers (across your collected posts) who have a position at that company. Relation filter: 'coworker' = current employees, 'alumni' = any past or current position (most useful for page_type='SCHOOL' companies), 'any' = both. Matches need job history on file, and engagers collected from reactions/comments usually have none: `coverage` counts candidates (engagers whose headline or current company names the company) with and without job history, and when missing data may hide matches `_meta.next_step` names enrich_people with the exact person_ids to pass and its credit cost. The company must be saved in Flux: if it is not, the error's `_meta.next_step` names linkedin_company_info (1 credit) with the arguments that save it; a company_name that matches several saved companies returns `candidates` to pick from instead of guessing. Pure DB read — no LinkedIn pull, no credits charged.

NameTypeReqDescription
company_idstring–companies.id UUID
company_namestring–Exact company name, case-insensitive. Several matches return candidates.
company_urlstring–Public LinkedIn company URL
limitinteger–Max engagers to return (1-100, default 20)
linkedin_company_idstring|number–LinkedIn's numeric company id (the `id` linkedin_company_info returns)
relationstring–coworker = current employees only; alumni = any position (past or current); any = both

No output schema declared.

No examples provided.

get_campaign_stats ~109

[Read · free] Summary stats for a Constellation campaign: target count, entry count, outreach volume, and acceptance / reply rates broken down by pool (coworker / engager / mutual) and composite-score tier. Outcomes logged for people who are not campaign entries are counted under an `unattributed` bucket in both by_pool and by_tier, so breakdowns always sum to the totals. Free — costs 0 credits.

NameTypeReqDescription
campaign_idstringyesCampaign id

No output schema declared.

No examples provided.

get_company_engagement_overlap ~414

[Read · free] Given two companies, return the people who engaged (reacted or commented) with posts published by BOTH companies' own LinkedIn pages, counting only company-page posts and engagers already collected in your library. Use it to find people interested in two target accounts at once. It does NOT compare which employees of each company engage with you (for that, use get_post_engagers_by_company). It needs data collected first: each company's page posts (a company stream, or linkedin_company_posts) and their engagers (get_post_set_engagers on those posts, or linkedin_post_reactions / linkedin_post_comments); when a company has no page posts in your library the response says so. Identify each company by company_x_url, company_x_linkedin_id (LinkedIn's numeric id, as linkedin_company_info returns it), company_x_name (exact, case-insensitive; several matches return candidates instead of a guess) or company_x_id (companies.id UUID). A company not saved in Flux returns `_meta.next_step` naming linkedin_company_info (1 credit). Pure DB read — no LinkedIn pull, no credits charged.

NameTypeReqDescription
company_a_idstring–Company A — companies.id UUID
company_a_linkedin_idstring|number–Company A — LinkedIn's numeric company id (from linkedin_company_info)
company_a_namestring–Company A — exact company name, case-insensitive
company_a_urlstring–Company A — LinkedIn URL
company_b_idstring–Company B — companies.id UUID
company_b_linkedin_idstring|number–Company B — LinkedIn's numeric company id (from linkedin_company_info)
company_b_namestring–Company B — exact company name, case-insensitive
company_b_urlstring–Company B — LinkedIn URL
limitinteger–Max overlapping engagers to return (1-100, default 20)

No output schema declared.

No examples provided.

get_cost_estimate ~342

[Meta · free] Preview what a tool call will cost before running it. Pass tool_name plus the params you intend to call it with: variable-cost tools (get_post_set_engagers, map_constellation, enrich_people, linkedin_profile_posts, linkedin_company_posts, linkedin_post_reactions, linkedin_post_comments, run_stream_now) are priced from those params with the same formula the tool's balance pre-check uses. Returns { tool_name, cost_max, cost_typical?, unit, explanation, cost (= cost_max), balance, sufficient, known_tool }. cost_max is the worst case the balance must cover; cost_typical is what such a call usually costs (you are charged only for what is actually fetched). Also accepts a stream type (external_profile, company, topic, person_interests, hiring_signals, ad_watch) to preview its per-page run price (stream_cost). Free.

NameTypeReqDescription
paramsobject–The params you plan to call the tool with. Examples: get_post_set_engagers { profile_id | collection_id | post_ids / post_urls, max_posts, max_pages_per_post, max_enrich, freshness_days } (with a sco…
tool_namestringyesMCP tool name (e.g. 'get_post_set_engagers') or stream type (e.g. 'external_profile')

No output schema declared.

No examples provided.

get_credit_balance ~57

[Meta · free] Return the authenticated user's current credit balance, the current calendar month's credit period (UTC), that month's allocation if one was granted (null otherwise), credits used since the period started, and the most recent allocation. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_engagement_brief ~180

[Read · free] For one person, return their recent posts most relevant to what you post about — plus suggested talking points. Use before a warm comment or DM. Free — costs 0 credits. Identify the person via *exactly one* of: `target_id` (a Constellation target — original input), `person_id` (a row in `people`), or `linkedin_url` (any form). The non-campaign forms work even when no Constellation campaign exists.

NameTypeReqDescription
linkedin_urlstring–LinkedIn profile URL (vanity or encoded form) — auto-resolved to a people row
person_idstring–people.id — when you already have the canonical person row
target_idstring–Constellation targets.id — for the original campaign-scoped flow

No output schema declared.

No examples provided.

get_engagement_industry_breakdown ~254

[Read · free] Histogram of engagers' companies grouped by industry. Pivots on companies.industry_hierarchy (e.g. 'Tech > Software Development'). Depth=1 buckets by top-level, =2 by top+mid, =3 by full hierarchy. Engagers with no current company / no industry hierarchy bucket as `_unknown`. Pure DB read — no LinkedIn pull, no credits charged. Needs engagers synced first: if the post(s) have no recorded engagements, run `get_post_set_engagers` (1 credit per page, works on a collection or profile) as the usual first step; `linkedin_post_reactions` / `linkedin_post_comments` (1 credit per page of up to 100 people, so usually 1 credit each) pull a single post.

NameTypeReqDescription
depthinteger–1=top-level industry, 2=mid, 3=leaf (full hierarchy)
post_idstring–posts.id UUID
post_urlstring–Public LinkedIn post URL
sample_companies_per_bucketinteger–How many sample company names to attach per industry row (0-10, default 3)

No output schema declared.

No examples provided.

get_engagement_trends ~185

[Read · free] Get engagement time series for a profile with gap-filled buckets, rolling averages, and trend direction. Each bucket includes avg engagement, likes, comments, shares, and conversation rate. Useful for understanding whether engagement is growing or declining. Pass `scope` (a post_collections.id) to plot trends for a specific collection.

NameTypeReqDescription
date_fromstring–Start date (ISO 8601)
date_tostring–End date (ISO 8601)
granularitystring–Time bucket granularity
profile_idstringyesTracked profile ID from list_profiles
rolling_windownumber–Rolling average window size in buckets (default: 4 for weekly, 7 for daily, 3 for monthly)
scopestring–Optional post_collections.id to scope the time series

No output schema declared.

No examples provided.

get_engager_position_history ~144

[Read · free] Return a person's full employment timeline from the position graph. Only for people connected to you: they engaged with posts you can see in Flux, are in one of your campaigns or segments, or you pulled them (an engagement pull, or their profile via linkedin_profile_info / linkedin_profile_posts). Anyone else returns not-found with a next_step to pull their profile via linkedin_profile_info. Sorted current-first, then most-recent past by started_at desc. Pure DB read — no LinkedIn pull, no credits charged.

NameTypeReqDescription
linkedin_urlstring–Person's LinkedIn profile URL
person_idstring–people.id UUID

No output schema declared.

No examples provided.

get_inbound_attribution ~195

[Read · free] Which of your posts bring in DMs, leads and clients, next to which get engagement. Reads the inbound outcomes logged with log_outcome (inbound_dm | lead | client) for one of your tracked profiles over the last `days` (default 90). Returns totals, top_by_outcomes (posts credited with at least one outcome), top_by_engagement (your most-engaged posts in the window, with their outcome counts, so the two rankings can be compared), by_format, and the unattributed outcomes still waiting for a post (fix with log_outcome outcome_id + post_url). Engagement is not used to attribute: outcomes are matched by post_url, message text and timing. Free — costs 0 credits.

NameTypeReqDescription
daysinteger–Look-back window in days (default 90)
profile_idstringyesYour tracked profile id from list_profiles

No output schema declared.

No examples provided.

get_outreach_path ~224

[Read · free] Given a target person, find the shortest warm-intro path through your engager network. Walks coworker (shared current company) + alumni (shared past company / school) edges. Up to 3 hops. Paths only exist where job history is on file, and engagers collected from reactions/comments usually have none: the response's `coverage` says how many candidates (the target, and engagers tied to the target's companies) have job history, and when missing data may hide paths `_meta.next_step` names enrich_people with the exact person_ids to pass and its credit cost. Pure DB read — no LinkedIn pull, no credits charged.

NameTypeReqDescription
limitinteger–Max paths to return (default 10)
max_hopsinteger–Max path length (1=direct, 2=one intermediate, 3=two intermediates). Default 2.
target_linkedin_urlstring–Target — LinkedIn URL
target_person_idstring–Target — people.id UUID

No output schema declared.

No examples provided.

get_outreach_queue ~318

[Read · free] Return a prioritized outreach queue. Provide *exactly one* of three scopes: • `campaign_id` — full Constellation queue, one row per person (their best entry's composite_score, pool, recommended_action), with `targets[]` listing every target they connect to ({target_id, entry_id, composite_score, pool, recommended_action, target_person: {person_id, full_name, current_title}}) and prior outreach_log entries. Pools: coworker = same company as the target (no relationship implied), engager = someone the target engages with, mutual = someone several targets engage with. Pass a target_person.person_id to get_outreach_path to check warm paths. • `segment_id` — people in a saved audience segment, ranked by their engagement count against your tracked profiles' posts. No composite_score. • `linkedin_urls` — an ad-hoc list of LinkedIn URLs, same engagement-count ranking as segments. Free — costs 0 credits.

NameTypeReqDescription
campaign_idstring–Campaign id (full Constellation scoring)
limitinteger–Max entries to return (1-200, default 50)
linkedin_urlsarray–Ad-hoc LinkedIn URL list (engagement-count scoring); max 200
poolstring–Optional filter: only return entries in this pool. Only meaningful for `campaign_id` scope; ignored for segment / urls.
segment_idstring–Audience segment id (engagement-count scoring)

No output schema declared.

No examples provided.

get_post_engagers_by_company ~221

[Read · free] Given a LinkedIn post URL or id, return the companies whose people engaged (reacted/commented), ranked by engager count. Joins through person_positions(is_current=true). Pure DB read — no LinkedIn pull, no credits charged. Engagers without a known current company are bucketed as `_unknown_company`. Optional industry_urn filter narrows to one industry.

NameTypeReqDescription
industry_urnstring–Optional urn:li:fsd_industry:<id> filter (from companies.industry_urn)
limitinteger–Max companies to return (1-100, default 20)
post_idstring–posts.id UUID (use when you already know the local id)
post_urlstring–Public LinkedIn post URL (e.g. https://www.linkedin.com/feed/update/urn:li:activity:1234)
top_engagers_per_companyinteger–How many sample engager names to attach per company row (0-10, default 3)

No output schema declared.

No examples provided.

get_post_set_engagers ~630

[Acquire · 1 credit/page + 3/person enriched] Pull from LinkedIn (costs credits) and return the consolidated, deduped people who reacted to or commented on a SET of posts — one tracked profile's posts (profile_id), a post collection (collection_id), or an explicit list of up to 50 posts (post_ids and/or post_urls, e.g. the post_ids linkedin_post_search returns; a URL not yet in Flux is stubbed for free, no save_post needed). Fetches only posts not synced within freshness_days, walks up to max_pages_per_post pages (100 people/page) of reactions and of comments per post, includes comment replies, and enriches (title/company via a profile lookup) only never-seen people, up to max_enrich. Costs 1 credit per page fetched (a page is up to 100 people; a post with under 100 reactions and under 100 comments = 2 credits; the most a post can cost is 2 × max_pages_per_post) + 3 per person enriched; cached posts and cached pages are free. The balance must cover the worst case (posts × 2 × max_pages_per_post + max_enrich × 3) before anything runs (get_cost_estimate with these params returns the same number); you are charged only for pages actually fetched. When the balance is short, the insufficient_credits error spells out what the worst case assumed and lists `suggestions` (smaller max_pages_per_post / max_posts / max_enrich, each with its resulting max) that fit the balance. Per-post reactions_fetched / reactions_total / comments_total / truncated tell you when a post had more engagers than were fetched.

NameTypeReqDescription
collection_idstring–post_collections.id — engagers across this collection's posts
forceboolean–Re-sync posts even if within the freshness window
freshness_daysinteger–Skip posts whose engagers were synced within this many days
max_enrichinteger–Max never-seen engagers to enrich via /linkedin/profile (0-100, default 0)
max_pages_per_postinteger–Max pages (100 people each) to walk per endpoint per post (1-20, default 10). Each page costs 1 credit.
max_postsinteger–Max posts to sync this call (1-100). Default 25; with post_ids/post_urls the default is the list length.
post_idsarray–posts.id values (e.g. from linkedin_post_search results) — engagers across exactly these posts. Combine with post_urls; 50 total max. Each must be a post you can read.
post_urlsarray–LinkedIn post URLs — engagers across exactly these posts. URLs not yet in Flux get a stub row (no extra credit). Combine with post_ids; 50 total max.
profile_idstring–Tracked profile id — engagers across this profile's stored posts

No output schema declared.

No examples provided.

get_posting_insights ~151

[Read · free] Get optimal posting patterns for a profile: best day of week, best hour, format performance breakdown, and character length sweet spot. Includes full metric breakdown (likes, comments, shares, conversation rate) for every bucket. All metrics relative to the user's own baseline. Pass `scope` (a post_collections.id) to recompute the patterns against a specific collection.

NameTypeReqDescription
date_fromstring–Start date (ISO 8601)
date_tostring–End date (ISO 8601)
profile_idstringyesTracked profile ID from list_profiles
scopestring–Optional post_collections.id to scope the analysis

No output schema declared.

No examples provided.

get_posts ~295

[Read · free] List a tracked profile's persisted posts with full metrics and text — query against the local post library, no LinkedIn pull, free. Use this when the caller already has a profile_id and wants to read its posts. Filter by date range, post type, minimum engagement, or text. Pass `scope` (a post_collections.id) to restrict to a specific collection (e.g. an external profile, topic stream, or hand-curated set). Paginated. For keyword/semantic search across posts, use `search_posts`. For fresh LinkedIn pulls, use `linkedin_profile_posts`.

NameTypeReqDescription
date_fromstring–Start date (ISO 8601, e.g. 2025-01-01)
date_tostring–End date (ISO 8601)
min_engagementnumber–Minimum total engagement
pagenumber–Page number (1-based)
page_sizenumber–Results per page (max 50)
post_typestring–Filter by post type
profile_idstringyesTracked profile ID from list_profiles
scopestring–Optional post_collections.id to filter posts to a specific collection
searchstring–Text search across post content (case-insensitive)
sort_bystring–Sort field
sort_dirstring–Sort direction

No output schema declared.

No examples provided.

get_profile_summary ~69

[Read · free] Get KPI summary for a tracked profile: total posts, average engagement (broken down by likes/comments/shares/conversation rate), posts per week, engagement trend, top format, and posting goal status.

NameTypeReqDescription
profile_idstringyesTracked profile ID from list_profiles

No output schema declared.

No examples provided.

get_stream_feed ~81

[Read · free] Return the most recent posts a stream has collected into the library, newest first by published_at. Use this to browse what a topic / external profile / person_interests / company stream has surfaced on its schedule.

NameTypeReqDescription
limitnumber–Max posts to return
stream_idstringyesStream ID from list_streams

No output schema declared.

No examples provided.

get_target_warmth_brief ~130

[Read · free] For a target person, summarize all engagement evidence between them and your collected posts: posts they reacted to, posts they commented on, frequency, recency, reaction kinds, comment text snippets. Computes a v0 warmth score from engagement count, comment signal, and recency. Pure DB read — no LinkedIn pull, no credits charged.

NameTypeReqDescription
days_backinteger–How far back to look at engagements (default 90)
linkedin_urlstring–Target's LinkedIn profile URL
person_idstring–people.id UUID

No output schema declared.

No examples provided.

get_topic_insights ~191

[Read · free] Surface the most-frequent topics in a profile's posts, with engagement context. Returns top N unigrams and (optionally) top N bigrams ranked by post count, each with avg_engagement, vs_baseline, and a sample_post_url. Mirrors the dashboard topics chart, server-side. Pass `scope` (a post_collections.id) to scope the analysis to a collection.

NameTypeReqDescription
bigramsboolean–Also compute and return top bigrams (default true)
date_fromstring–Start date (ISO 8601)
date_tostring–End date (ISO 8601)
ninteger–Max terms per list (default 15)
profile_idstringyesTracked profile ID from list_profiles
scopestring–Optional post_collections.id to scope the analysis

No output schema declared.

No examples provided.

get_usage_history ~107

[Meta · free] Return recent credit_ledger transactions for the authenticated user. Filter by tool name, reason, or date range. Paginated. Free.

NameTypeReqDescription
date_fromstring–Start date (ISO 8601)
date_tostring–End date (ISO 8601)
limitnumber–Max rows to return
reasonstring–Filter by ledger reason
tool_namestring–Filter to a specific MCP tool

No output schema declared.

No examples provided.

linkedin_ad_search ~111

[Acquire · 10 credits] Search the LinkedIn ad library. Useful for tracking competitor ad creative and messaging. Costs 10 credits per call.

NameTypeReqDescription
companystring–Company name or LinkedIn slug to filter ads
keywordsstring–Keyword filter applied to ad creative
refreshboolean–Bypass the cache and re-run the search live (costs 10 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.

No output schema declared.

No examples provided.

linkedin_company_info ~251

[Acquire · 1 credit] Fetch one LinkedIn company (numeric id, name, industry, size, location, website, description). Costs 1 credit per call. Use it to resolve a company to its numeric LinkedIn `id`, which linkedin_people_search (`company`) and linkedin_job_search (`companyId`) take for an exact company match. Look up by `linkedin_url` when you have it: a lookup by `name` returns the best match, which can be a different company with a similar name. The company is saved to `companies`.

NameTypeReqDescription
linkedin_urlstring–LinkedIn company URL (e.g. https://www.linkedin.com/company/acme). Most reliable.
namestring–Company name (e.g. 'Acme Analytics'). Returns the best match; check the returned name and URL.
refreshboolean–Bypass the cache and fetch a fresh copy from LinkedIn (costs 1 credit). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.
universal_namestring–The slug from the company URL (e.g. 'acme' for linkedin.com/company/acme).

No output schema declared.

No examples provided.

linkedin_company_posts ~183

[Acquire · 5 credits/page] Fetch recent posts from a LinkedIn company page. 5 credits per page of 50, up to 250 posts, charged only for pages actually fetched. Results are stored in the post library (source_type='external') and linked to a linkedin_profiles row (profile_type='company').

NameTypeReqDescription
linkedin_urlstringyesLinkedIn company URL (e.g. https://www.linkedin.com/company/acme)
max_postsnumber–Maximum posts to return (1-250). 5 credits per page of 50, charged only for pages actually fetched.
refreshboolean–Bypass the cache and re-fetch from LinkedIn (5 credits per page of 50, charged only for pages actually fetched). Default false: a previously-fetched result is returned free, with how long ago it was…

No output schema declared.

No examples provided.

linkedin_company_search ~246

[Acquire · 5 credits] Search LinkedIn companies. Filter by keywords, industryId, or location. Costs 5 credits per page of 50. Each company comes back with its numeric LinkedIn `id`, which is what linkedin_people_search (`company`) and linkedin_job_search (`companyId`) take for an exact company match.

NameTypeReqDescription
industryIdstring–LinkedIn industry ID (numeric, comma-separated for several). Not an industry name — IDs are LinkedIn's industry codes (V2), listed at https://learn.microsoft.com/en-us/linkedin/shared/references/refe…
keywordsstring–Free-text search (e.g. 'b2b saas analytics')
locationstring–Location filter (e.g. 'San Francisco Bay Area')
pageinteger–Results page, 50 companies per page (default 1). 5 credits per page not already cached.
refreshboolean–Bypass the cache and re-run the search live (costs 5 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.

No output schema declared.

No examples provided.

linkedin_job_search ~211

[Acquire · 5 credits] Search LinkedIn job postings. Useful for tracking hiring signals at target companies. Costs 5 credits per call.

NameTypeReqDescription
companyIdstring–Restrict to a LinkedIn company ID (numeric, e.g. '1441'). Not a name or slug — resolve one first with linkedin_company_info (1 credit) or linkedin_company_search, both of which return the company's i…
keywordsstringyesJob title keywords (e.g. 'staff engineer python')
locationstring–Location filter (e.g. 'San Francisco, CA')
postedLimitstring–Only jobs posted within this window.
refreshboolean–Bypass the cache and re-run the search live (costs 5 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.
sortBystring–Sort order. 'date' is the useful one for hiring signal. Default: relevance.

No output schema declared.

No examples provided.

linkedin_people_search ~376

[Acquire · 5 credits] Search LinkedIn people. Filter by company, title, location, or free-text keywords. Costs 5 credits per page of 25 (map_constellation's built-in lead search is billed at a bundled 1 credit instead, a deliberate discount). Each person comes back with current title, company, company id, start date and location. To list the people at one company, pass its LinkedIn company URL or numeric id as `company` and walk `page` while `truncated` is true. Results are saved to `people` with their current position, so get_outreach_path can route to them (pass a result's `person_id` as `target_person_id`).

NameTypeReqDescription
companystring–Current company. Pass a LinkedIn company URL (https://www.linkedin.com/company/acme) or a numeric LinkedIn company ID (e.g. '1441', the `id` linkedin_company_info and linkedin_company_search return)…
keywordsstring–Free-text search (e.g. 'data engineer fintech')
locationstring–Location filter (e.g. 'New York')
pageinteger–Results page, 25 people per page (default 1). 5 credits per page not already cached.
refreshboolean–Bypass the cache and re-run the search live (costs 5 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.
titlestring–Current title filter (e.g. 'Director'). Comma-separate several (e.g. 'SDR,Account Executive').

No output schema declared.

No examples provided.

linkedin_post_comments ~225

[Acquire · 1 credit/page] Fetch the people who commented on a single LinkedIn post (and their comment text), including replies to comments. Costs 1 credit per page of up to 100 comments, walking up to max_pages pages (default 10), so at most max_pages credits; cached pages are free. The output's fetched / total_available / truncated fields say when the post had more comments than were fetched. Each comment and reply is persisted to post_engagements with the commenter and full comment text.

NameTypeReqDescription
max_pagesinteger–Max pages of up to 100 comments to fetch (1-20, default 10). Each page costs 1 credit.
post_urlstringyesPublic LinkedIn post URL (e.g. https://www.linkedin.com/feed/update/urn:li:activity:1234)
refreshboolean–Bypass the cache and re-fetch from LinkedIn (costs 1 credit per page). Default false: previously-fetched pages are returned free, with how long ago they were retrieved.

No output schema declared.

No examples provided.

linkedin_post_reactions ~230

[Acquire · 1 credit/page] Fetch the people who reacted to a single LinkedIn post. Costs 1 credit per page of up to 100 reactions, walking up to max_pages pages (default 10), so at most max_pages credits; cached pages are free. The output's fetched / total_available / truncated fields say when the post had more reactions than were fetched. Engagers (with reaction kind) are persisted to the post_engagements graph so subsequent queries about who-engages-with-whom are SQL, not API calls.

NameTypeReqDescription
max_pagesinteger–Max pages of up to 100 reactions to fetch (1-20, default 10). Each page costs 1 credit.
post_urlstringyesPublic LinkedIn post URL (e.g. https://www.linkedin.com/feed/update/urn:li:activity:1234)
refreshboolean–Bypass the cache and re-fetch from LinkedIn (costs 1 credit per page). Default false: previously-fetched pages are returned free, with how long ago they were retrieved.

No output schema declared.

No examples provided.

linkedin_post_search ~139

[Acquire · 5 credits] Search LinkedIn posts by keyword. Costs 5 credits per call. Returns a single page of matching posts, each with a post_id (stored as a stub, no extra credit) you can pass to get_post_set_engagers to pull who engaged; _meta.next_step has that call ready.

NameTypeReqDescription
filtersobject–Optional filters
querystringyesSearch query / keywords
refreshboolean–Bypass the cache and re-run the search live (costs 5 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.

No output schema declared.

No examples provided.

linkedin_profile_comments ~106

[Acquire · 5 credits] Fetch the recent posts a LinkedIn person has commented on. Useful for inferring interests and conversation partners. Costs 5 credits per call.

NameTypeReqDescription
linkedin_urlstringyesLinkedIn profile URL of the person whose comments you want
refreshboolean–Bypass the cache and re-fetch from LinkedIn (costs 5 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.

No output schema declared.

No examples provided.

linkedin_profile_info ~149

[Acquire · 5 credits] Fetch a LinkedIn person profile (headline, current role, work history, education, location). Costs 5 credits per call. Results are upserted into `people` (structured fields) and `linkedin_profiles` (so profile-brief renders) — same enrichment side-effect as the other linkedin_profile_* tools.

NameTypeReqDescription
linkedin_urlstringyesLinkedIn profile URL (e.g. https://www.linkedin.com/in/username)
refreshboolean–Bypass the cache and fetch a fresh copy from LinkedIn (costs 5 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.

No output schema declared.

No examples provided.

linkedin_profile_posts ~187

[Acquire · 5 credits/page] Fetch recent posts from a LinkedIn person profile. 5 credits per page of 50, up to 250 posts, charged only for pages actually fetched. Results are stored in the post library (source_type='external') and linked to a linkedin_profiles row so profile-brief can render research-only prospects.

NameTypeReqDescription
linkedin_urlstringyesLinkedIn profile URL (e.g. https://www.linkedin.com/in/username)
max_postsnumber–Maximum posts to return (1-250). 5 credits per page of 50, charged only for pages actually fetched.
refreshboolean–Bypass the cache and re-fetch from LinkedIn (5 credits per page of 50, charged only for pages actually fetched). Default false: a previously-fetched result is returned free, with how long ago it was…

No output schema declared.

No examples provided.

linkedin_profile_reactions ~104

[Acquire · 5 credits] Fetch the recent posts a LinkedIn person has reacted to. Useful for inferring interests. Costs 5 credits per call.

NameTypeReqDescription
linkedin_urlstringyesLinkedIn profile URL of the person whose reactions you want
refreshboolean–Bypass the cache and re-fetch from LinkedIn (costs 5 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.

No output schema declared.

No examples provided.

list_collections ~64

[Read · free] List all post collections for the authenticated user, with member counts. Includes manual collections, smart collections (predicate-based), and auto_stream collections (system-managed). Free — costs 0 credits.

NameTypeReqDescription
typestring–Optional filter by collection type

No output schema declared.

No examples provided.

list_profiles ~32

[Read · free] List all tracked LinkedIn profiles for the authenticated user. Returns profile IDs needed by other tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_segment_templates ~85

[Meta · free] List available smart-segment templates. Pass a template id to create_segment to pre-fill its `config` predicate without crafting one from scratch. Each template's description states exactly what its config matches; like every smart segment, it only matches people connected to you (engagers on your visible posts and people in your campaigns). Free — costs 0 credits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_segments ~78

[Read · free] List all audience segments for the authenticated user, with member counts. Audience segments are named groups of people (e.g. 'ICP — VPs of Marketing', 'Champions'). Free — costs 0 credits.

NameTypeReqDescription
typestring–Optional filter by segment type ('manual', 'smart', or 'auto_stream')

No output schema declared.

No examples provided.

Install

How do I install the Flux LinkedIn MCP server?

Flux LinkedIn MCP is a hosted endpoint at https://www.fluxgraph.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.fluxgraph.app

# add to Claude Code
claude mcp add --transport http app-fluxgraph-linkedin 'https://www.fluxgraph.app/mcp'
Common questions

What is the Flux LinkedIn MCP server?

Flux LinkedIn MCP is listed in the public MCP registry as app.fluxgraph/linkedin. LinkedIn intelligence: post analytics and research for public profiles and company pages. This page covers its hosted endpoint (https://www.fluxgraph.app/mcp).

Is the Flux LinkedIn MCP server safe to use?

Flux LinkedIn MCP scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Flux LinkedIn MCP server expose?

Flux LinkedIn MCP exposes 72 tools: list_profiles, preview_profile, preview_posting_insights, preview_search_posts, claim_preview, and 67 more. Their descriptions and schemas cost roughly 13,766 tokens of context every time the server is loaded.

Does the Flux LinkedIn MCP server require authentication?

Yes. Flux LinkedIn MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Flux LinkedIn MCP server still maintained?

Flux LinkedIn MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Flux LinkedIn MCP server?

VerifyMCP ran 13 checks on Flux LinkedIn MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.