Skip to main content
Glama
CNR-Consulting

tillpad-mcp

by CNR-Consulting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to tillpad-mcp

  • CorroborateMe

    CNR-Consulting
    A
    license
    B
    quality
    B
    maintenance
    Enables agents and apps to verify end-user identity through company API keys, human login links with multi-channel notifications, OIDC client registration, and budget-aware billing.
    13
    1
    MIT

Related Servers

  • MemoryAI

    toozuuu
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to automatically capture durable knowledge and retrieve only relevant, token-bounded context from a secure local-first long-term memory, with support for progressive disclosure, snapshots, health diagnostics, and background tasks.
    -

  • BuildAutomata Memory MCP

    brucepro
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides AI agents with persistent, searchable memory that survives across conversations using semantic search, temporal versioning, and smart organization. Enables long-term context retention and cross-session continuity for AI assistants.
    14
    -
  • whimsicality-mcp by WhimsicalityLabs

    whimsicality-mcpofficial

    WhimsicalityLabs
    A
    license
    B
    quality
    B
    maintenance
    Provides persistent memory for AI agents, including context storage, facts, plans, RAG search, code snippets, and conversation compaction, enabling state to survive across sessions and processes.
    14
    15 npm
    2
    MIT

  • haksnbot-memory

    haksndot
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides persistent memory storage for AI agents with full-text search, tagging, and importance levels, enabling agents to store and retrieve memories efficiently.
    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

B3/5.0

Scored across 17 tools

Disambiguation4/5

Each tool targets a distinct operation within its area—billing, keys, KVP, files/RAG, support—and the descriptions clarify boundaries. usage_get and budget_get both report quota state but with different focuses, and inspect_storage aggregates rather than duplicating the CRUD tools. Overall, misselection risk is low.

Naming Consistency2/5

Names mix verb-first styles (usage_get, file_upload, inspect_storage) with noun-first styles (keys_create, kvp_put, run_finish) and compound nouns like billing_machine_pay. There is no consistent verb_noun convention, though prefixes like kvp_ and files_ provide some structure.

Tool Count3/5

17 tools is at the high end for a single MCP server and spans several unrelated domains: billing, key management, key-value storage, RAG files, and support. For a multi-purpose platform API the count is defensible, but it is heavier than a focused, well-scoped server should be.

Completeness3/5

KVP storage has full CRUD and RAG covers upload, listing, and semantic search, but file deletion is missing and key management only supports creation, not listing or revocation. Billing covers usage and budgets but not detailed subscription state or payment history. These gaps are workable but notable for a platform toolkit.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources