-
-
Notifications
You must be signed in to change notification settings - Fork 253
new active script to detect open mcp servers #499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Great job! No new security vulnerabilities introduced in this pull requestUse @Checkmarx to reach out to us for assistance. Just send a PR comment with Examples: |
|
@bananabr thanks for this PR! Am I right in thinking that the paths you're checking should be absolute, ie Do you have any links to example MCP servers which this rule detects so we can test it? The build is failing, but it looks like you can fix that with |
|
The file name and code link don't match. They should also follow the naming guidance: https://github.com/zaproxy/community-scripts/blob/main/CONTRIBUTING.md#naming-scripts |
|
To address the DCO requirement you'll need to sign-off the commit(s):
If it makes life easier feel free to squash it all into one commit. |
…cp servers Signed-off-by: Daniel Santos <[email protected]>
6c5ad1b to
d2c52e2
Compare
For zaproxy/community-scripts#499. Signed-off-by: Daniel Santos <[email protected]>
Signed-off-by: Daniel Santos <[email protected]>
I think there is merit in both. It becomes a matter of performance versus completeness in my opinion. Most cases I found in the wild were under the server's root directory though. Here is a sample of an open MCP server you can use for testing: https://gist.github.com/bananabr/52570a3d6c23f83c2dbd0690afc28cb4 |

This script detects potentially exposed MCP servers by sending MCP initialization requests