# AgentOS (remote · tryagentos.net)

Shared business knowledge, tools and skills for AI agents, with citations and approval controls.

- Trust score: 39/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `tryagentos.net`: 39/100 (this document), [markdown](https://verifymcp.io/servers/devvcore-agentos/api-mcp.md), [page](https://verifymcp.io/servers/devvcore-agentos/api-mcp)

## Channel facts

- Endpoint: `https://tryagentos.net/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the AgentOS MCP server?

AgentOS is a hosted endpoint at https://tryagentos.net/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http devvcore-agentos 'https://tryagentos.net/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "devvcore-agentos": {
      "url": "https://tryagentos.net/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "devvcore-agentos": {
      "type": "http",
      "url": "https://tryagentos.net/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.devvcore-agentos]
url = "https://tryagentos.net/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "devvcore-agentos": {
      "type": "remote",
      "url": "https://tryagentos.net/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add devvcore-agentos --url 'https://tryagentos.net/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  devvcore-agentos:
    url: "https://tryagentos.net/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "devvcore-agentos": {
      "Transport": "http",
      "Url": "https://tryagentos.net/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add devvcore-agentos -t streamable-http -u 'https://tryagentos.net/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "devvcore-agentos": {
      "type": "http",
      "url": "https://tryagentos.net/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-12 (score 39, +1)

- [security improvement] Authorization: partial → pass

### 2026-11-06 (score 38, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-10-28 (score 38, +2)

- [security improvement] Authorization: fail → pass

### 2026-10-27 (score 36, −2)

- [security regression] Authorization: unverified → fail
- [security regression] Transport: fail → unverified
- [security improvement] HSTS header: unverified → pass
- [security] Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- [functional] Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

### 2026-10-26 (score 38, 0)

- [security regression] Transport: unverified → fail
- [security regression] Authorization: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-10-17 (score 0)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/devvcore-agentos/api-mcp#diagnostics

## Score history

- 2026-11-21: 39
- 2026-11-20: 39
- 2026-11-19: 39
- 2026-11-18: 39
- 2026-11-17: 39
- 2026-11-16: 39
- 2026-11-15: 39
- 2026-11-14: 39
- 2026-11-13: 39
- 2026-11-12: 39
- 2026-11-11: 38
- 2026-11-10: 38
- 2026-11-09: 38
- 2026-11-08: 38
- 2026-11-07: 38
- 2026-11-06: 38
- 2026-11-05: 38
- 2026-11-04: 38
- 2026-11-03: 38
- 2026-11-02: 38
- 2026-11-01: 38
- 2026-10-31: 38
- 2026-10-30: 38
- 2026-10-29: 38
- 2026-10-28: 38
- 2026-10-27: 36
- 2026-10-26: 38
- 2026-10-25: 38
- 2026-10-24: 38
- 2026-10-23: 38

## Common questions

### What is the AgentOS MCP server?

AgentOS is an MCP server listed in the public MCP registry as io.github.devvcore/agentos. Shared business knowledge, tools and skills for AI agents, with citations and approval controls. This page covers its hosted endpoint (https://tryagentos.net/api/mcp).

### Is the AgentOS MCP server safe to use?

AgentOS scores 39 out of 100 on VerifyMCP. 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.

### Does the AgentOS MCP server require authentication?

Yes. AgentOS asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the AgentOS MCP server still maintained?

AgentOS is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the AgentOS MCP server?

VerifyMCP ran 5 checks on AgentOS, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about AgentOS: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://tryagentos.net/api/mcp
- Authorisation metadata: https://tryagentos.net/.well-known/oauth-protected-resource/api/mcp
- Website: https://tryagentos.net/
- Changelog RSS feed: https://verifymcp.io/servers/devvcore-agentos/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/devvcore-agentos/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/devvcore-agentos/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/devvcore-agentos/api-mcp
