vasp-mcp
Related Servers
Alternatives to vasp-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables MCP clients to explore a local War Selection installation by reading mod code, game JSON data, logs, and Lua API indexes, while also linting mods, parsing Lua log errors, diffing mod and game versions, generating scaffolds, and watching logs in real time.26MIT
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server that enables inspecting and auditing markdown agent steering files such as CLAUDE.md, AGENTS.md, GEMINI.md, SKILL.md, rules, commands and memory files. It reads files byte-exactly, outlines headings, lints frontmatter, invisible characters and broken links, estimates per-session token budgets, and locates steering files by when they load, all without ever writing, deleting or making network calls.MIT
- AlicenseCqualityBmaintenanceEnables MCP clients to inspect server state, detect an installed Questa/ModelSim simulator without launching it, and extract diagnostic messages from simulation text output. It provides a scaffold toward deterministic regression runs and waveform analysis, but does not yet execute synthesis or simulation.3Apache 2.0
- AlicenseAqualityDmaintenanceProvides read-only access to an Obsidian vault, enabling file listing, content reading, and text search across notes via MCP.42Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to browse selected folders, search filenames, inspect metadata, and read bounded UTF-8 text files through a read-only, token-authenticated interface.1MIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that lets an agent audit its own environment by discovering local MCP configurations and skill folders on Windows, macOS, and Linux and running offline static checks for prompt injection, hidden instructions, hardcoded secrets, dangerous commands, unpinned packages, and excessive filesystem or transport permissions. It exposes tools to scan everything discovered, list configurations, vet a single skill, or analyze supplied text, returning text, JSON, SARIF, or HTML findings with CI-friendly severity levels.8 npmMIT
TDQS
Scored across 5 tools
Each tool has a distinct role: input validation (check_vasp_inputs), input parsing (read_vasp_inputs), run summary (summarize_vasp_run), project scan (scan_vasp_project), and rule metadata (list_vasp_lint_rules). The only mild overlap is between check_vasp_inputs and read_vasp_inputs, but descriptions clearly separate validation from raw parsing.
All five tools follow the same verb_vasp_noun pattern (check_vasp_inputs, summarize_vasp_run, read_vasp_inputs, scan_vasp_project, list_vasp_lint_rules). The convention is uniform and predictable.
Five tools is well-scoped for a VASP analysis/validation server, with no redundant or filler tools. Each covers a clearly different stage of the workflow.
The surface covers input validation, input reading, run summarization, project scanning, and rule listing, which is solid lifecycle coverage for diagnostics. It lacks any write/fix or cross-run comparison operations, but those are outside the apparent read-only analysis scope.