Server Details
Enterprise AI governance: spend, guardrails, policy, budgets, compliance, and provider health.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- thinkneo-ai/mcp-server
- GitHub Stars
- 0
- Server Listing
- thinkneo-control-plane
See and control every tool call
Available Tools
8 toolsthinkneo_check_policyInspect
Check if a specific model, provider, or action is allowed by the governance policies configured for a workspace. Requires authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| model | No | AI model name to check (e.g., gpt-4o, claude-sonnet-4-6, gemini-2.0-flash) | |
| action | No | Specific action to check (e.g., create-completion, use-tool, fine-tune) | |
| provider | No | AI provider to check (e.g., openai, anthropic, google, mistral) | |
| workspace | Yes | Workspace name or ID whose governance policies to check against |
thinkneo_check_spendInspect
Check AI spend summary for a workspace, team, or project. Returns cost breakdown by provider, model, and time period. Requires authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| period | No | Time period for the report: today, this-week, this-month, last-month, or custom | this-month |
| end_date | No | End date for a custom period in ISO format (YYYY-MM-DD). Only used when period='custom' | |
| group_by | No | Dimension to group costs by: provider, model, team, or project | provider |
| workspace | Yes | Workspace name or ID (e.g., 'prod-engineering', 'finance-team') | |
| start_date | No | Start date for a custom period in ISO format (YYYY-MM-DD). Only used when period='custom' |
thinkneo_evaluate_guardrailInspect
Evaluate a prompt or text against ThinkNEO guardrail policies before sending it to an AI provider. Returns risk assessment, violations found, and recommendations. Requires authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The prompt or text content to evaluate for policy violations (max 32,000 characters) | |
| workspace | Yes | Workspace whose guardrail policies to apply for this evaluation | |
| guardrail_mode | No | Evaluation mode: 'monitor' (log violations only) or 'enforce' (block the request on violation) | monitor |
thinkneo_get_budget_statusInspect
Get current budget utilization and enforcement status for a workspace. Shows spend vs limit, alert thresholds, and projected overage. Requires authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| workspace | Yes | Workspace name or ID to retrieve current budget status for |
thinkneo_get_compliance_statusInspect
Get compliance and audit readiness status for a workspace. Shows governance score, pending actions, and compliance gaps. Requires authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| framework | No | Compliance framework to assess: soc2 (SOC 2 Type II), gdpr (GDPR), hipaa (HIPAA), or general (ThinkNEO AI governance) | general |
| workspace | Yes | Workspace name or ID to evaluate compliance readiness for |
thinkneo_list_alertsInspect
List active alerts and incidents for a workspace. Includes budget alerts, policy violations, guardrail triggers, and provider issues. Requires authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of alerts to return (1–100) | |
| severity | No | Filter alerts by severity level: critical, warning, info, or all | all |
| workspace | Yes | Workspace name or ID to list active alerts for |
thinkneo_provider_statusInspect
Get real-time health and performance status of AI providers routed through the ThinkNEO gateway. Shows latency, error rates, and availability. No authentication required.
| Name | Required | Description | Default |
|---|---|---|---|
| provider | No | Specific provider to check: openai, anthropic, google, mistral, xai, cohere, or together. Omit to get status for all providers. | |
| workspace | No | Workspace context for provider routing configuration (optional) |
thinkneo_schedule_demoInspect
Schedule a demo or discovery call with the ThinkNEO team. Collects contact information and preferences. No authentication required.
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | Contact's role: cto, cfo, security, engineering, or other | |
| Yes | Business email address to receive follow-up from the ThinkNEO team | ||
| company | Yes | Company or organization name | |
| context | No | Additional context such as current AI providers used, request volume, or specific use case | |
| interest | No | Primary area of interest: guardrails, finops, observability, governance, or full platform | |
| contact_name | Yes | Full name of the person requesting the demo | |
| preferred_dates | No | Preferred meeting dates, times, and timezone (e.g., 'Tuesdays or Thursdays, 9-11am EST') |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.