AI or Not MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIORNOT_API_KEY | Yes | Your AI or Not API key | |
| AIORNOT_API_URL | No | API base URL | https://api.aiornot.com |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aiornot_analyze_mediaB | Analyze image, video, audio (music/voice), or text using the AI or Not API and return confidence scores. |
| aiornot_is_liveA | Check if the AI or Not API is live. |
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 2 tools
The two tools are completely distinct: one performs media analysis and the other checks API liveness. There is no possible confusion between them.
Both tools share the consistent `aiornot_` prefix and use snake_case, but `analyze_media` is a clear verb_noun while `is_live` is a status-style name rather than an action on an object. Minor deviation in an otherwise predictable pattern.
With only two tools, the server is minimal, but the narrow purpose of wrapping the AI or Not API makes the count reasonable. It is slightly thin but not insufficient.
The analysis tool covers all supported media types (image, video, audio, text) and returns confidence scores, while the liveness tool covers API availability. For the stated purpose, there are no obvious gaps.