MCP Factory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NASA_API_KEY | No | API key for NASA APOD. Uses DEMO_KEY by default. |
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 |
|---|---|
| get_todays_space_photoA | Get today's Astronomy Picture of the Day from NASA. |
| get_space_photo_by_dateA | Get the Astronomy Picture of the Day for a specific date (YYYY-MM-DD). |
| get_random_space_photoA | Get a random Astronomy Picture of the Day from NASA's archives. |
| scan_codebaseA | Run a full multi-pass security and quality scan on a codebase directory. Executes all analyzers: secret detection, OWASP security patterns, debug statement detection, code quality checks, style linting, and dependency vulnerability scanning via OSV.dev. Use this when asked to review, audit, or scan a codebase for issues. |
| scan_secretsA | Scan a codebase directory for exposed secrets, API keys, and credentials. Detects AWS keys, GitHub tokens, GCP keys, Slack tokens, JWTs, private keys, database connection strings, and generic hardcoded secrets. Use this when asked to check for leaked credentials or secrets. |
| scan_security_patternsA | Scan a codebase for OWASP-style security antipatterns. Detects SQL injection vectors, XSS sinks, eval/exec usage, insecure cryptographic primitives, path traversal, insecure deserialization, and shell injection patterns. Use this when asked about security vulnerabilities or OWASP compliance. |
| scan_code_qualityA | Scan a codebase for code quality and style issues. Checks for debug/print statements, oversized files, long lines, deep nesting, too many function parameters, trailing whitespace, TODO/FIXME comments, mixed indentation, superfluous comments, and naming convention violations (PEP 8 for Python, camelCase for JS/TS). Use this when asked to check code quality, readability, or style. |
| scan_dependenciesA | Scan a project's dependency manifests for known CVEs via OSV.dev. Parses package.json, requirements.txt, pyproject.toml, go.mod, Cargo.toml, and Gemfile.lock, then queries the OSV vulnerability database for each dependency. Use this when asked to check dependencies for vulnerabilities or CVEs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| famous_space_dates | List of famous space exploration dates to explore in APOD archives. |
| owasp_top_10_reference | OWASP Top 10 (2021) quick reference for code security reviews. |
TDQS
Scored across 8 tools
The space photo tools are clearly distinct (random, specific date, today). The scanning tools are also distinct, though the comprehensive scan_codebase overlaps with the individual scanners; descriptions help clarify when to use each. The two domains are unrelated but clearly named, reducing confusion.
All tool names follow a consistent verb_noun pattern (get_*_space_photo for photos, scan_* for code scans). No mixing of conventions, making them predictable and easy to navigate.
With 8 tools across two domains, the count is well-scoped. The space photos domain has 3 tools (covers essential queries) and the scanning domain has 5 tools (comprehensive coverage without excess).
The space photo tools cover random, specific date, and today—sufficient for basic retrieval. The scanning tools cover quality, dependencies, secrets, security patterns, and a full scan, leaving few gaps. Missing features like search or description retrieval for photos are minor.