{"id":"pubchempy-mcp-server","name":"pubchempy-mcp-server","homepage":"https://pypi.org/project/pubchempy-mcp-server/","repo_url":null,"category":"ai-ml","subcategories":[],"tags":["ai-ml","mcp","pubchem","chemistry","tooling","data-enrichment"],"what_it_does":"pubchempy-mcp-server is an MCP server wrapper for PubChemPy, exposing PubChem-related operations as MCP tools so an agent can query/lookup chemical information via the MCP protocol.","use_cases":["Agentic workflows that need PubChem lookups (compound name/CID search, property retrieval).","Enriching chemical datasets with PubChem metadata.","Building internal research assistants that query chemical identifiers and properties."],"not_for":["High-throughput production ingestion pipelines without explicit rate-limit/backoff strategy.","Use cases requiring strong guarantees on data provenance/versioning beyond what PubChem provides.","Security-sensitive environments where outbound access to PubChem cannot be controlled/monitored."],"best_when":"You want to integrate PubChemPy capabilities into an MCP-compatible agent with minimal custom plumbing, and you can run/trust the MCP server deployment.","avoid_when":"You need strict SLAs, documented retry/idempotency semantics, or the package is deployed without observing/handling upstream rate limits from PubChem.","alternatives":["Use PubChemPy directly in your app/agent (Python).","Call PubChem PUG REST directly (HTTP) with your own client + retry/backoff.","Use other chemical identifier/property APIs (where available) with better enterprise controls."],"af_score":48.5,"security_score":43.0,"reliability_score":30.0,"package_type":"mcp_server","discovery_source":["pypi"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:47:43.868570+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"No package-specific auth details were provided. MCP deployments often run locally or behind your own access controls; upstream PubChem usage typically does not require OAuth-style auth for basic requests."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; assumes no commercial hosting cost beyond your own infrastructure and PubChem usage constraints."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":48.5,"security_score":43.0,"reliability_score":30.0,"mcp_server_quality":62.0,"documentation_accuracy":45.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":90.0,"rate_limit_clarity":20.0,"tls_enforcement":70.0,"auth_strength":30.0,"scope_granularity":10.0,"dependency_hygiene":50.0,"secret_handling":60.0,"security_notes":"Security depends heavily on how the MCP server is deployed (network exposure, TLS termination, logging). Auth/scope controls are likely minimal or external to the MCP server. Upstream calls to PubChem should be performed with outbound network controls and care to avoid logging sensitive query data.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":50.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Upstream PubChem endpoints may impose rate limits; MCP wrapper behavior and backoff strategy may not be documented.","Large result sets may require pagination/limits; the MCP tool contract may not expose fine-grained control.","Network timeouts or transient upstream failures may surface as tool errors without clear retry guidance."]}}