Other · Local MCP server
Agentos
Build and manage policy-compliant AI agents with safety enforcement and compliance checking.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.imran-siddique/agentos- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-02-02
- Updated
- 2026-02-02
- Publisher
- imran-siddique (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/imran-siddique) · how
- Repository
- github.com/imran-siddique/agent-os (folder extensions/mcp-server)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | agentos-mcp-server | 1.0.1 | stdio |
How to connect Agentos
Agentos runs locally from a Node.js package published to the npm registry: agentos-mcp-server version 1.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y agentos-mcp-server@1.0.1. It reads these environment variables: AGENTOS_POLICY_MODE and AGENTOS_LOG_LEVEL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"agentos": {
"command": "npx",
"args": [
"-y",
"agentos-mcp-server@1.0.1"
],
"env": {
"AGENTOS_POLICY_MODE": "<value>",
"AGENTOS_LOG_LEVEL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Agentmailrooms MCPA paid remote MCP for OpenAI Codex agent coordination MCP, built to return verdicts, receipts, usage. | Remote · HTTPLive check: ✗ no handshake |
| Agentmarketplace MCPDiscover MCP servers + tools, auto-install into any client, pay for x402 endpoints in USDC. | Local · stdio |
| AgentNetAgent-to-agent referral network. Discover, recommend, and refer users between AI agents via MCP. | Remote · HTTPLive check: ✗ no handshake |
| AgentObserver - Check x402 Dependencies Before PayingCheck Exa, BlockRun, OneSource, Apify and other x402 dependencies before invoking or paying. | Remote · HTTPLive check: ✗ no handshake |
| AgentPay - Pay-per-call AI Microservices34 pay-per-call AI microservices via x402, USDC on Base, no API keys. | Remote · HTTPLive check: ✓ handshake |
| AgentPay - trust routing + spend caps for x402 agentsBuyer-side trust oracle + capped sessions for x402 agents: verified_route, receipts, 17 free tools. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| AgentPhoneGive AI agents real phone numbers, messages, and voice calls via MCP. | Remote & Local · HTTP, stdioLive check: sign-in required |
| AgentpmtAI agent marketplace for automated employees, workflows, skills, and tool orchestration. | Remote · HTTPLive check: sign-in required |