
Security News
Ruby's Bundler 4.0.18 Extends Cooldown to bundle lock and bundle cache
The supply chain control that delays freshly published gems now covers lockfile generation and gem vendoring in Ruby projects.
@attestry/mcp-server
Advanced tools
MCP server for Attestry — the cryptographically-verifiable AI compliance platform
MCP (Model Context Protocol) server for Attestry — the cryptographically-verifiable AI compliance platform. Lets AI assistants (Claude, Cursor, Windsurf) interact directly with your Attestry compliance data.
Create an API key in the Attestry app under Settings → Integrations → API Keys. The key has full access to the Attestry API — there are no scopes to configure.
No manual install is needed — the configs below launch the server on demand with npx. Just set your API key in the env block.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"attestry": {
"command": "npx",
"args": ["-y", "@attestry/mcp-server"],
"env": {
"ATTESTRY_API_KEY": "your-api-key-here"
}
}
}
}
Add to your project's .mcp.json:
{
"mcpServers": {
"attestry": {
"command": "npx",
"args": ["-y", "@attestry/mcp-server"],
"env": {
"ATTESTRY_API_KEY": "your-api-key-here"
}
}
}
}
Edit .cursor/mcp.json in your project root:
{
"mcpServers": {
"attestry": {
"command": "npx",
"args": ["-y", "@attestry/mcp-server"],
"env": {
"ATTESTRY_API_KEY": "your-api-key-here"
}
}
}
}
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"attestry": {
"command": "npx",
"args": ["-y", "@attestry/mcp-server"],
"env": {
"ATTESTRY_API_KEY": "your-api-key-here"
}
}
}
}
| Variable | Required | Default | Description |
|---|---|---|---|
ATTESTRY_API_KEY | Yes | — | Your Attestry API key (full access) |
ATTESTRY_API_URL | No | https://attestry.app | Attestry API base URL (SaaS control plane). The default is correct for the hosted product; override only for self-hosted/staging. |
attestry_check_complianceCheck an AI system's compliance status against regulatory frameworks.
Input:
systemId (string, required) — UUID of the AI systemframeworks (string[], optional) — Frameworks to check (e.g., ["eu_ai_act", "colorado_ai_act"])Output: Pass/fail status, score, compliance issues, active attestation count, last-assessed + checked timestamps, and recommendations.
attestry_classify_systemClassify an AI system's risk level across all applicable frameworks.
Input:
systemId (string, required) — UUID of the AI systemOutput: Overall risk level, per-framework classifications with rationale, applicable frameworks, and Colorado affirmative-defense status.
attestry_list_systemsList all registered AI systems for your organization.
Input: None
Output: Total count plus, for each system: ID, name, status, overall risk level, applicable frameworks, intended use, and deployment geography.
attestry_get_assessmentGet the latest compliance assessment summary for an AI system.
Input:
systemId (string, required) — UUID of the AI systemOutput: Compliance status, score, framework coverage (applicable / assessed / percentage), active attestations, last-assessed timestamp, and recommendations.
attestry_list_changesGet recent regulatory changes affecting AI compliance.
Input:
severity (string, optional) — Filter: critical, high, medium, lowframework (string, optional) — Filter by frameworklimit (number, optional) — Number of results (default: 10, max: 50)Output: Regulatory changes with titles, summaries, framework, severity, status, published + effective dates, and source URLs.
attestry_generate_documentGenerate a compliance document for an AI system.
Input:
systemId (string, required) — UUID of the AI systemdocType (string, required) — One of:
eu_technical_documentation — EU AI Act Article 11colorado_impact_assessment — SB 24-205risk_management_plan — NIST AI RMFmodel_card — Transparency documentationpost_market_monitoring_plan — EU AI Act Article 72consumer_disclosure — Colorado consumer noticenist_ai_rmf_profile — NIST framework profilecustom_framework_report — Custom frameworkassessmentId (string, optional) — Include assessment datauseAI (boolean, optional) — Use AI for narrative generation (default false; consumes AI credits)Output: Document ID, type, framework, generation timestamp, and a signed download URL + token (expires in ~72 hours).
| URI | Description |
|---|---|
attestry://systems | List of AI systems with risk classifications |
attestry://changes | Recent regulatory changes |
attestry://status | Compliance dashboard summary |
Once configured, you can ask your AI assistant:
Clone the repository, then from mcp-server/:
npm install
npm run dev # Watch mode
npm run build # Production build
npm start # Run the server
MIT © Attestry
FAQs
MCP server for Attestry — the cryptographically-verifiable AI compliance platform
We found that @attestry/mcp-server demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
The supply chain control that delays freshly published gems now covers lockfile generation and gem vendoring in Ruby projects.

Security News
During a UK cyber test, a Mythos 5 agent used sockpuppets, social engineering, and prompt injection to try to get a maintainer to merge malware.

Company News
Socket is now in the AWS Security Hub Extended plan. Adopt it through AWS, apply committed spend, and block malicious open source packages.