Ai Briefing MCP Server

@pipeworx/mcp-ai-briefing npm v0.1.0

Published by @pipeworx — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

AI Briefing MCP — Keep AI models current on industry developments

Trust grade
C
77/100
Last scanned get badge →
Trust
C · 77/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
Minimal
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
C Why this grade threat 78 − adoption risk = 77/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 − 22 = 78. What the published surface and source actually contain:

PointsWhat was foundCategory
−22 Hardcoded JSON Web Token in server code MTC-SRC-008 exfiltration

2. Client adoption risk — 78 − 1 = 77. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

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 Hardcoded JSON Web Token in server code (src/index.ts)MTC-SRC-008

A hardcoded JSON Web Token (a Supabase service_role key (full-access credential)) appears in `src/index.ts:34`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: JSON Web Token: eyJh…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server src/index.ts

What this scan could not see

Versions 1

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.1.0 latest C 77/100 1 1.13.0 2026-09-07

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: C · 77/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/pipeworx-mcp-ai-briefing/badge.svg)](https://mcptrustchecker.com/registry/pipeworx-mcp-ai-briefing)
HTML
<a href="https://mcptrustchecker.com/registry/pipeworx-mcp-ai-briefing"><img src="https://mcptrustchecker.com/registry/pipeworx-mcp-ai-briefing/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/pipeworx-mcp-ai-briefing/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 @pipeworx/mcp-ai-briefing --online

Use the free API → How scoring works

More in Web, Search & Scraping