UND Assay

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

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

8 tools

• check_before_install

  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. No warnings is NOT a safety guarantee.

• get_setup

  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…

• resolve_identifier

  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.

• 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.

• get_tool

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

• get_publisher

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

• get_changes

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

• get_evidence

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

Security scan

Recent checks