UND Assay

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.undassay/und-assay and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 31 Oct 2026. Not supplied by the maker.

• 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

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

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

• 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 / c

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