ask-habib-mcp
Related Servers
Alternatives to ask-habib-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to query a researcher's public profile, publications, full-text papers, CV, and availability through read-only MCP tools, including publication search and section-by-section paper reading.6754 npmMIT
- AlicenseNot gradedqualityDmaintenanceExposes a person's structured professional profile as MCP tools, enabling Claude and other MCP clients to answer questions about that person based on real data.3 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to query the author's career, projects, publications, and technical documents through read-only MCP tools.-
- AlicenseAqualityBmaintenanceEnables AI assistants to query and retrieve a structured professional profile, including expertise areas, CV, projects, active research, and target AI queries, through dedicated MCP tools and resources.6MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to query a person's CV and portfolio content via MCP tools and resources, returning grounded answers from local markdown data instead of relying on resume parsing.-
- FlicenseAqualityBmaintenanceEnables MCP-compatible agents to answer questions about you by exposing your CV through a tool, resource, and prompt.1-
TDQS
Scored across 5 tools
list_publications, get_publication, and search_publications have clearly distinct retrieval semantics (enumerate vs. fetch-by-id vs. keyword query), so an agent can pick correctly. The only soft overlap is get_profile vs. get_links, since get_profile's description already promises 'contact links' that get_links also returns.
Every tool follows the same verb_noun snake_case pattern (list_/get_/search_ + resource). Resource nouns are used consistently and predictably across the set.
Five tools is a tight, well-scoped surface for a personal publications/CV server; each tool covers a distinct access pattern and none appears redundant enough to remove.
The read-only domain (browse, fetch, search publications; profile and links) is fully covered with no dead ends. Minor gaps: no filtering/listing by venue or year, and get_links largely duplicates contact data already in get_profile.