polaris-audit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POLARIS_API_KEY | No | Bearer token for authenticated endpoints | |
| POLARIS_API_BASE | No | Override the API base URL (useful for self-hosting) | https://polarisaudit.com/api/scanner |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_urlA | Submit a website URL for a free Polaris Audit scan. Returns a scan token you can use with get_scan_result to retrieve the completed report. The scan typically completes within 30–60 seconds. |
| get_scan_resultA | Retrieve the results of a previously submitted scan using the scan token returned by audit_url. If the scan is still running, poll again after a few seconds. |
| get_public_resultA | Fetch a publicly shared Polaris Audit report by its UUID. Returns scores for privacy, security, accessibility, and performance plus a summary of key findings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: audit_url initiates a scan, get_scan_result retrieves results for a submitted scan, and get_public_result fetches publicly shared reports by UUID. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern (audit_url, get_public_result, get_scan_result) using snake_case. The naming is predictable and readable, with no deviations in style or convention.
With only 3 tools, the server feels thin for an audit domain that might benefit from additional operations like listing scans, deleting results, or updating reports. However, the core workflow (submit, retrieve, fetch public) is covered, making it borderline but functional.
The tool set covers the essential lifecycle of submitting scans and retrieving results, including public reports. Minor gaps exist, such as no ability to list or manage scans, but agents can work around this by tracking tokens externally.