chakoshi MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHAKOSHI_API_KEY | Yes | Your chakoshi API key. | |
| CHAKOSHI_API_URL | No | The URL of the chakoshi API. | https://api.beta.chakoshi.ntt.com/v1/guardrails/apply |
| CHAKOSHI_TIMEOUT_SEC | No | Timeout in seconds for API calls. | 10 |
| CHAKOSHI_GUARDRAIL_ID | Yes | Your guardrail ID. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| moderate_textC | Check if a text is safe using chakoshi Guardrails Apply API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlapping purposes.
A single tool cannot violate naming consistency; it is inherently consistent.
One tool is borderline for a moderation server; it may serve a narrow use case but feels thin for broader content safety needs.
The server only provides a single text moderation check, lacking other common operations like batch processing, severity levels, or content type differentiation.