enterprise-scout-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| enterprise_collectC | Collect enterprise info. L1: prefer_tier=l1 + platform gsxt (needs GSXT session). |
| enterprise_collect_batchC | Collect multiple company keywords (comma or newline separated). |
| enterprise_searchC | Lightweight search — collect with depth=0 (same default equity fields). |
| scout_sessionsB | List unified session/cookie registry (GSXT L1, aiqicha L2, ENScan mirror). |
| sync_gsxt_sessionB | Import GSXT personal-login cookies after browser login at shiming.gsxt.gov.cn. |
| sync_enscan_cookiesC | Import aiqicha cookie and sync into ENScan_GO config.yaml. |
| scout_doctorC | Report availability of ENScan_GO, Handaas, personas; optional live sidecar probe. |
| scout_sidecarsB | Live-probe ENScan_GO and proxy_pool sidecars. |
| scout_import_neo4jC | Import warehouse parquet into Neo4j (dry_run=True counts rows only). |
| scout_drain_retryC | Re-run captcha/failed jobs from raw/retry_queue; archive on success. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
enterprise_collect, enterprise_collect_batch, and enterprise_search overlap significantly — search is explicitly described as 'collect with depth=0', so an agent may struggle to pick the right entry point. scout_doctor and scout_sidecars also both probe sidecar availability with unclear boundaries, while the sync_* tools are distinct.
Two inconsistent prefixes (enterprise_* vs scout_*) are mixed with two verb styles: action-oriented names (enterprise_collect, sync_gsxt_session) coexist with noun-style names (scout_sessions, scout_doctor, scout_sidecars). Still readable, but no single predictable pattern.
Ten tools is a reasonable, well-scoped set for an enterprise collection pipeline covering collection, sessions, diagnostics, and export. Slightly heavy given that collect/search/batch and doctor/sidecars duplicate intent.
The surface covers collection, batch, search, session management, diagnostics, Neo4j import, and retry/drain, forming a coherent pipeline. Minor gaps exist around inspecting or deleting already-collected warehouse data and no explicit export/reporting operation.