com.mambabuilt/mcp-linkedin-company-presence-mapper
com-mambabuilt-mcp-linkedin-company-presence-mapper declares 1 capabilities across 1 tools, with 1 critical issue.
Issues
1 of 1 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.
1 of 1 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.
1 of 1 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.
1 tool can modify data and declares no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
map_linkedin_company_presence | write |
assumed |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-13 | 2 | tools/list answered by the npm package @mambalabsdev/mcp-linkedin-company-presence-mapper@1.2.1 (published to npm as @mambalabsdev/mcp-linkedin-company-presence-mapper, listed in the official MCP registry as com.mambabuilt/mcp-linkedin-company-presence-mapper 1.2.1), run in an isolated container with no network access and placeholder credentials |
| 2026-10-11 | 2 | tools/list answered by the npm package @mambalabsdev/mcp-linkedin-company-presence-mapper@1.1.1 (published to npm as @mambalabsdev/mcp-linkedin-company-presence-mapper, listed in the official MCP registry as com.mambabuilt/mcp-linkedin-company-presence-mapper 1.1.1), run in an isolated container with no network access and placeholder credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.