Rank #3 of 6 in MCP Infrastructure & Registries
vs Composio
vs Smithery
vs Pipedream MCP
vs Gram (Speakeasy)
vs ManufactShowcase
Try itExperimental
See what an agent can do with Glama before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://glama.ai/api/mcp/openapi.json | head -c 500recorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Auth credentials — stories about auth credentials in this arenaAuth credentialsevidence →
Stories about auth credentials in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Deployment self host — stories about deployment self host in this arenaDeployment self hostevidence →
Stories about deployment self host in this arena
Gateway controls — stories about gateway controls in this arenaGateway controlsevidence →
Stories about gateway controls in this arena
Hosted servers — stories about hosted servers in this arenaHosted serversevidence →
Stories about hosted servers in this arena
Observability analytics — stories about observability analytics in this arenaObservability analyticsevidence →
Stories about observability analytics in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plansevidence →
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Registry discovery — stories about registry discovery in this arenaRegistry discoveryevidence →
Stories about registry discovery in this arena
Sdk clients — stories about sdk clients in this arenaSdk clientsevidence →
Stories about sdk clients in this arena
Tool curation quality — stories about tool curation quality in this arenaTool curation qualityevidence →
Stories about tool curation quality in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 0 free · 1 paid · 0 enterprise · 25 not stated in evidence
Follow the green: where the map greys out is where Glama stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~6/10
unlocks → Scoped API keys · Versioning policy · Official CLI · Headless / CI · Full data export · Drive the publish-and-deploy workflow from an official CLI — authenticate, stage or build a server, push it, and install it into agents · Plug the platform's tools into major agent frameworks and SDKs (Vercel AI SDK, LangChain, CrewAI, OpenAI or Anthropic SDKs) with documented adapters
Subscribe to events via webhooks
~4/10
Build against official SDKs
~3/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
✓7/10
Download a machine-readable API spec (OpenAPI or equivalent)
✓8/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~4/10
unlocks → Headless / CI
Explore an interactive API reference with runnable examples
~5/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓8/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
n/an/a
Plug MCP servers into this product so it can use their tools
✓7/10
Get AI-generated insights and suggestions from my data inside the product
n/an/a
Set up automations that run autonomously in the background
~4/10
Auth credentials — stories about auth credentials in this arenaAuth credentials
Stories about auth credentials in this arena
Maintain separate connected accounts and scoped tokens per end user of my product, so each user's agent acts only on that user's credentials
—0/10
Let the platform run OAuth flows for downstream tools and vault the resulting credentials encrypted, with automatic token refresh
—0/10
White-label the authorization flow with my own branding and my own OAuth app credentials
—–
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Deployment self host — stories about deployment self host in this arenaDeployment self host
Stories about deployment self host in this arena
Gateway controls — stories about gateway controls in this arenaGateway controls
Stories about gateway controls in this arena
Hosted servers — stories about hosted servers in this arenaHosted servers
Stories about hosted servers in this arena
Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform
✓8/10
Point my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructure
✓7/10
Turn an existing API definition (OpenAPI) or custom code into a hosted MCP server without writing protocol plumbing
~4/10
Publish my own MCP server on the platform for distribution, discovery, and installation by others
✓7/10
Subscribe my agent to events from connected downstream apps (triggers/webhooks) instead of polling them
~4/10
Observability analytics — stories about observability analytics in this arenaObservability analytics
Stories about observability analytics in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Registry discovery — stories about registry discovery in this arenaRegistry discovery
Stories about registry discovery in this arena
Query the platform's registry or catalog through a documented API to discover servers and tools programmatically
✓8/10
Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to it
~6/10
Exercise an MCP server's tools from a browser-based inspector or playground before integrating it
✓8/10
Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agent
✓8/10
Sdk clients — stories about sdk clients in this arenaSdk clients
Stories about sdk clients in this arena
Tool curation quality — stories about tool curation quality in this arenaTool curation quality
Stories about tool curation quality in this arena
Rely on the platform scanning or inspecting listed servers for malicious or vulnerable behavior before my agents use them
~5/10
Compare servers using published quality signals — usage counts, health or liveness checks, scores, or verification badges
!5/10
Search and load tools at runtime through meta-tools instead of having thousands of tool definitions stuffed into my context
—0/10
Sorted by importance (agentic first) (high → low) · 52/52 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Tprobed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Cclaimed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Tprobed⚿ | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | disputed | 4/10 | Dcontradicted⚿ | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Tprobed⚿ | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ⚿ | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ⚿ | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 4/10 | Cclaimed | |
Query the platform's registry or catalog through a documented API to discover servers and tools programmatically C Api | ai agent | Registry discovery — stories about registry discovery in this arenaRegistry discovery | 3 | full | 8/10 | Tprobed⚿ | |
Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform C Catalog | developer | Hosted servers — stories about hosted servers in this arenaHosted servers | 3 | full | 8/10 | Tprobed⚿ | |
Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agent C Search | developer | Registry discovery — stories about registry discovery in this arenaRegistry discovery | 3 | full | 8/10 | Tprobed | |
Point my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructure C Connect | developer | Hosted servers — stories about hosted servers in this arenaHosted servers | 3 | fullpaid | 7/10 | Xcommunity | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 4/10 | Cclaimed | |
Let the platform run OAuth flows for downstream tools and vault the resulting credentials encrypted, with automatic token refresh C Oauth | developer | Auth credentials — stories about auth credentials in this arenaAuth credentials | 3 | none | 0/10 | ||
Maintain separate connected accounts and scoped tokens per end user of my product, so each user's agent acts only on that user's credentials C Multi tenant | platform-engineer | Auth credentials — stories about auth credentials in this arenaAuth credentials | 3 | none | 0/10 | ⚿ | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ⚿ | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Exercise an MCP server's tools from a browser-based inspector or playground before integrating it C Playground | developer | Registry discovery — stories about registry discovery in this arenaRegistry discovery | 2 | full | 8/10 | Cclaimed | |
Publish my own MCP server on the platform for distribution, discovery, and installation by others C Publish | developer | Hosted servers — stories about hosted servers in this arenaHosted servers | 2 | full | 7/10 | Xcommunity | |
Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to it C Metadata | developer | Registry discovery — stories about registry discovery in this arenaRegistry discovery | 2 | partial | 6/10 | Tprobed⚿ | |
Restrict which servers and individual tools an agent may call through allowlists or per-tool access control C Access control | platform-engineer | Gateway controls — stories about gateway controls in this arenaGateway controls | 2 | partial | 6/10 | Cclaimed | |
Compare servers using published quality signals — usage counts, health or liveness checks, scores, or verification badges C Signals | developer | Tool curation quality — stories about tool curation quality in this arenaTool curation quality | 2 | disputed | 5/10 | Dcontradicted | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed⚿ | |
Rely on the platform scanning or inspecting listed servers for malicious or vulnerable behavior before my agents use them C Security | platform-engineer | Tool curation quality — stories about tool curation quality in this arenaTool curation quality | 2 | partial | 5/10 | Tprobed | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 4/10 | Cclaimed | |
See a log of every tool call that passed through the platform, with enough detail to audit or replay what an agent did C Audit | platform-engineer | Gateway controls — stories about gateway controls in this arenaGateway controls | 2 | partial | 4/10 | Cclaimed | |
Subscribe my agent to events from connected downstream apps (triggers/webhooks) instead of polling them C Triggers | developer | Hosted servers — stories about hosted servers in this arenaHosted servers | 2 | partial | 4/10 | Cclaimed | |
Turn an existing API definition (OpenAPI) or custom code into a hosted MCP server without writing protocol plumbing C Generate | developer | Hosted servers — stories about hosted servers in this arenaHosted servers | 2 | partial | 4/10 | Cclaimed | |
Drive the publish-and-deploy workflow from an official CLI — authenticate, stage or build a server, push it, and install it into agents C Cli | developer | Sdk clients — stories about sdk clients in this arenaSdk clients | 2 | none | 0/10 | ⚿ | |
Plug the platform's tools into major agent frameworks and SDKs (Vercel AI SDK, LangChain, CrewAI, OpenAI or Anthropic SDKs) with documented adapters C Frameworks | developer | Sdk clients — stories about sdk clients in this arenaSdk clients | 2 | none | 0/10 | ||
Search and load tools at runtime through meta-tools instead of having thousands of tool definitions stuffed into my context C Tool search | ai agent | Tool curation quality — stories about tool curation quality in this arenaTool curation quality | 2 | none | 0/10 | ||
See transparent pricing per tool call or connection plus documented rate limits before committing to the platform G Pricing | developer | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 2 | none | 0/10 | ||
See usage analytics for the servers and tools my org consumes or publishes — call volumes, users, errors, and cost C Analytics | platform-engineer | Observability analytics — stories about observability analytics in this arenaObservability analytics | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
Bridge a locally running MCP server into the platform as a managed remote connection without deploying it C Bridge | developer | Deployment self host — stories about deployment self host in this arenaDeployment self host | 1 | partial | 5/10 | Cclaimed | |
Prototype my agent's tool connections on a meaningful free tier before paying anything G Pricing | developer | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 1 | disputed | 4/10 | Dcontradicted | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | 0/10 | ||
White-label the authorization flow with my own branding and my own OAuth app credentials C White label | platform-engineer | Auth credentials — stories about auth credentials in this arenaAuth credentials | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 36 stories with headroom
What would move Glama’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Auth credentials — stories about auth credentials in this arenaLet the platform run OAuth flows for downstream tools and vault the resulting credentials encrypted, with automatic token refresh
nonemoves PA Scoreimpact 30
No evidence Glama manages OAuth flows for downstream tools or vaults credentials with encrypted storage and automatic refresh; the docs cover hosting, gateway logging, per-tool access control and inspector testing but nothing about OAuth/credential vaulting.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
No evidence of a data-export feature, open-format export tools, or account-portability mechanism for user-uploaded MCP configurations, server catalogs, or usage data; evidence covers hosting, API access, and catalog browsing but not exporting/leaving with one's own data.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
Missing: any mention of open-source code, self-host installer/docker-compose for the core platform, or on-prem deployment instructions.
Auth credentials — stories about auth credentials in this arenaMaintain separate connected accounts and scoped tokens per end user of my product, so each user's agent acts only on that user's credentials
nonemoves PA Scoreimpact 30
No evidence of per-end-user connected accounts or scoped tokens; Glama's gateway/hosting docs describe per-tool access control and a single API-key model for the platform itself, not multi-tenant credential isolation for a product's end users.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
Missing: any training-data opt-out policy, privacy documentation, or terms-of-service statement on data usage.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
No evidence of an official Glama CLI tool anywhere in the docs, probes, or community discussion; the product exposes web UI, APIs (OpenAPI, registry API), and a browser-based inspector, but nothing indicating a dedicated CLI for AI-native workflows.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Missing: scoped credential creation, permission/role definitions per key, evidence of least-privilege token issuance for agents.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Missing: explicit API version numbering, changelog/migration guides, and a stated deprecation/support-lifetime policy.
Showing the top 8 of 36 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 29 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
MCP docs20 stories
- Point an agent at llms.txt or agent-oriented docs
- Plug MCP servers into this product so it can use their tools
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Explore an interactive API reference with runnable examples
- Test against a sandbox environment without touching production data
- Bridge a locally running MCP server into the platform as a managed remote connection without deploying it
- Restrict which servers and individual tools an agent may call through allowlists or per-tool access control
- See a log of every tool call that passed through the platform, with enough detail to audit or replay what an agent did
- Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform
- Point my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructure
- Turn an existing API definition (OpenAPI) or custom code into a hosted MCP server without writing protocol plumbing
- Publish my own MCP server on the platform for distribution, discovery, and installation by others
- Do everything through the API that I can do in the UI
- Prototype my agent's tool connections on a meaningful free tier before paying anything
- Query the platform's registry or catalog through a documented API to discover servers and tools programmatically
- Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to it
- Exercise an MCP server's tools from a browser-based inspector or playground before integrating it
- Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agent
- Rely on the platform scanning or inspecting listed servers for malicious or vulnerable behavior before my agents use them
API reference10 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Explore an interactive API reference with runnable examples
- Download a machine-readable API spec (OpenAPI or equivalent)
- Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform
- Do everything through the API that I can do in the UI
- Query the platform's registry or catalog through a documented API to discover servers and tools programmatically
- Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to it
Hacker News10 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform
- Point my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructure
- Publish my own MCP server on the platform for distribution, discovery, and installation by others
- Do everything through the API that I can do in the UI
- Prototype my agent's tool connections on a meaningful free tier before paying anything
- Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agent
- Rely on the platform scanning or inspecting listed servers for malicious or vulnerable behavior before my agents use them
- Compare servers using published quality signals — usage counts, health or liveness checks, scores, or verification badges
.well known docs8 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Explore an interactive API reference with runnable examples
- Download a machine-readable API spec (OpenAPI or equivalent)
- Do everything through the API that I can do in the UI
- Query the platform's registry or catalog through a documented API to discover servers and tools programmatically
llms.txt7 stories
- Point an agent at llms.txt or agent-oriented docs
- Connect an agent via an official MCP server
- Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platform
- Query the platform's registry or catalog through a documented API to discover servers and tools programmatically
- Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agent
- Rely on the platform scanning or inspecting listed servers for malicious or vulnerable behavior before my agents use them
- Compare servers using published quality signals — usage counts, health or liveness checks, scores, or verification badges
Pricing docs7 stories
- Run the product headlessly / in CI for automation
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Subscribe my agent to events from connected downstream apps (triggers/webhooks) instead of polling them
- Do everything through the API that I can do in the UI
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://glama.ai/api/mcp/openapi.json | head -c 500reproduced$ curl -s https://glama.ai/api/mcp/openapi.json | head -c 500
{"openapi":"3.0.3","info":{"contact":{"email":"support@glama.ai","name":"Glama","url":"https://glama.ai"},"description":"The MCP API provides access to our curated directory of MCP servers. Use it to integrate the [Glama MCP server directory](https://glama.ai/mcp/servers) into your application.\n\n## Authentication\n\nDirectory read endpoints require an API [redacted]. [Create one here](https://glama.ai/settings/api-[redacted]s) and send it as `[redacted] <[redacted]>`.\n\nThe usage telemetry endpoint is
$curl -s 'https://glama.ai/api/mcp/v1/servers?first=2' | head -c 700reproduced$ curl -s 'https://glama.ai/api/mcp/v1/servers?first=2' | head -c 700
{"error":{"code":"unauthorized","message":"This endpoint requires an API [redacted]. Create one at https://glama.ai/settings/api-[redacted]s.\n\nUse of this data is governed by the API Data License, which requires visible attribution to Glama on every page that displays it, and a link to a record's Glama listing wherever you present that record: https://glama.ai/policies/terms-of-service"}}
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
3 of 9 testable claims verified · 0 contradicted → integrity 33/100
9 distinct capability claims found in Glama’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
3
Verified
6
Unverified
0
Contradicted
17
Undersold
Verified (4)
“Can build a server image straight from a connected GitHub repository”
Publish my own MCP server on the platform for distribution, discovery, and installation by othersfullproof ↗
“Supports deploying via Dockerfile, npm package, or PyPI module with configurable build steps and runtime versions”
Publish my own MCP server on the platform for distribution, discovery, and installation by othersfullproof ↗
“Offers a curated, searchable catalog of open-source servers and remote connectors with inspectable capabilities”
Search and browse a large catalog of MCP servers and tools by capability before wiring anything into my agentfullproof ↗
“Offers a curated, searchable catalog of open-source servers and remote connectors with inspectable capabilities”
Inspect a listed server's tools, input schemas, transport, and hosting attributes before connecting to itpartialproof ↗
Unverified (6)
“Lets you test any MCP server directly from your browser, supporting all MCP features”
Exercise an MCP server's tools from a browser-based inspector or playground before integrating itfullproof ↗
“Routes every MCP tool call from your agents through the platform so you can see and control what the AI does”
See a log of every tool call that passed through the platform, with enough detail to audit or replay what an agent didpartialproof ↗
“Provides per-tool access control to enable or disable individual tools”
Restrict which servers and individual tools an agent may call through allowlists or per-tool access controlpartialproof ↗
“Lets you expose a local MCP server via a public tunnel (mcp-proxy) so it can be tested with the hosted inspector”
Bridge a locally running MCP server into the platform as a managed remote connection without deploying itpartialproof ↗
“Supports automating workflows via schedules or webhooks”
“Supports automating workflows via schedules or webhooks”
Subscribe my agent to events from connected downstream apps (triggers/webhooks) instead of polling thempartialproof ↗
Undersold (17)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Plug MCP servers into this product so it can use their toolsfullproof ↗
Drive the product through a documented public APIpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Explore an interactive API reference with runnable examplespartialproof ↗
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Reach a deep catalog of third-party apps and APIs (hundreds to thousands of integrations) through the platformfullproof ↗
Point my MCP-compatible client at a hosted remote server URL and reach downstream tools without deploying any infrastructurefullproof ↗
Turn an existing API definition (OpenAPI) or custom code into a hosted MCP server without writing protocol plumbingpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Query the platform's registry or catalog through a documented API to discover servers and tools programmaticallyfullproof ↗
Rely on the platform scanning or inspecting listed servers for malicious or vulnerable behavior before my agents use thempartialproof ↗
Claims outside our story set (1)
Real capability claims found in Glama’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Server listings are private by default and can be switched to public when ready”
source ↗
Business model
The MCP directory and browser inspector are free to use; the AI workspace (chat, gateway, hosted servers) is a paid subscription, and the directory API is metered behind API keys with an attribution license.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% (30d, checked every 6h since Sep 8 '26)