discovery
Server Details
Search independent software the big engines bury: indie apps, open-source repos, and dev tools.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 5 of 5 tools scored. Lowest: 3.2/5.
Each tool has a clearly distinct purpose: get_listing for a single listing, index_stats for aggregate stats, list_capabilities for capabilities, search_indie for indie software, and search_middleware for middleware. No overlap in functionality.
Most tools follow a verb_noun pattern (get_listing, list_capabilities, search_indie, search_middleware). index_stats deviates slightly as it could be interpreted as noun_noun, but it's still clear and consistent in style.
Five tools is well-scoped for a discovery server, covering listing details, search, and index statistics. Each tool earns its place without being excessive or sparse.
Core discovery operations are covered: listing details, searches, capabilities listing, and stats. A minor gap is the lack of a tool for detailed middleware info beyond search results, but it's not critical for the server's purpose.
Available Tools
5 toolsget_listingInspect
Get full detail for one listing by id, including its outbound url, creator, tags, and popularity/recency signals.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
index_statsInspect
How much of the independent-software index is available: total listings, how many are fresh or small, and the top sources, languages and tags.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_capabilitiesInspect
List the middleware capabilities Devadex indexes (dialogue, auth, inventory, networking, memory, …) with how many middleware exist for each, plus the platforms available. Use this to pick a capability/platform for search_middleware.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
search_indieInspect
Search independent, small, and newly launched software that mainstream search engines bury. Each result has a buyUrl (the link to send the user to — it may be an affiliate link) and a clean url. Use small=true to see only low-authority (buried) results, fresh=true for recent launches.
| Name | Required | Description | Default |
|---|---|---|---|
| fresh | No | Only recently launched or updated listings. | |
| query | No | What the user wants, e.g. 'markdown editor', 'mcp server for notes', 'indie invoicing tool'. | |
| small | No | Only low-authority listings — the long tail Google buries. | |
| source | No | Filter to one source, e.g. 'npm' or 'github'. | |
| language | No | Filter by programming language, e.g. 'Rust'. |
search_middlewareInspect
Search reusable software middleware by CAPABILITY (what it does) across every platform — e.g. 'dialogue', 'authentication', 'inventory', 'networking', 'memory'. Returns middleware libraries, SDKs, and systems with an outbound link to where each is shipped. Use capability for the exact capability slug (see list_capabilities), platform to narrow to an engine/language, and query for free text.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Free-text, e.g. 'branching dialogue', 'oauth login'. | |
| platform | No | Platform slug, e.g. 'unity', 'godot', 'python', 'web'. | |
| capability | No | Capability slug, e.g. 'dialogue', 'authentication', 'pathfinding'. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!