Skip to main content
Glama
nous-portal-mcp

nous-portal-mcp

by callisto-syn

Related Servers

Alternatives to nous-portal-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A portable, stdio-based MCP server that exposes curated read operations across Microsoft Graph, Power BI, and Dataverse, plus an optional create-only Gemba action tool, using explicit Entra identities and read-only defaults. It lets teams run enterprise engineering workflow steps—discovery, draft preparation, and reviewed progress tracking—with separately approved, permission-scoped connectors and no automatic tenant access.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      This local MCP server enables AI assistants to query, report on, and, with explicit confirmation, change Webex organizations they administer. It supports multi-org reads, license and workspace inventories, and optional live SIP registration checks while keeping tokens local and writes gated.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A spec-compliant remote MCP server with built-in OAuth 2.1 and Dynamic Client Registration, enabling Notion Custom Agents to connect via 'Sign in with OAuth' without bearer tokens. It supports SSO federation to Google and Microsoft Entra, and includes basic tools like whoami, echo, and slow_task.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Minimal MCP server for testing SkyStage's self-auth auto-detection feature. It includes tools like ping, echo, server_info, and read_secret, and uses a mock OAuth provider for login.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      A read-only local MCP server that lets harnesses query Microsoft Intune devices, policies, apps, enrollment, and RBAC using the signed-in user's delegated Microsoft Graph access.
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: checking configuration, listing routes, starting device-code login, and polling for authentication. No ambiguity or overlap exists.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with 'nous_portal_' prefix, making them predictable and easy to understand.

    Tool Count5/5

    With 4 tools covering status, routes, and the auth flow (start + poll), the count is well-scoped for the server's purpose without being too thin or excessive.

    Completeness4/5

    The tool surface covers essential operations for the adapter (status, routes, authentication start and poll). Minor gaps like logout or token refresh are missing, but the core workflow is complete.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing