# Phaedrus (mcpb · linux-x64)

Research-feed MCP server: literature-watch findings, watchlist, and revenue-candidate drafts.

- Trust score: 27/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- mcpb · `linux-x64`: 27/100 (this document), [markdown](https://verifymcp.io/servers/ai-qompass-phaedrus/phaedrus-mcp-linux-x64.md), [page](https://verifymcp.io/servers/ai-qompass-phaedrus/phaedrus-mcp-linux-x64)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/qompassai/phaedrus/releases/download/v0.1.0/phaedrus-mcp-0.1.0-linux-x64.mcpb`
- Transport: `stdio`
- SHA-256: `4c8abf6cfdfd7ab20e91a343f488a0a83bfc41a7b9f25e8e3b1e7350d99b6fb4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 33/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 266 tokens (~26/item across 10 items; 7 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Phaedrus MCP server?

Phaedrus ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 4c8abf6cfdfd7ab20e91a343f488a0a83bfc41a7b9f25e8e3b1e7350d99b6fb4; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/qompassai/phaedrus/releases/download/v0.1.0/phaedrus-mcp-0.1.0-linux-x64.mcpb`
- SHA-256: `4c8abf6cfdfd7ab20e91a343f488a0a83bfc41a7b9f25e8e3b1e7350d99b6fb4`

### Verify on macOS / Linux

```bash
echo "4c8abf6cfdfd7ab20e91a343f488a0a83bfc41a7b9f25e8e3b1e7350d99b6fb4  phaedrus-mcp-0.1.0-linux-x64.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\phaedrus-mcp-0.1.0-linux-x64.mcpb).Hash -eq "4c8abf6cfdfd7ab20e91a343f488a0a83bfc41a7b9f25e8e3b1e7350d99b6fb4"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-21 (score 27)

First indexed and scored.

## MCP tools (7)

### `finding_list` (~24 tokens)

List curated findings, optionally filtered by system.

Input parameters:

- `system` (string)

### `finding_get` (~22 tokens)

Get one curated finding by id.

Input parameters:

- `id` (string, required)

### `research_submit` (~73 tokens)

File a CANDIDATE (finding, roadmap item, or test proposal) into the scan inbox. Never writes the curated store; Pax validates.

Input parameters:

- `kind` (string, required)
- `source` (string, required)
- `summary` (string, required)
- `system` (string, required)
- `title` (string, required)

### `watchlist_list` (~27 tokens)

List the watchlist (per-system venues and terms).

Input parameters:

- `system` (string)

### `capability_context` (~39 tokens)

Read lupin's capability registry (read-only) as planning vocabulary: capability ids + names, optionally keyword-filtered.

Input parameters:

- `query` (string)

### `revenue_candidate_draft` (~43 tokens)

Draft a lupin opportunity_submit payload for a revenue-shaped finding. Drafts only — this server never writes lupin's files.

Input parameters:

- `id` (string, required)

### `feed_summary` (~22 tokens)

Counts: findings by system/kind, systems watched, parse health.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/ai-qompass-phaedrus/phaedrus-mcp-linux-x64#diagnostics

## Score history

- 2026-10-24: 27
- 2026-10-23: 27
- 2026-10-22: 27
- 2026-10-21: 27

## Common questions

### What is the Phaedrus MCP server?

Phaedrus is an MCP server listed in the public MCP registry as ai.qompass/phaedrus. Research-feed MCP server: literature-watch findings, watchlist, and revenue-candidate drafts. This page covers its MCPB bundle (https://github.com/qompassai/phaedrus/releases/download/v0.1.0/phaedrus-mcp-0.1.0-linux-x64.mcpb).

### Is the Phaedrus MCP server safe to use?

Phaedrus scores 27 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Phaedrus MCP server expose?

Phaedrus exposes 7 tools: finding_list, finding_get, research_submit, watchlist_list, capability_context, and 2 more. Their descriptions and schemas cost roughly 250 tokens of context every time the server is loaded.

### What licence is the Phaedrus MCP server under?

Phaedrus declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/qompassai/phaedrus
- Website: https://qompass.ai/solutions/phaedrus/
- Changelog RSS feed: https://verifymcp.io/servers/ai-qompass-phaedrus/phaedrus-mcp-linux-x64.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-qompass-phaedrus/phaedrus-mcp-linux-x64.json
- HTML version of this page: https://verifymcp.io/servers/ai-qompass-phaedrus/phaedrus-mcp-linux-x64