project-advisors-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_architecture_scanB | Scans workspace source files for layer boundary violations, circular dependencies, and improper coupling. Supports Python, Rust, Go, Node.js, Java, Swift (iOS), and Kotlin (Android). |
| run_rest_api_scanB | Evaluates REST endpoints/controllers for HTTP compliance, missing pagination, state-mutating GETs, raw stack traces, and unvalidated payloads. |
| run_security_scanB | Audits security configurations, hardcoded secrets/API keys, exposed management endpoints, missing CSRF tokens, and insecure permissions. |
| run_vulnerability_scanB | Checks build dependency files (package.json, pom.xml, build.gradle, Cargo.toml, requirements.txt, etc.) against known CVE databases. |
| run_pentest_scanA | Generates non-destructive exploit payloads (SQLi, XSS, JWT tampering) against configured dev environment endpoints to test input sanitization. |
| get_telemetry_streamA | Retrieves live runtime activity (memory usage, unhandled exceptions, slow queries, leak traces) received from JVM or mobile sidecar streams. |
| run_mcp_design_scanA | Verifies the design and implementation of MCP (Model Context Protocol) servers. Checks for proper tool definitions, schema validation, transport security, and proper error handling. |
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
Each tool targets a distinct concern (dependencies, endpoints, runtime telemetry, MCP design, architecture, REST APIs, security config), but some overlap exists between security scan, vulnerability scan, and pentest scan. Descriptions clarify boundaries, so misselection is unlikely but possible.
Six of seven tools follow the 'run_*_scan' pattern, which is predictable and consistent. The outlier 'get_telemetry_stream' uses a different verb and noun style, creating a minor deviation but not causing confusion.
Seven tools is well within the ideal range for a specialized scanning server. Each tool covers a distinct aspect of project advisory, and the count feels neither sparse nor bloated.
The tool surface covers the main advisory domains: dependencies, security config, architecture, REST APIs, and runtime telemetry. Minor gaps like container scanning or infrastructure checks exist, but the core workflows are well covered.