Files

T

retoor 251c3dc2ba research: mcp-client-support subject (106 sources, 3 conclusions)

- wire spec: lifecycle, stdio + Streamable HTTP transports, tools,
  utilities, legacy SSE, versioning, changelog (14 Tier 1)
- client ecosystem: Claude Code/VS Code/Cursor/Codex configs,
  mcp-remote, Smithery, registries, Glama (12 Tier 1)
- security/ops: authorization draft, trust model, poisoning,
  rug pulls, production hardening (12 Tier 1) + 68 Tier 2 cards
- conclusions: minimal stdlib client on 2025-11-25, normalizer +
  resolver agent for pasted configs/GitHub URLs, untrusted-until-
  consent trust model; nothing built yet
- audit PASS (14 subjects, 797 sources, 32 conclusions)

2026-10-18 19:23:02 +02:00

2.6 KiB

Raw Blame History

Glama MCP directory

Metadata

Field	Value
Institute	Molodetz Institute - Research and Retrieval Division
Subject	mcp-client-support
Document type	Source Dossier
Tier	1
Source title	Glama MCP directory
Source URL	https://glama.ai/mcp
Source publisher / author	Glama
Source type	vendor docs
Source date (published)	Unknown, not stated
Date researched	2026-10-18
Researched by	tai (agent), model: Claude Sonnet 5, on behalf of retoor
Research method	gather-subagent direct page fetch, parent synthesis from evidence pack
Confidence	Medium
Status	Active

Summary

Glama's MCP directory page, presenting it as a discovery platform ("#1 Platform for Discovering MCP Servers, Connectors, Clients") that "indexes, scans, and ranks servers based on security, compatibility, and ease of use". Products around the directory include Chat, Directory API, Gateway, Hosting, and Inspector.

Key findings

"Glama indexes, scans, and ranks servers based on security, compatibility, and ease of use"; self-describes as "#1 Platform for Discovering MCP Servers, Connectors, Clients".
Products include Chat, Directory API, Gateway, Hosting, Inspector.
Directory read endpoints require an API key (glm_... keys from glama.ai/settings/api-keys), sent as Authorization: Bearer <key>; only "The usage telemetry endpoint is unauthenticated."
"Attribution is required... data is licensed, not public domain."

Pros / strengths

Positions the directory as a ranked, scanned catalog (security, compatibility, ease of use), which is a stronger discovery signal than an unranked list.
The product family (API, Gateway, Hosting, Inspector) suggests the directory data is kept live enough to serve adjacent products.
API key requirement and licensing terms are stated on the record, so usage obligations are known up front.

Cons / limitations / caveats

Marketing-heavy page ("#1 Platform") with no publish date; ranking-methodology claims are self-reported and unverified.
Keyed access plus attribution/licensing obligations constrain casual or unattributed reuse by tai.
An unauthenticated GET /api/mcp/v1/servers was observed returning 401, consistent with the key requirement but confirming no free read path.

Relevance to tai

Usable as a fallback catalog when registry plus repo signals are thin, with attribution obligations. The API-key requirement puts it behind the keyless official registry in tai's lookup order.

Changelog

Date	Change
2026-10-18	Initial dossier created.

2.6 KiB Raw Blame History