Conviction Fm MCP Server

conviction-fm npm v0.4.0

Published by abcxz — 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.

Trust grade
D
63/100
Last scanned
Trust
D · 63/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
Moderate
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.
D Why this grade threat 67 − adoption risk = 63/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 − 33 = 67. What the published surface and source actually contain:

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

2. Client adoption risk — 67 − 4 = 63. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable
inspection depth (source) — how much of the target the scan could see

Grade capped: 2 confirmed high findings → grade capped at D. 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 3

high Hardcoded JSON Web Token in server code (bin/cli.mjs)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `bin/cli.mjs:285`. 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 bin/cli.mjs

high Hardcoded JSON Web Token in server code (lib/api.mjs)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `lib/api.mjs:7`. 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 lib/api.mjs

medium Hardcoded egress to an external endpoint (bin/cli.mjs)MTC-SRC-003

In the server's implementation (`bin/cli.mjs:283`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://gbbiwhismttjuhzetzrm.supabase.co/functions/v1/withdraw-agent-funds'

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 bin/cli.mjs

What this scan could not see

Versions

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.4.0 latest D 63/100 3 1.7.0 2026-07-23

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

Use the free API → How scoring works

More in Gaming & Entertainment