Skip to main content
Glama
CNR-Consulting

CorroborateMe

by CNR-Consulting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to CorroborateMe

No user-submitted related servers found.

    Related Servers

    • mcp-secure-server

      andreimelneichuk
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access corporate HR and CRM APIs on behalf of a specific user through OAuth 2.1 token verification, deny-by-default RBAC, token exchange, audit logging, PII masking, and untrusted-output envelopes.
      MIT

    • Wallet4Agent MCP Server

      TalaoDAO
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with a DID-based identity, secure wallet, and cloud KMS-backed signing keys, enabling trusted interactions with persons, companies, and other agents via standards like OIDC4VCI, OIDC4VP, and SD-JWT.
      Apache 2.0

    • Mailgent MCP Server

      loomal-ai
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides identity infrastructure for AI agents to manage email communications, including sending, replying, and organizing messages. It also includes a secure vault for managing credentials and generating TOTP codes.
      7 npm
      MIT

    • AgentPay MCP Server

      Rumblingb
      F
      license
      Not graded
      quality
      A
      maintenance
      Provides a trust and governance layer for AI agents, enabling secure API access, credential vaulting, paid execution with human approval, and automatic call resume.
      6 npm
      2
      -

    • Higgfield MCP

      nanabrownsnr
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables secure API key management, generation tracking, and calling external APIs through stored credentials, with JWT and persona-scoped access plus Twynity integration.
      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 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: login lifecycle, webhook management, integrations, billing, keys, and OAuth. Even related tools like get_login_status and retry_login_webhook serve clearly different purposes (status check vs. retry), so there is no realistic ambiguity.

    Naming Consistency3/5

    All names are snake_case, but the verb/noun order is inconsistent—some are verb-first (create_login_link, get_login_status) while others are noun-first (budget_get, keys_create, integration_list). This mixed convention reduces predictability, though the names remain readable and self-explanatory.

    Tool Count5/5

    13 tools is well within the ideal 3-15 range for a server with this breadth (authentication, billing, integrations, key management, OAuth). Each tool appears justified and none feel redundant or superfluous for the scope.

    Completeness3/5

    The tool surface covers core creation and retrieval workflows (create/login status, keys_create, billing_checkout), but lacks lifecycle operations such as revoking keys, deleting OAuth clients, or removing webhook allowlist entries. These gaps could force agents to hit dead ends in real-world scenarios.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources