Local MCP server for authenticated LinkedIn member post snapshots
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"flin-linkedin-posts-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# flin-linkedin-posts-mcp `flin-linkedin-posts-mcp` is a local MCP server for reading and analyzing the authenticated member's own LinkedIn post/share data. It uses LinkedIn member OAuth login and the Member Data Portability API. Each user runs the MCP locally, signs into their own LinkedIn account in the system browser, and stores their token on their own machine. The MCP supports two login flows: - Regular 3-legged OAuth with a client secret. This is the recommended local setup for most LinkedIn Developer apps. - Native OAuth PKCE. This does not require a client secret, but LinkedIn must explicitly enable the Native PKCE protocol for your app. ## Important Access Requirement This MCP does not bypass LinkedIn API approval. Each user should create their own LinkedIn Developer app with access to Member Data Portability API (Member) and the `r_dma_portability_self_serve` permission. Without that product/scope, LinkedIn returns `403 ACCESS_DENIED` for `memberSnapshotData`. Native PKCE is a separate LinkedIn app capability. If LinkedIn shows `Not enough permissions to access Native PKCE protocol`, use the regular 3-legged OAuth setup below or ask LinkedIn to enable Native PKCE for the app. Relevant LinkedIn docs: - 3-legged OAuth: https://learn.microsoft.com/en-us/linkedin/shared/authentication/authorization-code-flow - Native OAuth PKCE: https://learn.microsoft.com/en-us/linkedin/shared/authentication/authorization-code-flow-native - Member Snapshot API: https://learn.microsoft.com/en-us/linkedin/dma/member-data-portability/shared/member-snapshot-api - Snapshot domains: https://learn.microsoft.com/en-us/linkedin/dma/member-data-portability/shared/snapshot-domain - API access overview: https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access ## Features - Browser-based LinkedIn login with regular OAuth or native PKCE - Local token storage outside the repository - Auth status and logout tools - Snapshot domain count/debug tool - Authent…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.