Yasin-MCP
Server 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
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 22 tools
The domain prefixes make docs, GitHub, registry, and governance tools easy to separate, and most operations target a clear resource. However, yasin_docs_list_architecture and yasin_docs_get_project_architecture are easy to confuse, and yasin_docs_search overlaps somewhat with yasin_docs_list_documents.
Nearly all tools follow a yasin_<domain>_<verb>_<resource> pattern with consistent list_/get_ prefixes. Exceptions like yasin_docs_search, yasin_gov_ping_low_risk, and yasin_gov_apply_mark break the verb convention, though the domain prefixes keep the overall scheme readable.
At 22 tools, the server sits in the heavy range and spans four distinct domains, making the surface feel larger than necessary. It is not extreme, but several similar read-only GitHub and docs tools make the count feel slightly bloated.
The server covers a broad read-only surface for docs, GitHub, registry, and governance, but it lacks write/update/delete operations and some get-by-id counterparts for list-only resources like commits and workflow runs. This leaves notable gaps if the server is intended to support end-to-end documentation or repository workflows.