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.imran-siddique/agentos

NPM · AGENTOS-MCP-SERVER

Build and manage policy-compliant AI agents with safety enforcement and compliance checking

Available components

0 this week 79 Trust /100

Last scanned (7 hours ago)

Scores higher than 62% of npm servers

Category Security

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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 9.0.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 44 of 122 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency47
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 275 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1591 tokens (~159/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_agent" implies "deploy" 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 10 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 4 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 0
    • CVE-2023-54404 affects this package: high ▼ security
  • 21 Oct 26 +1
    • Stability: 0.97 → pass security
  • 19 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 17 Oct 26 +3
    • Stability: 0.83 → 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 npm/agentos-mcp-server@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 122 packages
Packages resolved 122
Deprecated 1
Stale 43
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,591 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
attach_policy ~210

Attach safety policies to an agent. Policies enforce rules and constraints on agent behavior. Available policy templates: - pii-protection: Protects personally identifiable information (GDPR compliant) - rate-limiting: Prevents resource abuse through rate limits - cost-control: Prevents runaway costs from automated operations - data-deletion: Prevents accidental data loss - secrets-protection: Prevents exposure of secrets and credentials - human-review: Requires human approval for sensitive actions Compliance frameworks: - gdpr-compliance: EU data protection compliance - soc2-security: SOC 2 Type II security controls - hipaa-healthcare: Healthcare data privacy (PHI protection) - pci-dss-payments: Payment card data security

NameTypeReqDescription
agentIdstringyesAgent ID to attach policy to
customRulesarray–Additional custom rules to add
policyIdstringyesPolicy template ID (e.g., "pii-protection", "gdpr-compliance")

No output schema declared.

No examples provided.

audit_log ~151

Query the audit trail for an agent. The audit log records: - Every action attempted by the agent - Policy evaluations and decisions - Approval requests and outcomes - Success/failure status - Timestamps and metadata Use for: - Debugging agent behavior - Compliance reporting - Security investigations - Performance analysis

NameTypeReqDescription
actionFilterstring–Filter by action type
agentIdstringyesAgent ID to get audit log for
endTimestring–End of time range (ISO 8601)
limitnumber–Maximum entries to return (default: 100)
startTimestring–Start of time range (ISO 8601)

No output schema declared.

No examples provided.

check_compliance ~174

Check an agent's compliance with regulatory frameworks. Supported frameworks: - SOC2: Service Organization Control 2 Type II - GDPR: EU General Data Protection Regulation - HIPAA: Health Insurance Portability and Accountability Act - PCI_DSS: Payment Card Industry Data Security Standard - CCPA: California Consumer Privacy Act - NIST: NIST Cybersecurity Framework - ISO27001: ISO/IEC 27001 Information Security - FEDRAMP: Federal Risk and Authorization Management Program The compliance check evaluates: - Policy coverage for framework requirements - Audit trail completeness - Access control implementation - Data protection measures

NameTypeReqDescription
agentIdstringyesAgent ID to check
frameworkstringyesCompliance framework to check against
generateReportboolean–Generate detailed compliance report

No output schema declared.

No examples provided.

create_agent ~189

Create a new AI agent from a natural language description. The agent will be configured with appropriate policies and safety guardrails. Example usage: - "Create an agent that processes customer feedback from support emails daily" - "Build a data pipeline that backs up my Documents folder to Google Drive" - "Set up an agent to monitor our API health and alert on issues" Returns the agent specification with recommended safety policies.

NameTypeReqDescription
approvalRequiredboolean–Whether human approval is required before execution
descriptionstringyesNatural language description of what the agent should do
languagestring–Programming language for the agent
policiesarray–Policy templates to apply (e.g., "pii-protection", "rate-limiting")
schedulestring–Cron schedule for recurring execution (e.g., "0 9 * * *" for daily at 9 AM)

No output schema declared.

No examples provided.

create_policy ~173

Create a custom policy from a natural language description. Policies define rules that agents must follow. Example policies: - "Block access to customer credit card data" - "Require approval for any external API calls" - "Rate limit database queries to 100 per minute" - "Log all file deletions" Policies can be based on existing templates: - pii-protection, rate-limiting, cost-control - gdpr-compliance, soc2-security, hipaa-healthcare The policy engine will translate your description into enforceable rules.

NameTypeReqDescription
basedOnstring–Policy template to extend
categorystringyesPolicy category
descriptionstringyesNatural language policy description
frameworkstring–Compliance framework (e.g., "SOC2", "GDPR", "HIPAA")

No output schema declared.

No examples provided.

deploy_agent ~118

Deploy an agent to start execution. Deployment environments: - local: Runs on your machine (default) - cloud: Runs on AgentOS cloud infrastructure (requires API key) Before deployment, the agent must: - Pass all policy checks - Have valid configuration - Have necessary integrations configured For scheduled agents, deployment starts the scheduler. For triggered agents, deployment enables the triggers.

NameTypeReqDescription
agentIdstringyesAgent ID to deploy
autoStartboolean–Start agent immediately after deployment
environmentstring–Deployment environment

No output schema declared.

No examples provided.

get_agent_status ~100

Get the current status, metrics, and health of an agent. Returns: - Current status (draft, testing, deployed, paused, stopped, error) - Execution metrics (runs, success rate, errors) - Recent activity - Policy compliance stats - Resource usage

NameTypeReqDescription
agentIdstringyesAgent ID to get status for
includeLogsboolean–Include recent logs
includeMetricsboolean–Include execution metrics

No output schema declared.

No examples provided.

list_templates ~178

Browse the library of pre-built agent and policy templates. Agent templates include: - Data processors, email assistants, database analysts - File organizers, backup agents, web scrapers - Slack bots, API monitors, report generators Policy templates include: - Security: PII protection, secrets protection, data deletion safety - Compliance: GDPR, SOC 2, HIPAA, PCI DSS - Operational: Rate limiting, cost control, human review Use templates as a starting point for your custom agents.

NameTypeReqDescription
categorystring–Filter by category (e.g., "data", "security", "compliance")
frameworkstring–Filter by compliance framework (e.g., "GDPR", "SOC2")
searchstring–Search query to filter templates
typestring–Template type to list

No output schema declared.

No examples provided.

request_approval ~165

Request human approval for a sensitive agent action. Use this when: - Policy requires human review before execution - Agent attempts a high-risk action - You want to add an extra safety check Approval requests are sent to designated approvers via: - Email notification - Slack notification (if configured) - Dashboard alert Requests expire after the specified time (default: 24 hours).

NameTypeReqDescription
actionstringyesAction requiring approval (e.g., "delete_files", "send_email")
agentIdstringyesAgent ID requesting approval
approversarrayyesEmail addresses of approvers
descriptionstringyesDetailed description of what will happen if approved
expiresInHoursnumber–Hours until approval expires (default: 24)

No output schema declared.

No examples provided.

test_agent ~133

Test an agent with a simulated scenario before deployment. This performs a dry-run that: - Validates the agent configuration - Checks all policies against the test scenario - Simulates workflow execution - Reports any policy violations or issues - Estimates resource usage and costs No actual changes are made during testing.

NameTypeReqDescription
agentIdstringyesAgent ID to test
dryRunboolean–Run without side effects (default: true)
mockDataobject–Mock data for testing (optional)
scenariostringyesTest scenario description (e.g., "Process 100 customer emails")

No output schema declared.

No examples provided.

Install

How do I install the io.github.imran-siddique/agentos MCP server?

io.github.imran-siddique/agentos runs locally as an npm package, launched with npx -y agentos-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · agentos-mcp-server

# add to Claude Code
claude mcp add imran-siddique-agentos -- npx -y agentos-mcp-server
Common questions

What is the io.github.imran-siddique/agentos MCP server?

io.github.imran-siddique/agentos is an MCP server listed in the public MCP registry as io.github.imran-siddique/agentos. Build and manage policy-compliant AI agents with safety enforcement and compliance checking. This page covers its npm package (agentos-mcp-server).

Is the io.github.imran-siddique/agentos MCP server safe to use?

io.github.imran-siddique/agentos scores 79 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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.imran-siddique/agentos MCP server expose?

io.github.imran-siddique/agentos exposes 10 tools: create_agent, attach_policy, test_agent, deploy_agent, get_agent_status, and 5 more. Their descriptions and schemas cost roughly 1,591 tokens of context every time the server is loaded.

Is the io.github.imran-siddique/agentos MCP server still maintained?

io.github.imran-siddique/agentos 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.imran-siddique/agentos MCP server under?

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

What did VerifyMCP test on the io.github.imran-siddique/agentos MCP server?

VerifyMCP ran 16 checks on io.github.imran-siddique/agentos, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.