Skip to main content
Glama
thinkneo-ai

ThinkNEO MCP SMB

Official
by thinkneo-ai

Related Servers

Alternatives to ThinkNEO MCP SMB

  • A
    license
    A
    quality
    B
    maintenance
    Enterprise AI governance layer for spend tracking, runtime guardrails, policy enforcement, and budget limits. Connects Claude, ChatGPT, and any MCP client to ThinkNEO's control plane for SOC2/GDPR/HIPAA compliance monitoring and real-time provider health.
    8
    3
    Apache 2.0

Related Servers

  • A
    license
    A
    quality
    A
    maintenance
    An MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.
    30
    53 PyPI
    2
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables self-hosted AI gateway and agent control plane with governed MCP tools, virtual-key budgets, caching, and audit, supporting OpenAI, Anthropic, Gemini, MCP, and A2A protocols. It provides deterministic prompt enhancement and governed execution with a zero-credential first run.
    7
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables production-hardened MCP tool serving with OAuth 2.1 audience-restricted tokens, purpose-bound tools, human-in-the-loop approvals, containment, and audit trails for AI agents.
    Apache 2.0
  • A
    license
    B
    quality
    D
    maintenance
    Dynamic MCP server — 30+ tools across fact verification, agent memory, Indian NLP, contract risk, security threat modelling, sales call intelligence and more. x402/USDC micropayments on Base.
    33
    7 npm
    MIT

TDQS

A4.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: guardrails_check is the combined scanner, while the three others each target a specific threat type (injection, PII, secrets). Descriptions explicitly state when to use each, eliminating ambiguity.

Naming Consistency5/5

Tool names follow a consistent pattern: 'guardrails_scan_{target}' for dedicated tools and 'guardrails_check' for the combined one. The naming is predictable and intuitive.

Tool Count5/5

With 4 tools, the set is well-scoped for a security scanning server. It provides three focused scanners and one aggregated check, covering the domain without unnecessary bloat or missing essentials.

Completeness5/5

The tool set covers prompt injection, PII (in multiple formats), and secrets/credentials comprehensively. The combined tool offers a full safety scan, leaving no obvious gaps for the stated purpose of LLM input and data leakage prevention.

Maintenance

ActivityInactive
ResponsivenessNo issues