INDIVIDUAL MCP TOOL

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.

undassay.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://undassay.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_setup and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

A tool name or description suggests retrieving external content.

Parent server

undassay.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: und-assay
Remote MCP URL: https://undassay.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "und-assay",
  "transport": "streamable-http",
  "url": "https://undassay.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related 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.
resolve_identifier — Resolve an MCP server name, catalog id or GitHub repository URL to the real registry entry.
search_tools — Search cataloged MCP servers by keywords.
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.