Skip to main content

attestari-mcp

Attestari's verdict on an npm or PyPI package version, over the Model Context Protocol. The answer is the Attestari lookup API's: the grade, the decision, the confirmed findings by reason code and place, and the methodology version and document hash the decision cites. "Not examined" is its own answer and is never a sign that a package is safe.

Every lookup needs an Attestari API key (the Developer tier and above, https://attestari.ai/pricing#line-2) and is counted as one lookup, as through the API. What is sent is the ecosystem, the package name and the version, and nothing else.

Run it locally

ATTESTARI_API_KEY=att_live_... uvx attestari-mcp

It speaks MCP over standard input and output and opens no port. In an MCP client's configuration:

{
  "mcpServers": {
    "attestari": {
      "command": "uvx",
      "args": ["attestari-mcp"],
      "env": { "ATTESTARI_API_KEY": "att_live_..." }
    }
  }
}

ATTESTARI_API_URL changes the lookup API's address (default https://api.attestari.ai).

Or remotely

The same server runs at https://mcp.attestari.ai/mcp (Streamable HTTP). A client sends its key (Authorization: Bearer att_live_...), or connects by OAuth: a client that supports MCP authorization finds Attestari's authorization server from the server's protected resource metadata, and an owner or an admin of the organization grants it at app.attestari.ai. A connection is listed, and revoked, beside the organization's keys, and counts as one of them. The access token stays with the server: the lookup API is told which connection a lookup is for, and counts it as it counts a key's.

Tools

  • lookup_package: one package (ecosystem: npm or pypi; name; version, or none for the latest version examined).
  • lookup_packages: up to 20 packages at once, each counted as one lookup.

Both only read. Each answer says its outcome: graded, not_gradeable (examined, no opinion given), not_a_server (out of scope), not_examined, under_re_examination, refused (the key, the plan or a limit) or unavailable.

What the answer carries from a package

Its name, its version, and the file paths of its findings and capabilities with their line numbers. No excerpt of a package's code or text is passed on: text written by a package's publisher never reaches the agent through this server.

Licence

MIT.

Metadata

Release files for attestari-mcp 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for attestari-mcp 0.2.0
File Size Uploaded Provenance Actions
attestari_mcp-0.2.0.tar.gz 28.0 kB With provenance Details for attestari_mcp-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for attestari-mcp 0.2.0
File Interpreter ABI Platform Actions
attestari_mcp-0.2.0-py3-none-any.whl Python 3 none any Details for attestari_mcp-0.2.0-py3-none-any.whl

Total release size: 47.6 kB

Release files / attestari_mcp-0.2.0.tar.gz

Download URL attestari_mcp-0.2.0.tar.gz
Size 28.0 kB
Tags Source
SHA-256 checksum
How to use checksums
9ca99ad966e7ccc8405c137373b9846aebb34dbf24cd4196f6b6f50d6a7f3a98
BLAKE2b-256 checksum
How to use checksums
0454a351f327bc2719d587e707ed80bb2f7f4ae84feac2e74c3e5e9aa9b06695
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 6, 2026.

Transparency log

Release files / attestari_mcp-0.2.0-py3-none-any.whl

Download URL attestari_mcp-0.2.0-py3-none-any.whl
Size 19.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1843d148fba35fde75ec657163e90742b48648c3d37f77a68c05f5d09f7f3537
BLAKE2b-256 checksum
How to use checksums
c553572f249baf6b2177326a55695ce93b0d66d635b69f0abc24789ee631f16d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 6, 2026.

Transparency log

Security for attestari-mcp 0.2.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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for attestari_mcp-0.2.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 Oct 6, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page