Skip to main content
Glama
Sign In
TrustedMCP

TrustedMCP

by akshay-bhanderi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Look up an MCP server

lookup_server
Read-onlyIdempotent

Look up any MCP server's TrustedMCP grade and check results by name, package, image, URL, repo or launch command to see what to fix first.

Instructions

Get an MCP server's TrustedMCP grade (A-D) by name, npm or PyPI package, Docker image, server URL, GitHub repo or launch command (e.g. 'npx -y @playwright/mcp'). Returns the four checks (login, upkeep, known bugs, connection), what to fix first and the TrustedMCP page. For servers without a grade, returns matching official MCP Registry entries.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "lookup_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesName, package, image, URL, repo or command, e.g. 'notion', '@playwright/mcp', 'https://mcp.stripe.com'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the shape of the response (four checks: login, upkeep, known bugs, connection), that it surfaces 'what to fix first', links the TrustedMCP page, and degrades gracefully to official MCP Registry entries when no grade exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the primary action and result, then the return payload and fallback. Dense but every clause carries information; the identifier enumeration is slightly redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description covers the input forms, the graded response contents, the recommended-fix signal, and the ungraded fallback. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single query parameter already documents its accepted forms and examples. The description restates the list of identifier types without adding syntax, normalization, or ambiguity-resolution rules, so it does little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Get an MCP server's TrustedMCP grade (A-D)') and enumerates the identifier forms accepted. An agent can tell what the tool produces, though it doesn't explicitly distinguish itself from the sibling registry_lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'Get ... by name, npm or PyPI package, Docker image, server URL, GitHub repo or launch command', and the fallback for ungraded servers is noted. However there is no explicit statement of when to prefer this over registry_lookup or find_alternatives, and no exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools