aegis-integrity
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AEGIS_DEVICE | No | PyTorch device (cpu, cuda, mps). | cpu |
| AEGIS_ENV_FILE | No | The MCP server no longer loads ./.env (only AEGIS_ENV_FILE or ~/.aegis/.env). | |
| AEGIS_INDEX_DIR | No | Persistent FAISS + MinHash index directory. | ./aegis_index |
| AEGIS_REPORT_DIR | No | Output directory for JSON/HTML reports. | ./aegis_reports |
| AEGIS_MAX_FILE_MB | No | MCP tools read only .pdf, .docx, .tex and .txt files up to 50 MB (AEGIS_MAX_FILE_MB). | 50 |
| AEGIS_ALLOWED_ROOTS | No | Set AEGIS_ALLOWED_ROOTS to confine every tool to specific folders (recommended when an agent drives AEGIS). | |
| AEGIS_CITATION_EMAIL | No | Email for Crossref polite-pool. | aegis-check@example.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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aegis_analyze_paperA | Run the full AEGIS integrity check on a paper (PDF/DOCX/TEX/TXT/MD). |
| aegis_compare_papersA | Compare two papers directly for overlap or self-plagiarism. |
| aegis_check_citationsA | Verify a paper's references against Crossref (citations module only). |
| aegis_check_guidelinesA | Fast offline style pass: equations, grammar and per-publisher guidelines. |
| aegis_index_summaryA | List the papers in the local AEGIS comparison corpus. |
| aegis_index_addA | Add a paper to the local comparison corpus for future plagiarism checks. |
| aegis_statusA | Show which AEGIS checks are ready, which are missing, and how to fix them. Call this first if a check is skipped or reports "unavailable". |
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 7 tools
The tools are mostly distinct: aegis_analyze_paper is clearly the full suite, while aegis_check_guidelines and aegis_check_citations are focused subsets. The only mild overlap is that the full analysis includes those checks, but the descriptions make the intended use cases (full vs. fast/offline) clear.
All tools use the aegis_ prefix with snake_case, which is highly consistent. There are minor pattern deviations: most tools follow verb_noun (analyze_paper, check_guidelines), but index_add and index_summary group by resource first, and aegis_status is a bare noun.
Seven tools is well-scoped for an integrity-checking server, with each tool covering a distinct workflow: full analysis, focused checks, comparison, corpus management, and diagnostics. No tool feels redundant or excessive.
The surface covers the core integrity workflow: full analysis, citations, guidelines, paper comparison, corpus indexing, listing, and status. A minor gap is corpus management: papers can be added and listed but not removed or cleared, which could become a limitation over time.