Fix critical dependency vulnerability and update package test

[IgorWnek]

Issue

Vulnerability

I wanted to run the MCP server locally. Once I installed packages I saw the information about the critical severity vulnerability:

npm install

added 155 packages, and audited 156 packages in 996ms

36 packages are looking for funding
  run `npm fund` for details

1 critical severity vulnerability

Fixing tests

I've run the tests and they failed, but they seems outdated. I've fixed the single place so the tests are correctly reflecting the code.

Solution

I've run the npm's audit to fix that:

npm audit fix

changed 1 package, and audited 156 packages in 955ms

36 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

NPM also automatically fixed to package name in the correct one.

This upgrade updated the form-data to 4.0.4.

Regarding the tests, I've just updated the path to the tools index file.

Please let me know what do you think.

Tests

After those fixes I've run commands:

npm run build

npm run test

npm start

✅ Tests went correct
✅ Then I've configured this locally running MCP server in Zed and tested if everything works fine.

[github-actions]

Thanks for the pr,it's now under review

[IgorWnek]

@Jpisnice what's wrong with this Labeler? I didn't change anything in GH Actions or so.
What do you think about those changes?

[Jpisnice]

@Jpisnice what's wrong with this Labeler? I didn't change anything in GH Actions or so. What do you think about those changes?

hey @IgorWnek ,thanks for the changes.really appreciate it