Skip to main content
Glama
Ritwikjoshi

Ritwik Joshi MCP

by Ritwikjoshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Ritwik Joshi MCP

  • Events MCP

    himanshusaleria
    A
    license
    Not graded
    quality
    D
    maintenance
    Discover tech events, startup meetups, AI events across cities including hidden ones.
    31 npm
    2
    MIT

Related Servers

  • Pavan Madduri — Personal

    pmady
    A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol (MCP) server that exposes a professional profile — certifications, industry articles, open source contributions, and live GitHub activity — as a queryable API for AI agents.
    7
    11
    MIT

  • resume-mcp

    brysontang
    F
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that provides a structured API for AI agents to query a person's resume, including profile, projects, writing, and gated access to experience and skills.
    -

  • requarks-wiki-mcp

    uyu423
    A
    license
    A
    quality
    C
    maintenance
    An MCP server that enables AI agents to interact with Wiki.js as a knowledge base through a comprehensive set of 29 tools for content retrieval and management. It supports full-text search, page versioning, and asset browsing with optional write operations secured by safety gates.
    29
    19 npm
    7
    MIT

  • resume-mcp

    suryakapila
    F
    license
    A
    quality
    B
    maintenance
    MCP server that exposes a resume as callable tools and resources, enabling AI agents to query experience, skills, projects, and contact information via natural language.
    3
    -
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 9 tools

Disambiguation4/5

Each tool targets a distinct audience need—profile, keynotes, TEDx talks, past events, blog posts, FAQ, AI positions, booking, and media kit. There is minor overlap between info.faq and booking.info around booking logistics, and speaker.profile could be confused with info.ai_positions at the edges, but descriptions are specific enough to guide correct selection.

Naming Consistency4/5

The tools consistently use a lowercase dot-separated namespace pattern like speaker.* and info.*, which makes the organizational structure predictable. The main deviation is that most tools use noun-like descriptors while blog.search and media.send_kit use verb-based names, creating a slight stylistic inconsistency.

Tool Count5/5

Nine tools is a well-scoped size for a personal speaker and booking server. Each tool covers a meaningful aspect of the domain—biography, talks, events, written content, FAQs, expert opinions, booking, and media distribution—without unnecessary redundancy.

Completeness5/5

The tool surface covers the full promotional and booking lifecycle: who the speaker is, what he speaks about, past proof, published content, practical FAQs, booking logistics, and press kit delivery. No significant dead ends or obvious missing capabilities are apparent for this server's stated purpose.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources