# AgentViva (remote · agentviva.dev)

Is an AI tool, agent or MCP server alive, and since when? Checks from the outside, with proof.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `agentviva.dev`: 36/100, [markdown](https://verifymcp.io/servers/dev-agentviva-agentviva/agentviva.md), [page](https://verifymcp.io/servers/dev-agentviva-agentviva/agentviva)
- remote · `agentviva.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dev-agentviva-agentviva/mcp-public.md), [page](https://verifymcp.io/servers/dev-agentviva-agentviva/mcp-public)

## Channel facts

- Endpoint: `https://agentviva.dev/mcp/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.7.1`

## 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**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 692 tokens (~230/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

AgentViva is a hosted endpoint at https://agentviva.dev/mcp/public, 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 dev-agentviva-agentviva 'https://agentviva.dev/mcp/public'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-agentviva-agentviva": {
      "url": "https://agentviva.dev/mcp/public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-agentviva-agentviva": {
      "type": "http",
      "url": "https://agentviva.dev/mcp/public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-agentviva-agentviva]
url = "https://agentviva.dev/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-agentviva-agentviva": {
      "type": "remote",
      "url": "https://agentviva.dev/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-agentviva-agentviva --url 'https://agentviva.dev/mcp/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-agentviva-agentviva:
    url: "https://agentviva.dev/mcp/public"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-agentviva-agentviva": {
      "Transport": "http",
      "Url": "https://agentviva.dev/mcp/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-agentviva-agentviva -t streamable-http -u 'https://agentviva.dev/mcp/public'
```

### Other

```json
{
  "mcpServers": {
    "dev-agentviva-agentviva": {
      "type": "http",
      "url": "https://agentviva.dev/mcp/public"
    }
  }
}
```

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-20 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 70)

First indexed and scored.

## MCP tools (3)

### `lookup_tool` (~92 tokens)

Is this AI tool up?

Look up an AI tool AgentViva already watches publicly, by name ("Notion") or address ("notion.so"), and get its state (up, degraded, down, blocked or unknown), since when, and its public status page. No API key needed. It reads what AgentViva already knows; it does not check the address now.

Input parameters:

- `query` (string, required): A tool name or an address.

### `check_url` (~184 tokens)

Is this address working right now?

Check any public website or hosted MCP server once, right now, and get what AgentViva saw: works, partly works, does not work, or blocked (the site refused the check or asks bots not to open it, which does not mean it is down), with the evidence (HTTP status, where the redirects ended, the page title, or the MCP tools it lists). No API key needed. One check is a snapshot, not a verdict over time: for a tool AgentViva watches every day, lookup_tool gives its confirmed state and history. The same address is answered from a 5-minute copy. Private and local addresses are refused.

Input parameters:

- `type` (string): page (a website, the default) or mcp (a hosted MCP server).
- `url` (string, required): The address, for example notion.so or https://example.com/mcp.

### `report_problem` (~159 tokens)

Report that a tool does not work

Tell AgentViva that a tool it watches publicly does not work for you or your user, by name ("Notion") or address ("notion.so"), with an optional short note of what happened. AgentViva checks it again right away (at most once an hour per tool) and answers with what that check saw. A report never changes the tool's state by itself: only AgentViva's own checks do, and several must agree. One report per network, tool and day is counted. No API key needed. For a tool AgentViva does not watch, use check_url instead.

Input parameters:

- `note` (string): What happened, in a few words (optional).
- `query` (string, required): A tool name or an address.

## Diagnostics

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

## Score history

- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 72
- 2026-11-18: 72
- 2026-11-17: 71
- 2026-11-16: 71
- 2026-11-15: 70
- 2026-11-14: 70

## Common questions

### What is the AgentViva MCP server?

AgentViva is an MCP server listed in the public MCP registry as dev.agentviva/agentviva. Is an AI tool, agent or MCP server alive, and since when? Checks from the outside, with proof. This page covers its hosted endpoint (https://agentviva.dev/mcp/public).

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

AgentViva scores 73 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.

### What tools does the AgentViva MCP server expose?

AgentViva exposes 3 tools: lookup_tool, check_url, report_problem. Their descriptions and schemas cost roughly 435 tokens of context every time the server is loaded.

### Does the AgentViva MCP server require authentication?

No. We connected to AgentViva without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AgentViva MCP server still maintained?

AgentViva 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 AgentViva MCP server?

VerifyMCP ran 13 checks on AgentViva, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://agentviva.dev/mcp/public
- Repository: https://github.com/AgentViva/docs
- Website: https://agentviva.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-agentviva-agentviva/mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-agentviva-agentviva/mcp-public/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-agentviva-agentviva/mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/dev-agentviva-agentviva/mcp-public
