REPORT 01M7BNA68E8M579MXFW45H3F22 · checks-v2
Agent Intercom MCP server: automated checks
What HostedMCP checked on 13 Nov 2026, 23:54 UTC for agent-intercom 0.2.5. Every result links to the public source it came from, so you can check it yourself.
Passed HostedMCP checks v2
100/100
8 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 13 Nov 2026, 23:54 UTC
- Commit
- —
- Package
- npm · 0.2.5
- Methodology
- checks-v2
Origin
30 / 30 points- PassSource repository linked and reachable10 pts
iambashar/agent-intercom is public and reachable
github.com/iambashar/agent-intercom ↗ - PassPackage names this repository as its source5 pts
agent-intercom names iambashar/agent-intercom as source
npmjs.com/package/agent-intercom ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for agent-intercom
npmjs.com/package/agent-intercom/v/0.2.5#provenance ↗ - Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-10-18
github.com/iambashar/agent-intercom ↗ - Not checkedOpenSSF Scorecard15 pts
Supply chain
25 / 25 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from agent-intercom
- PassNo critical advisory in the package or its dependencies15 pts
1 resolved dependencies checked; no critical advisory
osv.dev ↗
Tool safety
15 / 15 points- PassNo hidden instructions to the model15 pts
0 tool descriptions and the README read; no override phrases, credential paths or hidden characters
- Not checkedDestructive tools are labelled5 pts
Endpoint
not checked- Not checkedRemote endpoint answers the MCP handshake5 pts
What these checks do not cover
- The server's code is not run and its logic is not audited.
- Results describe the state on the date above and agent-intercom 0.2.5; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.