SEOSiri API Guard MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sanitize_and_validate_payloadC | Main Security Gatekeeper: Processes proposed payloads against universal OWASP rules and activates industry-specific compliance profiles (hipaa, pci, seo, biorobotics) dynamically. |
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
Only one tool exists, so there is no possibility of confusion with other tools. The tool's purpose is clear and distinct.
The single tool uses a clear verb_noun pattern (sanitize_and_validate_payload) in snake_case, which is consistent and descriptive.
A single tool is well-scoped for a dedicated security guard server focused on payload sanitization and validation, with no unnecessary bloat.
The tool covers the full scope of the server's purpose: both sanitization and validation with dynamic profile activation, with no obvious gaps.