mcp-erid
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ERID_API_KEY | No | API key for Pro features (audit_batch). Optional. | |
| MCP_ERID_TIMEOUT | No | HTTP timeout in seconds. Default: 30. | |
| MCP_ERID_API_BASE | No | URL of hosted backend. Default: production URL. | |
| MCP_ERID_LOG_LEVEL | No | Logging level (DEBUG/INFO/WARNING/ERROR). Default: WARNING. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_eridA | Валидация токена erid: формат/контрольные признаки, найден ли по публичным данным, читаемость. Бесплатно. |
| audit_ad_pageA | Аудит рекламной поверхности: наличие пометки «Реклама», данных рекламодателя, привязки erid (present/absent/uncertain). Бесплатно. |
| check_compliance_38fzB | Детерминированный чек-лист соответствия 38-ФЗ по собранным признакам: вердикт ok / issues / insufficient_data. Бесплатно. |
| explain_marking_requirementA | Справка по требованиям маркировки рекламы (что такое erid/ОРД/ЕРИР, кто за что отвечает, сроки, штрафы). Бесплатно. |
| audit_batchA | Пакетная проверка размещений: таблица результатов по каждому url. Тариф Pro (MCP_ERID_API_KEY). |
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 5 tools
Each tool has a well-defined, distinct purpose: single-page audit, batch audit, compliance check, explanation of requirements, and token validation. No significant overlap exists.
All tool names use snake_case and follow a verb_noun pattern. However, two tools start with 'audit' (audit_ad_page, audit_batch), which creates slight redundancy but still clear.
With 5 tools, the server is well-scoped for its domain (advertising marking audit and compliance). Each tool adds unique functionality, neither too few nor too many.
The tool set covers core workflows: auditing (single and batch), compliance checking, reference info, and token validation. A minor gap might be the lack of a tool to search or manage erid records, but the coverage is solid for the stated purpose.