Gds Agent MCP Server
gds-agent
PyPI
v1.0.1
Published by neo4j-contrib — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
| ✓ | inspection depth (source) — how much of the target the scan could see |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Shell/command execution in packaging/dev tooling (tests/conftest.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/conftest.py:25`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: subprocess.run(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/conftest.py
Tools 71
Each tool and what it can reach — statically extracted from the published source.
a_star_shortest_pathno sensitive capabilityall_pairs_shortest_pathsno sensitive capabilityapproximate_maximum_k_cutno sensitive capabilityarticle_rankno sensitive capabilityarticulation_pointsno sensitive capabilitybellman_ford_single_source_shortest_pathno sensitive capabilitybetweenness_centralityno sensitive capabilitybreadth_first_searchno sensitive capabilitybridgesno sensitive capabilityCELFno sensitive capabilitycloseness_centralityno sensitive capabilityconductanceno sensitive capabilitycreate_sessionno sensitive capabilitydegree_centralityno sensitive capabilitydelete_sessionno sensitive capabilitydelta_stepping_shortest_pathno sensitive capabilitydepth_first_searchno sensitive capabilitydijkstra_single_source_shortest_pathno sensitive capabilitydrop_graphno sensitive capabilitydrop_modelno sensitive capabilityeigenvector_centralityno sensitive capabilityfast_rpno sensitive capabilityfind_shortest_pathno sensitive capabilityget_graph_infono sensitive capabilityget_node_labelsno sensitive capabilityget_node_properties_keysno sensitive capabilityget_relationship_properties_keysno sensitive capabilityget_relationship_typesno sensitive capabilitygraph_sage_predictno sensitive capabilitygraph_sage_trainno sensitive capabilityharmonic_centralityno sensitive capabilityhashgnnno sensitive capabilityHDBSCANno sensitive capabilityHITSno sensitive capabilityk_1_coloringno sensitive capabilityk_core_decompositionno sensitive capabilityk_means_clusteringno sensitive capabilityk_nearest_neighborsno sensitive capabilitylabel_propagationno sensitive capabilityleidenno sensitive capabilitylist_graphsno sensitive capabilitylist_modelsno sensitive capabilitylist_sessionsno sensitive capabilitylocal_clustering_coefficientno sensitive capabilitylongest_pathno sensitive capabilitylouvainno sensitive capabilitymax_flowno sensitive capabilityminimum_directed_steiner_treeno sensitive capabilityminimum_weight_spanning_treeno sensitive capabilitymodularity_metricno sensitive capabilitymodularity_optimizationno sensitive capabilitynode_similarityno sensitive capabilitynode2vecno sensitive capabilitypagerankno sensitive capabilitypredict_link_predictionno sensitive capabilitypredict_node_classificationno sensitive capabilitypredict_node_regressionno sensitive capabilityprize_collecting_steiner_treeno sensitive capabilityproject_graph_cypherno sensitive capabilityrandom_walkno sensitive capabilityspeaker_listener_label_propagationno sensitive capabilitystream_node_propertiesno sensitive capabilitystream_relationship_propertiesno sensitive capabilitystream_relationshipsno sensitive capabilitystrongly_connected_componentsno sensitive capabilitytrain_link_prediction_modelno sensitive capabilitytrain_node_classification_modelno sensitive capabilitytrain_node_regression_modelno sensitive capabilitytriangle_countno sensitive capabilityweakly_connected_componentsno sensitive capabilityyens_shortest_pathsno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (71 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.1 latest |
A 93/100 | 1 | 1.8.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan gds-agent --online --registry pypiMore in Learning & Documentation
Security scan results for the Agentmail MCP server.
Security scan results for the Alfahq MCP server.
Security scan results for the Alpine MCP server.
Security scan results for the Atag MCP server.
Security scan results for the Aurais Mcp Research Reader MCP server.
Security scan results for the Bookstack MCP server.