Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.veriswarm/veriswarm-mcp

PYPI · VERISWARM-MCP

VeriSwarm MCP Server — Trust infrastructure for AI agents via Model Context Protocol

Available components

+11 this week 61 Trust /100

Last scanned (8 minutes ago)

Scores higher than 58% of PyPI servers

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to veriswarm/veriswarm-sdk). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 6522 tokens (~63/item across 102 items; 102 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "kill_agent" implies "kill" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 102 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 +11
    • Malware scan: pass → unverified ▼ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: 0 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
    • Package version: 0.4.0 → 0.6.0 functional
  • 2 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 1 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 26 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 20 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 19 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/veriswarm-mcp@0.6.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo veriswarm/veriswarm-sdk
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/veriswarm/veriswarm-sdk/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.6.0
Rekor log index 3678348090
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:c13bde26ac0af8708cc1cae20a04c55f605bf6650f407a02394211b58029b940

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 102 exposed · ~6,522 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
activate_workflow ~41

Activate a workflow so its triggers (schedule/event/webhook) start firing. workflow_id: the workflow ID to activate

NameTypeReqDescription
workflow_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

approve_approval ~61

Approve a pending approval request. Requires an account-session token (operator role); api-key-only callers get a 401. `reason` is captured in the audit ledger.

NameTypeReqDescription
approval_idstringyes–
reasonstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

cancel_a2a_task ~77

Cancel an in-flight A2A task. agent_id: the receiving agent (`agt_*`). task_id: the task id to cancel (`a2a_*`). Returns the updated task state. No-op if the task already terminated.

NameTypeReqDescription
agent_idstringyes–
task_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

cancel_workflow_execution ~41

Cancel a running or paused workflow execution. execution_id: the execution ID to cancel (starts with wfx_)

NameTypeReqDescription
execution_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

check_decision ~71

Check if an agent is allowed to perform an action. Returns allow, review, or deny. Uses x-api-key auth. The agent must belong to the tenant that owns the API key.

NameTypeReqDescription
action_typestringyes–
agent_idstringyes–
resource_typestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

check_delegation ~75

Check active delegation grants for an agent. Requires session auth (x-account-access-token). Not available with API key only. agent_id: the agent whose delegations to check scope: optional scope filter, e.g. read, write, admin

NameTypeReqDescription
agent_idstringyes–
scopestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

check_tool_allowed ~47

Check whether a tool is permitted under active Guard policies for this workspace. Requires session auth (x-account-access-token). Not available with API key only.

NameTypeReqDescription
tool_namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

check_tool_permission ~80

Check if an agent has trust-gated permission to use a tool. agent_id: the agent requesting the tool tool_name: name of the tool to check (e.g., 'process_refund') Returns whether the tool is allowed based on the agent's trust score.

NameTypeReqDescription
agent_idstringyes–
tool_namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

check_trust ~32

Get an agent's current trust scores, policy tier, and risk band.

NameTypeReqDescription
agent_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

create_approval ~118

Submit a new approval request to the operator queue. agent_id: optional VeriSwarm agent id (`agt_*`); omit for system-initiated reviews. requested_action_json: JSON-encoded dict describing the action being approved (free-form per-tenant schema). ttl_seconds: how long the request stays pending before expiring. Server enforces 60 ≤ ttl_seconds ≤ 30 days.

NameTypeReqDescription
agent_idstring––
requested_action_jsonstring––
ttl_secondsinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

create_workflow ~90

Create a new Cortex Workflow from a JSON definition. name: display name for the workflow slug: URL-safe identifier (lowercase, hyphens ok) definition: the full workflow definition as a JSON string description: optional description of what the workflow does

NameTypeReqDescription
definitionstringyes–
descriptionstring––
namestringyes–
slugstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

deactivate_workflow ~35

Deactivate a workflow, stopping all triggers. workflow_id: the workflow ID to deactivate

NameTypeReqDescription
workflow_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

deploy_template ~53

Deploy a workflow template as a new workflow in your workspace. template_id: the template ID (e.g., "builtin:content-pipeline-v2" or a custom template ID)

NameTypeReqDescription
template_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

explain_score ~29

Get a human-readable explanation of an agent's current trust scores.

NameTypeReqDescription
agent_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

export_vault ~45

Create a Vault export job. Returns the job ID and status. export_type: format for the export — json or csv (default json)

NameTypeReqDescription
export_typestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

forget_contact ~123

GDPR: Delete all data associated with a contact. Requires session auth (x-account-access-token). Not available with API key only. contact_identifier: email, phone, or contact ID to purge contact_type: 'email', 'phone', or 'contact_id' dry_run: if True, shows what would be deleted without deleting Purges from PII tokens, events, and KB chunks. Generates a cryptographic deletion proof stored in Vault.

NameTypeReqDescription
contact_identifierstringyes–
contact_typestring––
dry_runboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_a2a_agent_card ~109

Get an A2A agent card for the given agent. The card is an A2A-compatible JSON document that includes the `x-veriswarm-trust` extension (current trust score + tier), and — when keys are provisioned — the `x-veriswarm-transport` extension carrying the agent's Ed25519 public key for inter-agent message signing. agent_id: VeriSwarm agent id (`agt_*`).

NameTypeReqDescription
agent_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_a2a_history ~67

Get agent-to-agent interaction history. agent_id: the agent to query role: 'requesting' (outbound) or 'receiving' (inbound)

NameTypeReqDescription
agent_idstringyes–
limitinteger––
rolestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_a2a_task ~101

Get the status + result of an A2A task. agent_id: the receiving agent (`agt_*`). task_id: the task id returned by `submit_a2a_task` (`a2a_*`). Returns the task's status (submitted / running / succeeded / failed / cancelled), the response messages (when complete), and any error context.

NameTypeReqDescription
agent_idstringyes–
task_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_agent ~37

Get a full agent profile including current trust scores and metadata. agent_id: the agent's unique identifier

NameTypeReqDescription
agent_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_agent_analytics ~75

Get aggregated quality analytics for an agent. agent_id: the agent to analyze days: lookback period (1-365) Returns resolution rate, accuracy, tone, efficiency, security scores, escalation rate, cost, and grade distribution.

NameTypeReqDescription
agent_idstringyes–
daysinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_agent_attributes ~53

Read the tenant-defined ABAC attributes for an agent. These attributes are merged into the Cedar entity at decision time and can be referenced in custom policies as principal.<key>.

NameTypeReqDescription
agent_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_agent_flags ~34

Get active moderation flags for an agent. agent_id: the agent's unique identifier

NameTypeReqDescription
agent_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_agent_reputation ~57

Get an agent's cross-platform reputation score. Returns reputation score (0-100), platform count, positive/negative interaction counts, and per-platform breakdown.

NameTypeReqDescription
agent_idstringyes–
daysinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_agent_timeline ~53

Get an agent's event timeline. agent_id: the agent's unique identifier limit: maximum number of timeline entries (default 50)

NameTypeReqDescription
agent_idstringyes–
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_approval ~29

Get a single approval request by id (`apr_*`).

NameTypeReqDescription
approval_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_benchmark_history ~47

Get benchmark results for an agent across versions. Returns scores, pass rates, and promote/review/block recommendations.

NameTypeReqDescription
agent_idstringyes–
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_circuit_breakers ~28

Get current state of all LLM provider circuit breakers (closed/open/half-open).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_compliance_report ~66

Get a per-tenant compliance report for a specific framework. framework_id: 'eu-ai-act' | 'nist-ai-rmf' | 'iso-42001' Returns pass/warn/fail per control with evidence counts and recommendations.

NameTypeReqDescription
framework_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_content_provenance ~61

Public lookup of a provenance manifest by SHA-256 content hash. Use this to verify whether a piece of content was AI-generated by a VeriSwarm agent. No authentication required on the server side.

NameTypeReqDescription
content_hashstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_context_dashboard ~27

Combined context governance dashboard — topics + quality + gaps.

NameTypeReqDescription
daysinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_context_gaps ~29

Detect agents with high failure rates and low knowledge base coverage.

NameTypeReqDescription
daysinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_cost_recommendations ~56

Get cost optimization recommendations for an agent. Analyzes conversation patterns and suggests: model downgrades, KB improvements, prompt optimization, and security reviews.

NameTypeReqDescription
agent_idstringyes–
daysinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_credentials ~48

Issue a signed JWT Passport credential for the authenticated agent. Requires agent key auth (VERISWARM_AGENT_KEY). Not available with API key only. Also requires the platform signing key to be configured.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_custom_domain ~34

Get the custom domain configuration for the workspace. Requires session auth (x-account-access-token). Not available with API key only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_error_budget ~25

Get error budget status based on tenant SLO targets and recent LLM usage.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_execution ~42

Get the status and step-by-step results of a workflow execution. execution_id: the execution ID (starts with wfx_)

NameTypeReqDescription
execution_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_findings ~29

List Guard security findings. Optionally filter by agent_id.

NameTypeReqDescription
agent_idstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_ip_allowlist ~37

Get the current IP allowlist configuration for the workspace. Requires session auth (x-account-access-token). Not available with API key only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_my_score ~37

Get your own trust scores with improvement guidance. Requires agent key auth (VERISWARM_AGENT_KEY). Not available with API key only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_owasp_attestation ~61

Get a per-tenant OWASP Agentic AI Top 10 (2026) coverage report. Returns covered/partial/gap status for each of the 10 risks, evidence counts from Guard/Vault, and an overall coverage score.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_pii_session ~32

Get details of a PII tokenization session including all tokens created.

NameTypeReqDescription
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_provider_health ~41

Get health status of all LLM providers. Returns per-provider: success rate, P95 latency, active requests, cooldown status, and consecutive failure count.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_score_breakdown ~29

Get detailed score breakdown with contributing factors for an agent.

NameTypeReqDescription
agent_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_score_history ~33

Get score history over time for an agent.

NameTypeReqDescription
agent_idstringyes–
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_scoring_profile ~37

Get the current workspace's scoring profile and weight configuration. Requires session auth (x-account-access-token). Not available with API key only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_sre_dashboard ~27

Combined SRE dashboard — circuit breakers + SLO + error budget + provider health.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_workflow ~39

Get details of a specific workflow including recent executions. workflow_id: the workflow ID (starts with wf_)

NameTypeReqDescription
workflow_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

guard_scan_session ~468

Score one conversation turn for multi-turn exfiltration risk (Session Sentry). Call this once per turn — after the agent has generated its reply and before you send it to the user. Pass a stable ``session_id`` for the entire conversation and a monotonically increasing ``turn_index`` (0, 1, 2 …). The scorer accumulates canary-token egress and system-prompt extraction signals across turns with time decay. Key response fields: - ``blocked`` (bool) — if True, suppress the reply and halt the turn; the enforcement_level and block_threshold explain why. - ``session_score`` — cumulative exfiltration risk for the session (0.0–1.0). - ``turn_value`` — this turn's raw contribution before decay. - ``highest_severity`` — "none" | "low" | "medium" | "high" | "critical". - ``contributions`` — list of scored signals (type, value, weight). - ``enabled`` — False while the tenant is on the free tier (dormant); blocked will always be False in that state. session_id: stable identifier for this conversation (≤64 chars, alphanumeric / hyphens / underscores). Use the same value for every turn in the same conversation. turn_index: zero-based turn counter; must increase monotonically within a session. The scorer uses ordering to apply time decay. user_text: the user's message for this turn (optional but improves signal). agent_text: the agent's reply for this turn — primary exfil surface; always pass this. system_prompt: the system prompt active for this turn (optional; used to detect system-prompt extraction attempts in agent_text). agent_id: optional VeriSwarm agent ID (`agt_*`) to associate the scan with a registered agent's trust record. actor_id: optional caller / user identifier for audit purposes.

NameTypeReqDescription
actor_idstring––
agent_idstring––
agent_textstring––
session_idstringyes–
system_promptstring––
turn_indexintegeryes–
user_textstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

invite_team_member ~70

Invite a new team member to the workspace. Requires session auth (x-account-access-token). Not available with API key only. email: the email address to invite role: 'admin' or 'member' (default 'member')

NameTypeReqDescription
emailstringyes–
rolestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the io.github.veriswarm/veriswarm-mcp server?

io.github.veriswarm/veriswarm-mcp runs locally as a PyPI package, launched with uvx veriswarm-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · veriswarm-mcp

# add to Claude Code
claude mcp add veriswarm-veriswarm-mcp -- uvx veriswarm-mcp
Common questions

What is the io.github.veriswarm/veriswarm-mcp server?

io.github.veriswarm/veriswarm-mcp is listed in the public MCP registry as io.github.veriswarm/veriswarm-mcp. VeriSwarm MCP Server, Trust infrastructure for AI agents via Model Context Protocol. This page covers its PyPI package (veriswarm-mcp).

Is the io.github.veriswarm/veriswarm-mcp server safe to use?

io.github.veriswarm/veriswarm-mcp scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.veriswarm/veriswarm-mcp server expose?

io.github.veriswarm/veriswarm-mcp exposes 102 tools: check_trust, check_decision, get_my_score, get_score_history, get_score_breakdown, and 97 more. Their descriptions and schemas cost roughly 6,522 tokens of context every time the server is loaded.

Is the io.github.veriswarm/veriswarm-mcp server still maintained?

io.github.veriswarm/veriswarm-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.veriswarm/veriswarm-mcp server under?

io.github.veriswarm/veriswarm-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.