Friday Ai Codes MCP Server

@friday-ai-codes/mcp npm v0.6.0 Source verified

Published by friday-ai-codes — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Friday AI MCP server — expose Friday code intelligence, Graph RAG, coding plan and MR tools to Cursor / Claude Code / Codex via Model Context Protocol

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Shell/command execution in server code (dist/cli.js)MTC-SRC-002

In the server's implementation (`dist/cli.js:7`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ecFileSync } from "node:child_process"; import { Server } from "@modelcontextprotocol/sdk/server/index.js"; import { Std

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli.js

Tools 42

Each tool and what it can reach — statically extracted from the published source.

  • read_project_docingests untrusted input
  • analyze_repositoryno sensitive capability
  • answer_blueprint_clarificationno sensitive capability
  • apply_repo_associationno sensitive capability
  • confirm_feature_tech_planno sensitive capability
  • create_coding_planno sensitive capability
  • create_feature_tech_planno sensitive capability
  • create_feishu_technical_planno sensitive capability
  • create_learning_caseno sensitive capability
  • create_merge_requestno sensitive capability
Show 32 more tools ↓
  • create_work_item_repo_tasksno sensitive capability
  • execute_coding_planno sensitive capability
  • execute_work_item_repo_tasksno sensitive capability
  • find_related_chunksno sensitive capability
  • generate_requirement_specno sensitive capability
  • get_coding_executionno sensitive capability
  • get_entity_timelineno sensitive capability
  • get_feature_tech_planno sensitive capability
  • get_feishu_work_item_contextno sensitive capability
  • get_related_entitiesno sensitive capability
  • get_repo_researchno sensitive capability
  • get_repositoryno sensitive capability
  • get_repository_fileno sensitive capability
  • get_technical_blueprintno sensitive capability
  • grep_projectno sensitive capability
  • grep_repositoryno sensitive capability
  • improve_coding_planno sensitive capability
  • list_repository_filesno sensitive capability
  • lookup_project_by_branchno sensitive capability
  • read_blueprint_contextno sensitive capability
  • report_blueprint_contextno sensitive capability
  • report_project_knowledgeno sensitive capability
  • report_project_stateno sensitive capability
  • reverse_lookup_requirementsno sensitive capability
  • route_blueprint_reposno sensitive capability
  • route_repositoriesno sensitive capability
  • search_delivery_knowledgeno sensitive capability
  • search_learning_casesno sensitive capability
  • search_project_contextno sensitive capability
  • search_rag_chunksno sensitive capability
  • start_repo_researchno sensitive capability
  • summarize_branchno sensitive capability

What this scan could not see

Versions 5

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.6.0 latest A 94/100 1 1.13.0 2026-09-07
v0.5.0 A 94/100 1 1.13.0 2026-09-01
v0.4.0 A 94/100 1 1.12.1 2026-08-01
v0.3.0 A 94/100 1 1.10.0 2026-07-25
v0.2.0 A 100/100 1 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/friday-ai-codes-mcp/badge.svg)](https://mcptrustchecker.com/registry/friday-ai-codes-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/friday-ai-codes-mcp"><img src="https://mcptrustchecker.com/registry/friday-ai-codes-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/friday-ai-codes-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @friday-ai-codes/mcp --online

Use the free API → How scoring works

More in AI, Memory & Reasoning