# UND Assay (remote · undassay.com)

Evidence on MCP servers before you install: publisher, source, provenance, advisories, changes.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `undassay.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-undassay-und-assay/undassay.md), [page](https://verifymcp.io/servers/com-undassay-und-assay/undassay)

## Channel facts

- Endpoint: `https://undassay.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.13.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-05.

- **Endpoint Security**: 100/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 593 tokens (~74/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 25% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 UND Assay MCP server?

UND Assay is a hosted endpoint at https://undassay.com/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 com-undassay-und-assay 'https://undassay.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-undassay-und-assay": {
      "url": "https://undassay.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-undassay-und-assay": {
      "type": "http",
      "url": "https://undassay.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-undassay-und-assay]
url = "https://undassay.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-undassay-und-assay": {
      "type": "remote",
      "url": "https://undassay.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-undassay-und-assay --url 'https://undassay.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-undassay-und-assay:
    url: "https://undassay.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-undassay-und-assay": {
      "Transport": "http",
      "Url": "https://undassay.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-undassay-und-assay -t streamable-http -u 'https://undassay.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-undassay-und-assay": {
      "type": "http",
      "url": "https://undassay.com/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-05 (score 79, +2)

- [security improvement] DNSSEC: fail → pass

### 2026-11-03 (score 77, +1)

- [security] Tool “check_before_install” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 67 → 74
- [functional improvement] Tool coverage: 18% → 25%
- [cosmetic] “check_before_install” added an optional parameter “installed”

### 2026-11-01 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.12.0 → 0.13.0

### 2026-10-31 (score 75)

First indexed and scored.

## MCP tools (8)

### `check_before_install` (~142 tokens)

Check a tool before installing it

Evidence summary for an MCP server before you install or connect it: publisher identity level, provenance, known vulnerabilities, install scripts, maintenance, open warnings, checks that could not run, and recent changes. Pass installed (the servers already in use) to also get tool names this server shares with them, which an AI could call by mistake. No warnings is NOT a safety guarantee.

Input parameters:

- `identifier` (string, required): MCP server name (e.g. io.github.github/github-mcp-server), catalog id, or GitHub repository URL
- `installed` (array): Optional: names of MCP servers already installed, to check for tool-name clashes (first 20 used)

### `get_setup` (~98 tokens)

How to connect a tool

One stable answer (schema_version 1) for connecting an MCP server: its validated remote URL and transport, packages, copy-paste setup for Claude Code and JSON configs, warnings by severity, checks that could not run, and contradicted claims. auth is null until Assay has checked the sign-in metadata of the server. Never a safety rating.

Input parameters:

- `identifier` (string, required): MCP server name, catalog id, or GitHub repository URL

### `resolve_identifier` (~61 tokens)

Does this tool really exist?

Resolve an MCP server name, catalog id or GitHub repository URL to the real registry entry. If there is no exact match, returns the closest real names so look-alikes and invented names can be caught. No account needed.

Input parameters:

- `identifier` (string, required)

### `search_tools` (~81 tokens)

Search tools

Search cataloged MCP servers by keywords. Returns classification (verified_publisher = the publisher proved control of a domain or verified GitHub org, NOT that a company named in the tool made it / community / not_analyzed), identity level and warning counts.

Input parameters:

- `limit` (integer)
- `official_only` (boolean)
- `query` (string, required)

### `get_tool` (~48 tokens)

Full evidence for a tool

Every assertion for a tool with its state (VERIFIED, CLAIMED, CONTRADICTED, STALE, UNKNOWN), reason, check and evidence records.

Input parameters:

- `tool_id` (string, required)

### `get_publisher` (~43 tokens)

Publisher identity

How a publisher is identified across ecosystems (MCP namespace, domain, GitHub, packages) and the state of each link.

Input parameters:

- `publisher_key` (string, required)

### `get_changes` (~37 tokens)

What changed between versions

Metadata changes between consecutive published versions: new network hosts, replaced or added artifact sources, newly requested credentials.

Input parameters:

- `tool_id` (string, required)

### `get_evidence` (~51 tokens)

One assertion with its evidence

A single assertion of a tool (by field name) with the evidence records behind it: URL, fetch time, SHA-256.

Input parameters:

- `field` (string, required)
- `tool_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-undassay-und-assay/undassay#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 75

## Common questions

### What is the UND Assay MCP server?

UND Assay is an MCP server listed in the public MCP registry as com.undassay/und-assay. Evidence on MCP servers before you install: publisher, source, provenance, advisories, changes. This page covers its hosted endpoint (https://undassay.com/mcp).

### Is the UND Assay MCP server safe to use?

UND Assay scores 79 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 UND Assay MCP server expose?

UND Assay exposes 8 tools: check_before_install, get_setup, resolve_identifier, search_tools, get_tool, and 3 more. Their descriptions and schemas cost roughly 561 tokens of context every time the server is loaded.

### Does the UND Assay MCP server require authentication?

Yes. UND Assay 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 UND Assay MCP server still maintained?

UND Assay 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.

## Links

- Remote endpoint: https://undassay.com/mcp
- Website: https://undassay.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-undassay-und-assay/undassay.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-undassay-und-assay/undassay.json
- HTML version of this page: https://verifymcp.io/servers/com-undassay-und-assay/undassay