Skip to main content
Glama
lllNuggetslll

nessie-mcp-server

by lllNuggetslll
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nessie-mcp-server

No user-submitted related servers found.

    Related Servers

    • stravamcp

      didikz
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables a single Strava account to be accessed through the Model Context Protocol, exposing read-only athlete, activity, route, segment, stream, and gear data plus activity summaries and zones.
      -

    • MCP YNAB Server

      Meh-S-Eze
      F
      license
      B
      quality
      Not graded
      maintenance
      Provides access to YNAB (You Need A Budget) functionality through the Model Context Protocol, allowing users to view account balances, access transaction data, and create new transactions.
      10
      -

    • MCP OpenFEC Server

      psalzman
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Federal Election Commission data via the OpenFEC API, providing access to campaign finance information such as candidates, committees, contributions, and expenditures through the Model Context Protocol.
      12
      2
      BSD 3-Clause

    • neo4j-mcp-readonly

      ThisIsVoid
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only access to Neo4j databases via the Model Context Protocol, allowing safe Cypher queries, schema exploration, and database statistics.
      3 npm
      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.1/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools are clearly distinct, with get_ vs list_ separating single-resource and collection operations for customers and accounts. The main overlap is nessie_get_transactions versus nessie_list_deposits/nessie_list_withdrawals, but the descriptions clarify that the former is a combined feed.

    Naming Consistency5/5

    Every tool follows the same nessie_ prefix plus a consistent verb_noun convention: get_ for individual resources, list_ for collections, with singular and plural nouns used correctly. The naming is uniform and predictable.

    Tool Count5/5

    Nine tools is a well-scoped count for a read-only customer/account/transaction API. Each major resource type has a dedicated endpoint, and there is no obvious bloat or excessive granularity.

    Completeness4/5

    The tool surface covers customer lookup, account lookup, transactions, deposits, withdrawals, bills, and loans, which is solid for the apparent read-only domain. Minor gaps exist: no singular getters for deposits/withdrawals/bills/loans, and no write operations, but the server appears intentionally read-only.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources