mcpbeat Sign in

UND Assay MCP Server

answering

UND Assay is answering right now. Last checked 7 min ago. It exposes 8 tools.

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

Uptime history 13 hours of history
13 hours agonow
100.0%
Uptime 24h
48 of 48 checks
8
Tools
read from the server
185 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 November 2026. No other catalogue keeps this.

1 Nov a tool changed version

Nothing serious here today

Today is the operative word: we check UND Assay every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add und-assay --transport http https://undassay.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://undassay.com/mcp
~/.codex/config.toml
[mcp_servers.und-assay]
url = "https://undassay.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "und-assay": {
      "url": "https://undassay.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "und-assay": {
      "type": "http",
      "url": "https://undassay.com/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

before
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.
changes
get_changes
Metadata changes between consecutive published versions: new network hosts, replaced or added artifact sources, newly requested credentials.
evidence
get_evidence
A single assertion of a tool (by field name) with the evidence records behind it: URL, fetch time, SHA-256.
publisher
get_publisher
How a publisher is identified across ecosystems (MCP namespace, domain, GitHub, packages) and the state of each link.
resolve
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.
setup
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 the sign-in metadata of the server. Never a safety rating.
tool
get_tool
Every assertion for a tool with its state (VERIFIED, CLAIMED, CONTRADICTED, STALE, UNKNOWN), reason, check and evidence records.
tools
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.

Endpoints

URLTransportStateLatencyChecked
https://undassay.com/mcp streamable-http answering 209 ms 7 min ago

Alternatives to UND Assay

same job, measured the same way
ScriptProbe MCP
by thecompound

ScriptProbe: Check npm install scripts and publisher changes before installing.

local only
tashan
by tashan

Check any MCP server or agent skill before installing: upkeep, real adoption, and OSV advisories.

63 installs/wk local only
GAIP — evidence on AI agents before and after you call them
by tjcgraham-rgb

GAIP keeps an independent, dated record of what AI agents, MCP servers and online shops publish.

5 tools answering
Registry
by policylayer

The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install.

5 tools answering
MCP Checkup
by mcpcheckup

Observed facts on public MCP servers: protocol checks, tool changes, signed evidence. No verdicts.

6 tools answering
Mcpgrade
by mcpgrade

Security grades (A-F) for MCP servers. Check one before you install or trust it. mcpgrade.dev

48 installs/wk local only
sf-intelligence: offline Salesforce MCP server
by pranavnagrecha

Ask your AI what breaks before you change Salesforce. Offline, read-only, cited answers.

local only
MCP Probe
by incultnitollc

Inspect and score any MCP server 0-100 on publishability, schema and protocol before publish.

71 installs/wk local only

UND Assay — questions

Answers built from our own checks of this server.

What can UND Assay do?
It exposes 8 tools, read directly from the server on our last check. Among them: check_before_install, get_changes, get_evidence, get_publisher, get_setup, get_tool and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is UND Assay working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 48 of 48 checks got a reply (100.0%), average response time 185 ms. The bar chart above shows every period we have measured.
How do I connect UND Assay?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does UND Assay need an API key?
No. UND Assay completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is UND Assay?
It answers our handshake in 185 ms on average, which is faster than 74% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.