APIMatic Validator MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIMATIC_API_KEY | Yes | Your APIMatic API key for validating OpenAPI specifications |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate-openapi-using-apimaticC | Get validation summary for your OpenAPI spec using APIMatic |
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 ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name follows a clear verb-noun pattern (validate-openapi-using-apimatic).
A single tool is too few for a server focused on OpenAPI validation, as it lacks coverage for related operations like detailed error reporting, schema linting, or batch validation. This minimal set limits agent workflows and feels incomplete for the domain.
The tool surface is severely incomplete for OpenAPI validation. It only provides a summary validation, missing essential functions such as retrieving detailed validation errors, checking specific API endpoints, or supporting different OpenAPI versions, which are common needs in this domain.