retoor
251c3dc2ba
- 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)
53 lines
2.7 KiB
Markdown
53 lines
2.7 KiB
Markdown
# Glama Directory API reference
|
|
|
|
## Metadata
|
|
|
|
| Field | Value |
|
|
|---|---|
|
|
| Institute | Molodetz Institute - Research and Retrieval Division |
|
|
| Subject | mcp-client-support |
|
|
| Document type | Source Dossier |
|
|
| Tier | 1 |
|
|
| Source title | Glama Directory API reference |
|
|
| Source URL | https://glama.ai/mcp/reference |
|
|
| 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 Directory API reference: base URL `https://glama.ai/api/mcp` with [REDACTED] auth, 100 requests per second, cursor pagination, an OpenAPI document, and endpoints covering servers, remote connectors, hosted instances, and tool-usage reporting. Directory reads require an API key; only usage telemetry is unauthenticated.
|
|
|
|
## Key findings
|
|
|
|
- API: "Base URL `https://glama.ai/api/mcp`", "Bearer [REDACTED] / 100 requests per second / cursor pagination" (`endCursor`/`after`, `hasNextPage`), OpenAPI at `https://glama.ai/api/mcp/openapi.json`.
|
|
- "Directory read endpoints require an API key... send it as `Authorization: Bearer <key>`" (`glm_...` keys); only "The usage telemetry endpoint is unauthenticated." (Consistent with the observed 401 on an unauthenticated `GET /api/mcp/v1/servers`.)
|
|
- Endpoints: list servers, server attributes, retrieve server by ID/slug; list remote connectors, connector attributes, retrieve connector; hosted instances; report tool usage. "Attribution is required... data is licensed, not public domain."
|
|
|
|
## Pros / strengths
|
|
|
|
- A real paginated, rate-stated API (100 rps, cursor pagination, OpenAPI doc) rather than a scrape-only directory, so programmatic discovery is a supported path.
|
|
- Endpoint coverage (servers by ID/slug, remote connectors, hosted instances) maps cleanly onto resolver lookup needs.
|
|
- Auth and licensing terms are explicit, so integration obligations are knowable before building.
|
|
|
|
## Cons / limitations / caveats
|
|
|
|
- No publish date; endpoint details could drift without notice.
|
|
- Keyed access (key from `glama.ai/settings/api-keys`) plus attribution/licensing obligations add integration cost versus the keyless official registry.
|
|
- Vendor API doc: coverage and freshness claims for the underlying catalog are self-reported and unverified.
|
|
|
|
## Relevance to tai
|
|
|
|
Keyed, paginated discovery API usable as a fallback catalog when registry plus repo signals are thin, with attribution obligations. Confirms the lookup order: keyless official registry first, Glama second.
|
|
|
|
## Changelog
|
|
|
|
| Date | Change |
|
|
|---|---|
|
|
| 2026-10-18 | Initial dossier created. |
|