We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/russellbrenner/auslaw-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
# Security Policy
## Supported Versions
| Version | Supported |
| ------- | ------------------ |
| 0.1.x | :white_check_mark: |
## Reporting a Vulnerability
**Please do not open public issues for security vulnerabilities.**
To report a security vulnerability, please email: russell@lawquarter.com
We will respond within 48 hours and provide updates as the issue is addressed.
### What to Include
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
## Security Considerations
This tool:
- Makes HTTP requests to AustLII and jade.io
- Does not store user data
- Does not require authentication
- Runs locally as an MCP server
- Uses OCR for PDF processing (requires Tesseract)
### For Users
- Keep dependencies updated (`npm audit fix`)
- Review source code before running
- Use in trusted environments only
- Be aware of rate limiting when querying public APIs
### For Contributors
- Run `npm audit` before submitting PRs
- Follow secure coding practices
- Report vulnerabilities privately
- Test security-related changes thoroughly
## Known Security Considerations
### Dependency Vulnerabilities
We monitor dependencies for vulnerabilities using:
- `npm audit`
- Dependabot alerts
- Regular dependency updates
### External API Calls
This tool makes requests to:
- AustLII (public legal database)
- jade.io (if user provides URLs)
Users should:
- Respect terms of service of these platforms
- Implement rate limiting in production use
- Not expose this tool to untrusted input sources
### OCR Processing
When processing PDFs with OCR:
- Temporary files are created in system temp directory
- Files are cleaned up after processing
- Tesseract runs locally (no data sent externally)
## Security Updates
Security updates are released as soon as possible after a vulnerability is confirmed. Users should:
- Subscribe to GitHub releases
- Monitor npm advisories
- Update promptly when security releases are published
## Contact
For security-related questions: russell@lawquarter.com
For general questions: Open a GitHub issue