LinkedIn Profile, Company & B2B Enrichment API MCP Server
com-linkedindataapi-mcp-server declares 7 capabilities across 7 tools, with 1 critical issue. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
Issues
7 of 7 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
7 of 7 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
7 of 7 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
7 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
b2b_enrich_person | read |
declared |
b2b_enrich_company | read |
declared |
b2b_search_decision_makers | read |
declared |
b2b_get_person_posts | read |
declared |
b2b_get_company_posts | read |
declared |
b2b_search_posts | read |
declared |
b2b_search_hiring_signals | read |
declared |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.