plurity-audit-mcp
MCP server for the Plurity GEO Audit API. Lets any MCP-compatible AI client (Claude Desktop, Cursor, etc.) submit websites for AI-readiness audits and retrieve the full analysis — score, structured Q&A pairs, token-waste insights — directly inside the conversation.
Setup
1. Get an API key
Sign up at audit.plurity.ai, then go to Settings → API Keys and create a key. Copy the plt_... key — it is only shown once.
2. Add to your MCP client
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"plurity-audit": {
"command": "uvx",
"args": ["plurity-audit-mcp"],
"env": {
"PLURITY_API_KEY": "plt_your_key_here"
}
}
}
}
Restart Claude Desktop after saving.
Other MCP clients
Same config shape — set PLURITY_API_KEY in the env block and use uvx plurity-audit-mcp as the command.
Requires
uv— install withbrew install uvorcurl -LsSf https://astral.sh/uv/install.sh | sh.
Available tools
| Tool | Description |
|---|---|
submit_scan(url) |
Queue a URL for GEO audit. Returns scan ID and initial status immediately. |
get_scan(scan_id) |
Get the current status and results of a scan by ID. |
get_scan_by_url(url) |
Look up the latest scan result for a URL without knowing the scan ID. |
audit(url, timeout_seconds?) |
Submit and block until complete (polls every 5 s, default 5 min timeout). Returns full results. |
Scan statuses: pending → crawling → analyzing → complete (or failed).
Environment variables
| Variable | Required | Description |
|---|---|---|
PLURITY_API_KEY |
Yes | Your Plurity API key (plt_...) |
PLURITY_BASE_URL |
No | Override API base URL (default: https://audit.plurity.ai) |
1 maintainer
Metadata
1 maintainer
Release files for plurity-audit-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| plurity_audit_mcp-0.1.0.tar.gz | 7.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| plurity_audit_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.6 kB
Release files / plurity_audit_mcp-0.1.0.tar.gz
| Download URL | plurity_audit_mcp-0.1.0.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0d8821971dd26fa306e2875af6ee494c9ad9b2a0fc6aef4798fb1c4c75e0339c
|
|
BLAKE2b-256 checksum How to use checksums |
01a2ac14e3c0615b265a088c6d80cc035eb032d95c2c4cabbd093d35b961b3e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 10, 2026.
Transparency logRelease files / plurity_audit_mcp-0.1.0-py3-none-any.whl
| Download URL | plurity_audit_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5e04a45ab53bd6c795dfa2de5ccd67044c1fd75bc19fcdf12a14a83a6690ca1a
|
|
BLAKE2b-256 checksum How to use checksums |
3379ea01dea56e3838e2f98dbd15fcc6f3e96d7df798bc1b9cb0676419825e94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 10, 2026.
Transparency logSecurity for plurity-audit-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for plurity_audit_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 10, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
