@securityreviewai/security-review-mcp 0.2.10 → 0.2.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,7 +4,7 @@ TypeScript MCP server for [SecurityReview.ai](https://securityreview.ai), publis
|
|
|
4
4
|
|
|
5
5
|
- Pure Node runtime (no Python bootstrap)
|
|
6
6
|
- Stdio MCP server compatible with Cursor, Windsurf, Claude Desktop, ChatGPT MCP, and other MCP clients
|
|
7
|
-
-
|
|
7
|
+
- 54 tools for project/document/review/workflow/integration operations
|
|
8
8
|
- 8 built-in security-analysis prompts
|
|
9
9
|
- 4 read-only MCP resources
|
|
10
10
|
|
|
@@ -108,7 +108,7 @@ Compatibility flags (no-op, retained for older configs):
|
|
|
108
108
|
- `--python <path>`
|
|
109
109
|
- `--force-install`
|
|
110
110
|
|
|
111
|
-
## Tool Catalog (
|
|
111
|
+
## Tool Catalog (54)
|
|
112
112
|
|
|
113
113
|
### Projects
|
|
114
114
|
|
|
@@ -130,6 +130,7 @@ Compatibility flags (no-op, retained for older configs):
|
|
|
130
130
|
| `get_project_profile_security_control` | Get one security control by ID |
|
|
131
131
|
| `list_profile_compliance_requirements` | List compliance requirements in project profile |
|
|
132
132
|
| `get_profile_compliance_requirement` | Get one compliance requirement by ID |
|
|
133
|
+
| `update_vibe_project_profile` | Push/update vibe profile data (architecture notes, tech categories, user groups, compliance requirements, language stacks, description) by project ID |
|
|
133
134
|
|
|
134
135
|
### Documents
|
|
135
136
|
|
|
@@ -232,7 +233,13 @@ Compatibility flags (no-op, retained for older configs):
|
|
|
232
233
|
4. `start_workflow`
|
|
233
234
|
5. `get_workflow_status`
|
|
234
235
|
|
|
235
|
-
### 3)
|
|
236
|
+
### 3) Populate a Project Profile from Vibe/AI Context
|
|
237
|
+
|
|
238
|
+
1. `create_project` (or resolve with `find_project_by_name`)
|
|
239
|
+
2. `update_vibe_project_profile` — supply any combination of `architecture_notes`, `tech_categories`, `user_groups`, `compliance_requirements`, `language_stacks`, and `description`
|
|
240
|
+
3. `get_full_project_profile` — verify the updated profile
|
|
241
|
+
|
|
242
|
+
### 4) Bring in Jira/Confluence Context
|
|
236
243
|
|
|
237
244
|
1. `fetch_jira_issue` or `fetch_confluence_page`
|
|
238
245
|
2. `link_external_document` or `fetch_and_link_to_srai`
|