MCP servers observed by Lowdown
app.fluxgraph/linkedin MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 71 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.fluxgraph/linkedin
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.fluxgraph/linkedin?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-17: input or output schemas changed, descriptions changed, tool names changed; tool count 67 → 71
- 2026-11-14: input or output schemas changed, descriptions changed
What tools does it list?
71 tools on 2026-11-17:
add_campaign_accountsadd_to_collectionadd_to_segmentclaim_previewcreate_campaigncreate_collectioncreate_segmentcreate_streamdelete_streamenrich_peoplefind_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_infolinkedin_company_postslinkedin_company_searchlinkedin_job_searchlinkedin_people_searchlinkedin_post_commentslinkedin_post_reactionslinkedin_post_searchlinkedin_profile_commentslinkedin_profile_infolinkedin_profile_postslinkedin_profile_reactionslist_collectionslist_profileslist_segment_templateslist_segmentslist_streamslog_outcomemap_constellationpause_streampreview_posting_insightspreview_profilepreview_search_postsremove_from_collectionremove_from_segmentresolve_collectionresolve_companyresolve_peopleresolve_segmentresume_streamrun_stream_nowsave_postscore_connectionsscore_draftsearch_postssuggest_anglestraverse_graphtraverse_graph_help
MCP Registry declaration
- Registry name:
app.fluxgraph/linkedin - Declared version: 1.0.1
- Status: active
- Declared hosts:
www.fluxgraph.app
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:app.fluxgraph/linkedin", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.fluxgraph/linkedin?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).