Skip to main content
Glama
Sign In
highnote-mcp

highnote-mcp

by Mohith26
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to highnote-mcp

No user-submitted related servers found.

    Related Servers

    • CardOS MCP Server

      CardOS MCP Serverofficial

      CMSCardOS
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to issue and manage virtual cards, check balances, pull transactions, file disputes, and start KYC via the CardOS API.
      26
      16 npm
      MIT

    • x402card

      RWA-ID
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to spend from ENS-addressed virtual cards without ever seeing card numbers or API keys, by issuing cards with spend policy published as ENS text records, checking card status, requesting funding, freezing a card, and listing transactions. Charges within policy clear automatically, while above-policy requests escalate to a human approver and anomalous activity triggers an automatic freeze.
      MIT

    • AgentCard MCP Server

      tiny-agent-company
      -
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to manage and use prepaid virtual Visa cards with hard budget limits for secure online transactions. It provides tools for creating cards, checking balances, and retrieving payment credentials with human-in-the-loop approvals.
      1
      -
    • Shatale MCP Server

      Shatale MCP Serverofficial

      Shatale-SASU
      A
      license
      A
      quality
      A
      maintenance
      AI-native payment infrastructure that enables AI agents to make purchases, issue virtual cards, and manage spending within delegated budgets and policy controls.
      7
      447 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

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action pair: authorization simulation, card/account lookups, activity listing, issuance, two clearly-scoped spend-rule types, and two distinct card-state operations. The suspend vs close overlap is disambiguated by explicit 'reversible'/'cannot be undone' wording, and the amount-limit vs merchant-category rules are clearly separated.

    Naming Consistency5/5

    All nine tools follow a consistent snake_case verb_noun pattern (get_*, list_*, issue_*, set_*, restrict_*, suspend_*, close_*, simulate_*). Verb choices are meaningful and the singular/plural noun usage is coherent.

    Tool Count5/5

    Nine tools is well-scoped for a card-issuance and spend-control domain, and every tool earns its place by covering a distinct operation. No filler or trivially duplicative tools.

    Completeness3/5

    Core lifecycle (issue, look up, limit, simulate, suspend, close) is covered, but suspend is described as reversible with no resume/unsuspend tool, and spend rules can be created but not listed, updated, or removed. These dead ends will block agents that need to reverse or audit their changes.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources