
Hares — MCP security scanner
io.github.alialrikabi313Published by GitHub account alialrikabi313v0.1.0Updated Oct 24, 2026
Multi-layer security scanner for MCP servers and agent skills (injection, exfiltration)
Overview
A local MCP server that runs a multi-layer security scan of MCP servers and agent skills for injection and data-exfiltration risks.
- What you can do
- Scans MCP servers and agent skills for security problems, described as a multi-layer check covering injection and exfiltration risks. Runs as a local process started with npx and exposes its scanning capability to the assistant over stdio. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Useful when you want an assistant to vet an MCP server or agent skill before installing or trusting it, for example to check third-party components for prompt-injection or data-exfiltration patterns.
- Requirements
- Runs locally as a process on the user's machine via npx from the npm package @alihashim313/hares, so Node.js and npm are needed. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Hares — MCP security scanner in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.