io.github.veriswarm/veriswarm-mcp
PYPI · VERISWARM-MCP
VeriSwarm MCP Server — Trust infrastructure for AI agents via Model Context Protocol
Available components
Last scanned (1 hour ago)
Scores higher than 58% of PyPI servers
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.
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
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 →
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 →
invoke_a2a_agent ~186
Submit an A2A task to a (trust-ranked) agent and wait for the result. Convenience over submit_a2a_task + get_a2a_task: submits the task, then polls until it reaches a terminal state (completed / failed / canceled) or max_wait_seconds elapses, and returns the final task JSON (status, messages, artifacts). On timeout it returns the latest non-terminal task with "timed_out": true — keep polling with get_a2a_task. All trust / policy enforcement happens server-side; this tool only orchestrates submit + poll.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| max_wait_seconds | number | – | – |
| messages_json | string | yes | – |
| poll_interval_seconds | number | – | – |
| requesting_agent_id | string | yes | – |
| signature_json | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
kill_agent ~97
Activate the kill switch for an agent, immediately blocking all trust decisions. Works with an API key that a workspace owner or admin has granted the guard.killswitch.write scope (requires server support for that scope), or with an account session (x-account-access-token). agent_id: the agent to kill-switch reason: human-readable reason for the kill switch activation
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| reason | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
label_content ~78
Generate an Ed25519-signed provenance manifest for AI-generated content. Returns the manifest (signature, content hash, metadata). Machine-readable format compatible with EU AI Act Article 50 transparency requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| content | string | yes | – |
| content_type | string | – | – |
| model | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_a2a_catalog ~71
List the tenant's trust-ranked A2A agent catalog. Returns agents in descending trust-score order, excluding any agent currently in the kill-switch state. Each entry includes the agent's id, slug, current trust score, and a short description suitable for an A2A discovery flow.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_agents ~100
List agents in the workspace. Supports search and filtering by policy tier. query: optional search string to filter agents by name or slug tier: optional policy tier filter — tier_0 (most restricted), tier_1, tier_2, tier_3 (most trusted), or all page: page number for pagination (default 1)
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
| query | string | – | – |
| tier | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_approvals ~85
List approval requests for the authenticated tenant. state: one of "pending", "approved", "rejected", "expired", "all". agent_id: optional filter to a single agent (`agt_*`). limit: 1..500 (server-enforced).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| limit | integer | – | – |
| state | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_cedar_policies ~21
List active Cedar declarative policies for the tenant.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_compliance_frameworks ~31
List supported compliance frameworks (eu-ai-act, nist-ai-rmf, iso-42001).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_deletion_records ~34
List GDPR deletion records with verification hashes. Requires session auth (x-account-access-token). Not available with API key only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_guard_policies ~35
List all active Guard policies for the workspace. Requires session auth (x-account-access-token). Not available with API key only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_jit_grants ~48
List JIT grants for the tenant, optionally filtered by agent or status.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| limit | integer | – | – |
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_notifications ~38
List recent notifications for the workspace. Requires session auth (x-account-access-token). Not available with API key only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_red_team_attacks ~41
List available adversarial red team attack patterns. Returns attack counts by category: injection, PII extraction, policy boundary, off-topic, and jailbreak.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_team_members ~33
List team members in the current workspace. Requires session auth (x-account-access-token). Not available with API key only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_workflow_templates ~21
List available workflow templates (both built-in and custom).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_workflows ~41
List all Cortex Workflows for the current tenant. is_active: optional filter — true for active only, false for inactive only
| Name | Type | Req | Description |
|---|---|---|---|
| is_active | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
platform_status ~22
Check VeriSwarm platform health, uptime, and active feature flags.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
provision_a2a_keys ~65
Provision Ed25519 transport keys for an agent. Returns the public key. After provisioning, the agent's public key appears in agent cards under x-veriswarm-transport. Inter-agent messages can then be cryptographically signed.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
query_ledger ~63
Query the immutable Vault audit ledger. Optionally filter by agent. agent_id: filter ledger entries to a specific agent (optional) limit: maximum number of entries to return (default 50)
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
register_agent ~82
Register a new agent in VeriSwarm and return its agent_id. slug: URL-safe unique identifier for the agent, e.g. my-coding-agent display_name: human-readable name shown in dashboards description: optional description of the agent's purpose
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| display_name | string | yes | – |
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rehydrate_pii ~104
Restore original PII values from VeriSwarm tokens in text. Use AFTER the LLM has processed tokenized text and you need to write the real values back to a database, email, CRM, or other system. text: text containing VeriSwarm tokens like [VS:EMAIL:a1b2c3] session_id: the session ID from the original tokenize_pii call
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
reject_approval ~60
Reject 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.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_id | string | yes | – |
| reason | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
report_action ~81
Report a generic agent behavioral event to VeriSwarm for scoring. event_type: dot-separated event type, e.g. tool.call.success agent_id: the agent performing the action (required) payload: JSON string of additional event metadata (optional)
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| event_type | string | yes | – |
| payload | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
report_incident ~99
Report a security incident or anomalous behavior for Guard review. severity: critical, high, medium, or low description: human-readable description of the incident agent_id: the agent involved (required) pattern_type: optional classification, e.g. prompt_injection, data_exfil, abuse
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| description | string | yes | – |
| pattern_type | string | – | – |
| severity | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
report_interaction ~101
Report an agent-to-agent interaction event. other_agent_id: the agent being interacted with interaction_type: type of interaction, e.g. delegate, collaborate, query outcome: outcome of the interaction, e.g. success, failure, refused agent_id: the acting agent (required)
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| interaction_type | string | yes | – |
| other_agent_id | string | yes | – |
| outcome | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
report_tool_call ~76
Report a tool call event. Shorthand for tool.call.success / tool.call.failure events. agent_id is required by the event ingestion API.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| duration_ms | integer | – | – |
| error_type | string | – | – |
| success | boolean | – | – |
| tool_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
request_jit_grant ~106
Request a just-in-time access grant for an agent. Trusted agents (composite_trust >= 75, risk_score <= 30, verified, ttl <= 10min) are auto-approved. Others go to pending for human review.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | – |
| agent_id | string | yes | – |
| reason | string | – | – |
| resource_id | string | – | – |
| resource_type | string | – | – |
| ttl_seconds | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
reset_circuit_breaker ~44
Manually reset a circuit breaker to closed state (e.g., after fixing a provider outage).
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | – |
| provider | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
retry_workflow_execution ~44
Retry a failed workflow execution from where it left off. execution_id: the execution ID to retry (starts with wfx_)
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
revoke_jit_grant ~35
Revoke an approved JIT grant immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| grant_id | string | yes | – |
| reason | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
revoke_pii_session ~48
Revoke a PII tokenization session, deleting all stored tokens. Requires session auth (x-account-access-token). Not available with API key only.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
run_workflow ~33
Manually trigger a workflow execution. workflow_id: the workflow ID to run
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_ci ~118
Scan CI workflow YAML + Dockerfiles for secret-exfiltration risk. files_json: JSON string of an array of file objects, each {"path": str, "content"?: str, "diff"?: str}. Pass "content" (full file at head) for Layer 1 vulnerable-config checks and "diff" (unified diff hunks) for Layer 2 exfil-pattern checks. Returns findings plus a "blocked" decision from the tenant's GuardPolicy enforcement level.
| Name | Type | Req | Description |
|---|---|---|---|
| files_json | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_injection ~37
Scan text for prompt injection patterns. Returns is_injection (bool), confidence score, and matched patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_mcp_tools ~69
Scan MCP tool definitions for security risks (pre-deploy audit). tools_json: JSON string of an array of MCP tool definitions Checks for tool poisoning, typosquatting, schema manipulation, rug-pull patterns, prompt injection, and excessive permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| tools_json | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_tool ~62
Scan text/tool content for security threats (injection and moderation). tool_name: name of the tool or MCP server to scan tool_config: optional JSON string with tool configuration/schema details
| Name | Type | Req | Description |
|---|---|---|---|
| tool_config | string | – | – |
| tool_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
score_conversation_security ~94
Compute a security grade (A-F) for a conversation. Uses Guard + Vault audit data to score PII exposure, injection resistance, policy adherence, tool authorization, and grounding.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | – |
| injection_attempts | integer | – | – |
| injection_blocked | integer | – | – |
| pii_tokens_in_response | integer | – | – |
| policy_violations | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_agent_attributes ~80
Set ABAC attributes for an agent (replaces existing). attributes_json: JSON string of the attributes dict. Values must be strings, numbers, booleans, or lists of those. Reserved keys (policy_tier, risk_score, is_verified) are silently rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| attributes_json | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_custom_domain ~55
Set a custom domain for the workspace. Requires session auth (x-account-access-token). Not available with API key only. domain: the custom domain, e.g. 'trust.mycompany.com'
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_ip_allowlist ~97
Set the IP allowlist for the workspace. Requires session auth (x-account-access-token). Not available with API key only. cidrs: comma-separated list of CIDR ranges, e.g. '10.0.0.0/8,192.168.1.0/24' enabled: whether to enable the allowlist (default True)
| Name | Type | Req | Description |
|---|---|---|---|
| cidrs | string | yes | – |
| enabled | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_scoring_profile ~83
Set the workspace's scoring profile. Requires session auth (x-account-access-token). Not available with API key only. profile_code: one of 'general', 'high_security', 'community', 'enterprise', 'minimal' weight_overrides: optional JSON string of custom weight overrides
| Name | Type | Req | Description |
|---|---|---|---|
| profile_code | string | yes | – |
| weight_overrides | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
submit_a2a_task ~168
Submit a task to an agent via the A2A protocol. agent_id: the receiving agent (`agt_*`). requesting_agent_id: the calling agent's id (`agt_*`). messages_json: JSON-encoded list of message dicts (A2A message shape). signature_json: optional JSON-encoded Ed25519 signature envelope (`{"key_id": "...", "signature": "...", "algo": "ed25519"}`). Returns the new task id and accepted status, or an error if the receiving agent is killed, paused, or stopped (lifecycle-blocked).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| messages_json | string | yes | – |
| requesting_agent_id | string | yes | – |
| signature_json | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
test_cedar_policy ~72
Dry-run a Cedar policy against test input. Returns the decision.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | – | – |
| agent_id | string | – | – |
| is_verified | boolean | – | – |
| policy_text | string | yes | – |
| policy_tier | string | – | – |
| risk_score | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
tokenize_pii ~139
Remove PII from text, replacing with safe tokens like [VS:EMAIL:a1b2c3]. Use BEFORE sending text containing personal data to an LLM. The LLM will see tokens instead of real emails, phone numbers, SSNs, etc. Tokens carry type information so the LLM knows what kind of data was there. text: the text that may contain PII agent_id: optional agent ID to associate with the tokenization session_id: optional session ID to group tokens (auto-generated if empty)
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| session_id | string | – | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
unkill_agent ~72
Deactivate the kill switch for an agent, restoring normal trust decision processing. Works with an API key that a workspace owner or admin has granted the guard.killswitch.write scope (requires server support for that scope), or with an account session (x-account-access-token).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
validate_cedar_policy ~48
Validate Cedar policy syntax without persisting. Returns {"valid": true} on success, {"valid": false, "error": "..."} on failure.
| Name | Type | Req | Description |
|---|---|---|---|
| policy_text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_chain ~39
Verify the hash-chain integrity of the Vault audit ledger. limit: number of recent entries to verify (default 100)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_credential ~40
Verify a Passport JWT credential and return the decoded trust claims. credential: the JWT string issued by VeriSwarm Passport
| Name | Type | Req | Description |
|---|---|---|---|
| credential | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_deletion ~30
Verify a GDPR deletion record exists and return its cryptographic proof.
| Name | Type | Req | Description |
|---|---|---|---|
| record_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_identity ~58
Mark an agent as identity-verified in VeriSwarm Passport (admin action). Requires session auth (x-account-access-token). Not available with API key only. agent_id: the agent to mark as verified
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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
claude mcp add veriswarm-veriswarm-mcp -- uvx veriswarm-mcp
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.