UND Assay
REMOTE · UNDASSAY.COM
Evidence on MCP servers before you install: publisher, source, provenance, advisories, changes.
Available components
Last scanned (4 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security100
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 593 tokens (~74/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 25% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +2
- DNSSEC: fail → pass ▲ security
- 3 Nov 26 +1
- Tool “check_before_install” rewrote its description, which is the text the model reads security
- Schema quality: 67 → 74 ▼ functional
- Tool coverage: 18% → 25% ▲ functional
- “check_before_install” added an optional parameter “installed” cosmetic
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.12.0 → 0.13.0 functional
- 31 Oct 26 75
First indexed and scored.
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 · Probed https://undassay.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=undassay.com | CN=WE1,O=Google Trust Services,C=US | 30 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6d4625fcd16f18e613cf1a2a073911a0 |
| SANs: undassay.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of undassay.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| undassay.com. | present | 2371 | 13 | Verified |
| undassay.com. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Sign in to use this tool", resource_metadata="https://undassay.com/.well-known/oauth-protected-resource/mcp", scope="read"
Bearer error="invalid_token", error_description="Sign in to use this tool", resource_metadata="https://undassay.com/.well-known/oauth-protected-resource/mcp", scope="read"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; font-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Protected resource metadata
| Document | https://undassay.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://undassay.com/mcp |
| Authorisation server | https://undassay.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://undassay.com/mcp | Verified | 200 | |
| http (plaintext) | http://undassay.com/mcp | HTTPS enforced | 301 | https://undassay.com/mcp |
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 →
check_before_install Check a tool before installing it ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | 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) |
No output schema declared.
No examples provided.
get_changes What changed between versions ~37
Metadata changes between consecutive published versions: new network hosts, replaced or added artifact sources, newly requested credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| tool_id | string | yes | – |
No output schema declared.
No examples provided.
get_evidence One assertion with its evidence ~51
A single assertion of a tool (by field name) with the evidence records behind it: URL, fetch time, SHA-256.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | yes | – |
| tool_id | string | yes | – |
No output schema declared.
No examples provided.
get_publisher Publisher identity ~43
How a publisher is identified across ecosystems (MCP namespace, domain, GitHub, packages) and the state of each link.
| Name | Type | Req | Description |
|---|---|---|---|
| publisher_key | string | yes | – |
No output schema declared.
No examples provided.
get_setup How to connect a tool ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | MCP server name, catalog id, or GitHub repository URL |
No output schema declared.
No examples provided.
get_tool Full evidence for a tool ~48
Every assertion for a tool with its state (VERIFIED, CLAIMED, CONTRADICTED, STALE, UNKNOWN), reason, check and evidence records.
| Name | Type | Req | Description |
|---|---|---|---|
| tool_id | string | yes | – |
No output schema declared.
No examples provided.
resolve_identifier Does this tool really exist? ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
No output schema declared.
No examples provided.
search_tools Search tools ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| official_only | boolean | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · undassay.com
claude mcp add --transport http com-undassay-und-assay 'https://undassay.com/mcp'
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.