Secret MCP
NPM · SECRET-DESIGN-MCP · SCANNED SEP 20
Local MCP server for isolated, evidence-backed GDWEB design analysis and web search.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects sanitize-html 2.17.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 42 of 183 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 28 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 873 tokens (~174/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Secret MCP server?
Secret MCP runs locally as an npm package, launched with npx -y secret-design-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · secret-design-mcp
claude mcp add yyeongjin-secret-mcp -- npx -y secret-design-mcp
{
"mcpServers": {
"yyeongjin-secret-mcp": {
"command": "npx",
"args": [
"-y",
"secret-design-mcp"
]
}
}
} {
"servers": {
"yyeongjin-secret-mcp": {
"command": "npx",
"args": [
"-y",
"secret-design-mcp"
]
}
}
} codex mcp add yyeongjin-secret-mcp -- npx -y secret-design-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yyeongjin-secret-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"secret-design-mcp"
],
"enabled": true
}
}
} openclaw mcp add yyeongjin-secret-mcp --command npx --arg -y --arg secret-design-mcp
mcp_servers:
yyeongjin-secret-mcp:
command: "npx"
args: ["-y", "secret-design-mcp"] {
"McpServers": {
"yyeongjin-secret-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"secret-design-mcp"
]
}
}
} assistant mcp add yyeongjin-secret-mcp -t stdio -c npx -a -y secret-design-mcp
{
"mcpServers": {
"yyeongjin-secret-mcp": {
"command": "npx",
"args": [
"-y",
"secret-design-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
- CVE-2026-63670 affects this package: medium ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/secret-design-mcp@0.6.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g8qq-57p8-ggw5 | CVE-2026-84371 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-jxwj-j7wr-gfrw | CVE-2026-63670 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 183 packages
| Packages resolved | 183 |
|---|---|
| Deprecated | 1 |
| Stale | 42 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
full-web-search ~153
Search the web and fetch complete page content from top results. This is the most comprehensive web search tool. It searches the web and then follows the resulting links to extract their full page content, providing the most detailed and complete information available. Use get-web-search-summaries for a lightweight alternative.
| Name | Type | Req | Description |
|---|---|---|---|
| includeContent | boolean|string | – | Whether to fetch full page content (default: true) |
| limit | number|string | – | Number of results to return with full content (1-10) |
| maxContentLength | number|string | – | Maximum characters per result content (0 = no limit). Usually not needed - content length is automatically optimized. |
| query | string | yes | Search query to execute (recommended for comprehensive research) |
No output schema declared.
No examples provided.
generate-gdweb-design-indexes ~325
Automatically use this tool when the user asks to find GDWEB references and create layout analysis, frontend specifications, implementation plans, or DESIGN_INDEX files. This tool applies the dashboard-managed exclusion list, performs the GDWEB search internally, and sends one completely separate MCP sampling/createMessage request per non-excluded result. Each isolated request contains only one result and has no previous-result context. It writes one page-by-page, measurement-first DESIGN_INDEX_gdweb-<strNo>.md file before starting the next request, then returns only file paths and statuses to the calling LLM. Never replace this tool with search-gdweb-designs plus a combined summary. The connected MCP client must support sampling.
| Name | Type | Req | Description |
|---|---|---|---|
| awardOnly | boolean|string | – | Whether to require a non-empty GDWEB award field |
| includePreviousYear | boolean|string | – | Whether to include the previous year |
| language | string | – | Language for every generated document. Defaults to English; choose Korean for Korean output. |
| limit | number|string | – | Number of isolated result requests and output documents (1-10) |
| maxTokens | number|string | – | Per-work output budget for a complete multi-page specification (131,072-262,144 tokens; default 131,072) |
| outputDirectory | string | – | Directory for generated DESIGN_INDEX files. Defaults to DESIGN_INDEX_OUTPUT_DIR or ./design-index. |
| query | string | yes | Natural-language design query to search directly on GDWEB |
| year | number|string | – | Target award/registration year. Defaults to the current runtime year. |
No output schema declared.
No examples provided.
get-single-web-page-content ~105
Extract and return the full content from a single web page URL. This tool follows a provided URL and extracts the main page content. Useful for getting detailed content from a specific webpage without performing a search.
| Name | Type | Req | Description |
|---|---|---|---|
| maxContentLength | number|string | – | Maximum characters for the extracted content (0 = no limit, undefined = use default limit). Usually not needed - content length is automatically optimized. |
| url | string | yes | The URL of the web page to extract content from |
No output schema declared.
No examples provided.
get-web-search-summaries ~94
Search the web and return only the search result snippets/descriptions without following links to extract full page content. This is a lightweight alternative to full-web-search for when you only need brief search results. For comprehensive information, use full-web-search instead.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number|string | – | Number of search results to return (1-10) |
| query | string | yes | Search query to execute (lightweight alternative) |
No output schema declared.
No examples provided.
search-gdweb-designs ~196
Use this tool only when the user wants a lightweight list of GDWEB references. It applies the dashboard-managed exclusion list before returning results, returns metadata for multiple results, and does not generate implementation documents. For layout analysis, frontend specifications, DESIGN_INDEX files, or implementation planning, use generate-gdweb-design-indexes instead so every result is processed by a separate isolated LLM request.
| Name | Type | Req | Description |
|---|---|---|---|
| awardOnly | boolean|string | – | Whether to require a non-empty GDWEB award field. Defaults to true. |
| includePreviousYear | boolean|string | – | Whether to include the previous year in addition to the target year. Defaults to true. |
| limit | number|string | – | Number of GDWEB design results to return (1-10) |
| query | string | yes | Natural-language design reference query to search directly on GDWEB |
| year | number|string | – | Target award/registration year. Defaults to the current runtime year. |
No output schema declared.
No examples provided.
What is the Secret MCP server?
Secret MCP is listed in the public MCP registry as io.github.yyeongjin/secret-mcp. Local MCP server for isolated, evidence-backed GDWEB design analysis and web search. This page covers its npm package (secret-design-mcp).
Is the Secret MCP server safe to use?
Secret MCP scores 80 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Secret MCP server expose?
Secret MCP exposes 5 tools: full-web-search, search-gdweb-designs, generate-gdweb-design-indexes, get-web-search-summaries, get-single-web-page-content. Their descriptions and schemas cost roughly 873 tokens of context every time the server is loaded.
Is the Secret MCP server still maintained?
Secret MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Secret MCP server under?
Secret MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.