Skip to main content
Glama

Server Details

Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation1/5

Both tools accept identical inputs, run the same engine, and cover the same security-check workflow; check_mcp_trust and scan_mcp_server are near-duplicates. An agent cannot reliably determine which to call because the descriptions explicitly say they share the same engine and overlapping purposes.

Naming Consistency4/5

Both names follow a verb_mcp_object snake_case pattern, so the naming convention is recognizable and mostly predictable. The minor inconsistency is that 'trust' is an abstract assessment object while 'server' is a concrete entity, and 'check'/'scan' are semantically close verbs.

Tool Count3/5

Two tools for a narrow security-checking domain is borderline; the functionality could reasonably be a single tool. The count is not harmful, but it feels thin because the second tool mostly duplicates the first.

Completeness4/5

The pair covers the main input types (registry, GitHub repo, remote URL) and key security concerns such as tool-poisoning, capabilities, TLS, and repo trust. There are minor gaps such as no separate report retrieval or historical scan results, but those are not central to the stated purpose.

Available Tools

2 tools
check_mcp_trustAInspect

Check if an MCP server is safe to install: returns a trust score (0-100, grade A-F). Accepts a registry name (io.github.x/y), a GitHub repo (owner/repo), or a remote MCP URL. For remote servers it live-connects and analyzes the actual exposed tools for tool-poisoning + capabilities, and checks the backing repo (maintenance, license, security policy, auth). Call BEFORE installing or recommending any MCP server.

Inputs: target (required).

scan_mcp_serverBInspect

Scan and inspect an MCP server for security issues before connecting it: live tool-poisoning analysis, exposed-tool inventory + capabilities, TLS, and repo trust signals. Same engine as check_mcp_trust. Accepts a registry name, GitHub repo, or remote MCP URL.

Inputs: target (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources