HubLens MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hublens_trendingA | Get today's trending open-source projects from HubLens. Returns ranked projects with scores, stars, categories, and AI-generated summaries. |
| hublens_searchB | Search the HubLens archive of all historically tracked OSS projects. Supports filtering by category, source, and text search. |
| hublens_articleA | Get full details for a specific OSS project article by its slug. Includes summaries, use cases, highlights, and metadata in English and Chinese. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: hublens_article retrieves detailed information for a specific article, hublens_search performs broad filtering and text-based searches across the archive, and hublens_trending provides ranked trending projects. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with the prefix 'hublens_' followed by a descriptive action (article, search, trending). This uniformity enhances readability and predictability, with no deviations in style or convention.
With only 3 tools, the server feels slightly thin for a comprehensive OSS project analysis domain, as it lacks operations like creating, updating, or deleting content. However, the tools cover core retrieval and search functions adequately for a basic service.
The tools provide good coverage for reading and searching OSS project data, but there are notable gaps in CRUD operations (e.g., no create, update, or delete tools) and limited analytical functions beyond trending. This may restrict agents from performing full lifecycle management tasks.