MCP Project Assistant Framework (wissaltaj18/mcp-project-assistant-framework) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 26 tools. No publisher has claimed this listing.

C
Emerging
74/100

MCP Project Assistant Framework

Generates project features (HTML pages, backend APIs) from prompts and project-specific business rules stored as resources, with support for interchangeable LLM providers (local Ollama or cloud Gemini).

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

wissaltaj18

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 →

Install from

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
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 4 credentials: JIRA_API_TOKEN, SONAR_TOKEN, SONAR_PROJECT_KEY, ANTHROPIC_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes26 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.

read_project_resource

Lit une Resource (.md) d'un projet généré.

list_project_resources

Liste les Resources disponibles pour un projet.

list_available_prompts

Liste les prompts de génération actuellement disponibles.

generate_feature

Génère du code pour une fonctionnalité via le LLM configuré.

create_workspace

Crée un nouveau Workspace à partir d'un dépôt Git.

set_active_workspace

Active un Workspace déjà créé.

generate_resources

Génère les Resources d'un Workspace depuis son analyse d'architecture.

index_workspace

Indexe le code d'un Workspace dans sa base vectorielle (RAG).

prepare_workspace

Workflow complet : clone, active, génère les Resources, indexe.

update_resource

Modifie une Resource existante d'un Workspace.

set_preference

Définit une préférence de workflow pour un Workspace.

check_existing_feature

Vérifie si une fonctionnalité liée existe DÉJÀ dans le code.

read_file

Lit le contenu réel d'un fichier du Workspace actif.

get_project_structure

Renvoie l'arborescence réelle des fichiers du Workspace actif.

find_project_file

Cherche un fichier du Workspace actif par son nom.

run_tests

Exécute réellement la suite de tests du Workspace actif.

create_plan

SEULE façon de proposer une modification. Calcule et fige le contenu exact de chaque étape, attend l'approbation via approve_plan.

approve_plan

APPROUVE et EXÉCUTE RÉELLEMENT un plan proposé par create_plan.

reject_plan

Rejette un plan proposé -- aucune exécution n'a lieu.

read_jira_ticket

Lit un ticket Jira et retourne son contenu complet.

add_jira_comment

Ajoute un commentaire sur un ticket Jira.

update_jira_status

Change le statut d'un ticket Jira (ex: 'En cours', 'Terminé').

download_jira_attachment

Télécharge une pièce jointe d'un ticket Jira dans le dossier public/ du Workspace.

get_sonar_report

Récupère le rapport SonarCloud : Quality Gate, bugs, vulnérabilités, couverture.

sync_workspace

Synchronise le Workspace avec GitHub via git pull.

get_git_diff

Retourne le résumé des fichiers modifiés dans le dernier commit.

// 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.
configJIRA_BASE_URL
configJIRA_EMAIL
🔐 secretJIRA_API_TOKEN
configOLLAMA_MODEL
configOLLAMA_BASE_URL
configLLM_TIMEOUT_SECONDS
configGEMINI_MODEL
configGENERATED_PROJECTS_DIR
configACTIVE_LLM_PROVIDER
configSONAR_BASE_URL
🔐 secretSONAR_TOKEN
configSONAR_ORGANIZATION
🔐 secretSONAR_PROJECT_KEY
🔐 secretANTHROPIC_API_KEY
// 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

26/26 tools missing one or more hints — read_project_resource (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_project_resources (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_available_prompts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +23 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.).

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 3 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 Score](https://m8ven.ai/badge/mcp/wissaltaj18/mcp-project-assistant-framework)](https://m8ven.ai/mcp/wissaltaj18/mcp-project-assistant-framework)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e813a2df46e59d5c7fddf341bdc1c6e045295a47
code hash: 9472770b91620721a864ba1ccb92c0aaf5e75509cf4b621b6ab4d65bd6e6d9d2
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