Clean scanStatic scanned
Lets your agent work with your Salesforce orgs, from Aura to LWC migration to code analysis.
171k installs/moApache-2.0
Linkedin MCP
gtm-api · MCP server
Connects your AI client to gtm-api's hosted LinkedIn server, where every tool runs, so nothing is executed locally. The server gives an agent three tools for listing toolsets and calling more than 160 typed actions covering messaging, connection requests, content, enrichment, search and account health. The hosted side applies warm-up, daily limits and a preview-then-confirm step on outward actions. Sign in with OAuth in a browser, or use an API key from the gtm-api app.
Written by ooruby from the README of @gtm-api/linkedin-mcp 1.3.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
LinkedIn search, connection and messaging work can be handed to your agent through one hosted server, with a confirmation step before outward actions.
What you could do with it
- Ask your agent to list the available toolsets, then call a messaging or enrichment action.
- Have your agent prepare a connection request and review the preview before it is sent.
- Use an API key on a headless machine or in CI, where a browser sign-in is not possible.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (bin/cli.js:28)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
- Data handling disclosed
- finding
- no statement of what it reads, writes or sends (README.md)
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Managed LinkedIn MCP server for AI agents. Stdio launcher for the hosted gtm-api endpoint: search, connect, message and enrich on LinkedIn accounts you own. 160+ typed actions behind three MCP tools.
Compare with
- Linkedin MCPside by side
- MCP Domain To Linkedin Url Resolverside by side
- MCP Linkedin Post Engager Captureside by side
How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 1.3.1, the file with digest sha512-5AuA4AueK9BIZ8IsGBLPJqzyhsoc9Vx1ISstrI1BcgX3VPr4biXwnm7c/Tg95KhR5fXzI9tv8iyEIo+Ha39aAQ==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- No auth declared. Its hosted endpoint, as the official MCP registry lists it, does not say it asks for a key. That is what the listing declares, not a finding that it has no protection.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"gtm-api-linkedin-mcp": {
"command": "npx",
"args": [
"-y",
"@gtm-api/linkedin-mcp@1.3.1"
]
}
}
}Or run it directly.
npx -y @gtm-api/linkedin-mcp@1.3.1Pinned to 1.3.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @gtm-api/linkedin-mcp
- Version read
- 1.3.1
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/gtm-api-linkedin-mcp)About this listing
- Kind
- MCP server
- Category
- Sales & CRM
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-05
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.