What Python version is required?
Python 3.6 or higher is required.
@Sumedh1599
Basic information
Analyzes user-described build features (e.g. database, API integration, tools) and extracts core server requirements like resources, tools, prompts, external systems, and transports needed for MCP.
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
mcp_input_analyzer is an open-source Python library that analyzes user‑described build features (databases, API integrations, tools) and extracts core server requirements—such as resources, tools, prompts, external systems, and transports—for MCP (Microservices Configuration Platform). It converts free‑form text descriptions into structured, MCP‑compliant input definitions.
Install via pip: pip install mcp-input-analyzer (requires Python 3.6+). Import the MCPAnalyzer class, initialize it with a description string and optional fallback_behavior parameter, then call methods like extract_requirements(), generate_mcp_structure(), or create_claude_json() to obtain the desired output.
Python 3.6 or higher is required.
Install via pip: `pip install mcp-input-analyzer`. Alternatively, clone the repository and run `pip install .` from the source directory.
It can output a dictionary of structured server requirements (`extract_requirements()`), an MCP‑compliant input structure (`generate_mcp_structure()`), or a Claude‑readable JSON definition (`create_claude_json()`).
Yes, it includes fallback logic. The `MCPAnalyzer` constructor accepts a `fallback_behavior` parameter (default or custom) to control how unsupported features are handled.
No. The library is currently in early development and some tests may be failing. Contributions to fix issues are welcome.

Remote MCP server for domain and website checks: DNS, WHOIS/RDAP, domain age, TLS, DNSSEC, email auth (SPF/DKIM/DMARC), blocklists, a trust verdict ("should my agent click, sign in to, or pay this site?"), availability +
Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

Throw HTML at an API, get an unguessable URL back. Zero-config remote MCP server — your agent deploys pages, sites and CI reports in one call. Free, no signup needed.

The 9apes MCP server lets an AI assistant read the GitHub Actions data 9apes already collects for your organization: runs, jobs, steps, and their durations. Ask it why a build got slower, which jobs take the longest, or

Compliance frameworks delivered to AI agents. Nizh gives your agent read access to your organization's compliance program — SOC 2, ISO 27001, CMMC 2.0, NIST, and more — as MCP tools, so it can check posture, read a contr
Comments