portfolio-mcp (sohumsuthar/portfolio-mcp) is an MCP server listed on the M8ven Trust Index. It scores 55 out of 100, grade D. It declares 11 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
55/100

portfolio-mcp

An MCP server for managing MDX blog posts and project data with built-in Git integration for automated commits and pushes. It enables AI assistants to perform full CRUD operations on portfolio content through a standardized protocol or REST API.

→ sohumsuthar/portfolio-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code 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

sohumsuthar

Source: Glama

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 1 critical, 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 3 credentials: API_KEY, GITHUB_TOKEN, PORTFOLIO_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes11 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_posts

List all blog posts with their frontmatter

get_post

Get full content of a post by slug

create_post

Create a new blog post

update_post

Update an existing post

delete_post

Delete a post by slug

list_projects

List all projects

create_project

Create a new project

update_project

Update a project by title

delete_project

Delete a project by title

git_status

Get git status of portfolio repo

git_commit_push

Commit and push changes. First call returns dry-run, set confirmed:true to execute.

// known CVEs in dependencies1 critical1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalsimple-git@3.32.2GHSA-r275-fr43-pm7q

simple-git has blockUnsafeOperationsPlugin bypass via case-insensitive protocol.allow config key enables RCE

highsimple-git@3.32.2GHSA-hffm-xvc3-vprc

simple-git is vulnerable to Remote Code Execution

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configALLOWED_ORIGINCORS allowed origin
configAPI_HOST
🔐 secretAPI_KEYyour-secret-key
configAPI_PORT
configGITHUB_BRANCHBranch to read/write (default: main)
configGITHUB_OWNERGitHub username (default: sohumsuthar)
configGITHUB_REPORepository name (default: suthar-portfolio)
🔐 secretGITHUB_TOKENGitHub personal access token with repo scope
configGIT_BRANCH
configGIT_REMOTE
configGIT_REQUIRE_CONFIRM
configHOST
🔐 secretPORTFOLIO_API_KEY"": "your-api-key"
configPORTFOLIO_API_URL"": "https://your-deployment.vercel.app",
configPORTFOLIO_PATH/path/to/your/portfolio-repo
configPOSTS_DIRdata/posts
configPROJECTS_FILEdata/projectsData.js
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

11/11 tools missing one or more hints — list_posts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_post (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_post (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

1 critical, 1 high severity in production deps — simple-git@3.32.2 (critical), simple-git@3.32.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

1/6 production deps stale: gray-matter@2023-07-12 (3.1y)

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 5 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/sohumsuthar/portfolio-mcp?variant=verified)](https://m8ven.ai/mcp/sohumsuthar/portfolio-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 8f80cd1367eef16ebd6155ad79914882940fe53d
code hash: 2c8429e08f1ad467b6fd86e231d622c312800f45dfc07b3a6e015a00ff79439c
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