F
Warning
24/100
12 days ago

AI4S-agent-tools

Collecting a variety of Agent-Ready tool modules

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

deepmodeling

Source: github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Tool descriptions don’t match what handlers do
6 tools describe read intent but their handlers mutate — search_paper (line 93: with open(file_path, "wb") as f:); fetch_structures_with_filter (line 142: (out_folder / "summary.json").write_text(json.dumps(manifest, indent=2))); fetch_structures_with_spg (line 269: (out_folder / "summary.json").write_text(json.dumps(manifest, indent=2)))
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: OPENAI_API_KEY, GEMINI_API_KEY, GOOGLE_API_KEY, ZOTERO_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configMCP_TRANSPORT
configASKCOS_API_URL
configHMIX_DATA_PATH
configSCALER_TYPE_PATH
configSCALER_STRUC_PATH
configTYPE_MODEL_PATH
configSTRUCTURE_MODEL_PATH
configORCA
configPDB_MCP_HOST
configPDB_MCP_PORT
configZOTERO_LOCAL
configCHEMBL_MCP_HOST
configCHEMBL_MCP_PORT
configPYTHONUNBUFFERED
configABACUSAGENT_HOST
configABACUSAGENT_PORT
configABACUSAGENT_TRANSPORT
configABACUSAGENT_MODEL
configMODEL
configABACUSAGENT_WORK_PATH
🔐 secretOPENAI_API_KEY
🔐 secretGEMINI_API_KEY
🔐 secretGOOGLE_API_KEY
configZOTERO_EMBEDDING_MODEL
configOPENAI_EMBEDDING_MODEL
configGEMINI_EMBEDDING_MODEL
configZOTERO_LIBRARY_ID
configZOTERO_LIBRARY_TYPE
🔐 secretZOTERO_API_KEY
configZOTERO_PDF_MAXPAGES
configVIRTUAL_ENV
configXDG_CONFIG_HOME
configABACUS_PP_PATH
configABACUS_ORB_PATH
configBADER_EXE
configABACUSAGENT_SUBMIT_TYPE
configABACUS_COMMAND
configBOHRIUM_ABACUS_COMMAND
configBOHRIUM_ABACUS_IMAGE
configBOHRIUM_ABACUS_MACHINE
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

114/114 tools missing one or more hints — retrosynthesis_planning (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); reaction_prediction (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); single_step_retrosynthesis (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +111 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

5 tools perform destructive updates without destructiveHint — optimize_structure deletes at line 177 (Path(traj_file).unlink()); HEA_predictor deletes at line 67 (os.remove(folds_file)); generate_crystalformer_structures deletes at line 1380 (shutil.rmtree(output_path))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

6 tools describe read intent but their handlers mutate — search_paper (line 93: with open(file_path, "wb") as f:); fetch_structures_with_filter (line 142: (out_folder / "summary.json").write_text(json.dumps(manifest, indent=2))); fetch_structures_with_spg (line 269: (out_folder / "summary.json").write_text(json.dumps(manifest, indent=2)))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

109/111 tool handlers declare input schemas (98%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

85/111 tool handlers wrap calls in try/catch (77%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

8 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Tool description accuracy

6 tools have description/behavior mismatches: search_paper: description implies read-only but handler writes/deletes/executes; fetch_structures_with_filter: description implies read-only but handler writes/deletes/executes; fetch_structures_with_spg: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 9 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/deepmodeling-ai4s-agent-tools-5l0zi4?variant=verified)](https://m8ven.ai/mcp/deepmodeling-ai4s-agent-tools-5l0zi4)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 9ddc8c1c45c7c11dd456044697f59d668d42e708
code hash: b63237d027b3b00305ff4ba7d4ebdb80717e598ef2bbc2b66af7a3d0f549a1fc
verified: 8/8/2026, 7:40:51 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client