Skip to main content
Glama
ball2jh

findagrave-com-mcp

by ball2jh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to findagrave-com-mcp

No user-submitted related servers found.

    Related Servers

    • wikitree-mcp

      Genealogy-MCP
      A
      license
      A
      quality
      C
      maintenance
      Enables querying WikiTree genealogy data including profiles, ancestors, descendants, relatives, biography, photos, and categories via natural language.
      2
      1
      AGPL 3.0

    • familysearch-org-mcp

      ball2jh
      A
      license
      A
      quality
      B
      maintenance
      Enables direct interaction with FamilySearch.org's shared Family Tree and historical records, including reading and adding people, facts, relationships, sources, notes, memories, record search, and image downloads, without needing a browser.
      9
      MIT

    • GitHub GraphQL API MCP

      MCP-Mirror
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables querying and exploring the GitHub GraphQL API schema and executing optimized GraphQL queries to retrieve precise GitHub data (repositories, issues, PRs, users) with reduced token consumption.
      -

    • FamilySearch MCP Server

      JonathanReiss15
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search FamilySearch's Family Tree, view person details, explore ancestors and descendants, and search historical records using browser session authentication.
      5 npm
      3
      MIT
    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.5/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct domain (memorials, cemeteries, places, downloads, GraphQL), but findagrave_place search and findagrave_cemetery search can both return cemeteries by name, creating mild ambiguity about which to use.

    Naming Consistency4/5

    All tools share the findagrave_ prefix, but actions mix verb forms (search, get) with plural nouns (photos, flowers), and findagrave_download and findagrave_graphql break the resource-noun pattern of the other tools.

    Tool Count5/5

    Five top-level tools is well-scoped; each tool covers a logical area, and exposing actions under memorial/cemetery/place keeps the surface clean without bloat.

    Completeness5/5

    The server covers the full read-only workflow for Find a Grave: memorial search/detail/photos/flowers, cemetery and place lookup, photo download, and a GraphQL fallback for any missing data. No obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources