# Manpage MCP (remote · manpage.ai)

Search and read Linux manual pages with version-aware lookup and exact package provenance.

- Trust score: 67/100 (medium)
- Change this week: −8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `manpage.ai`: 67/100 (this document), [markdown](https://verifymcp.io/servers/ai-manpage-mcp/manpage.md), [page](https://verifymcp.io/servers/ai-manpage-mcp/manpage)

## Channel facts

- Endpoint: `https://manpage.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-17.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 496 tokens (~165/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 14 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions.
- **Tool Coverage**: 71/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.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

Manpage MCP is a hosted endpoint at https://manpage.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-manpage-mcp 'https://manpage.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-manpage-mcp": {
      "url": "https://manpage.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-manpage-mcp": {
      "type": "http",
      "url": "https://manpage.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-manpage-mcp]
url = "https://manpage.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-manpage-mcp": {
      "type": "remote",
      "url": "https://manpage.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-manpage-mcp --url 'https://manpage.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-manpage-mcp:
    url: "https://manpage.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-manpage-mcp": {
      "Transport": "http",
      "Url": "https://manpage.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-manpage-mcp -t streamable-http -u 'https://manpage.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-manpage-mcp": {
      "type": "http",
      "url": "https://manpage.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-13 (score 67, −9)

- [security regression] Stability: 0.30 → fail
- [security regression] Tool “get_man_page” was removed
- [security regression] Tool “give_feedback” was removed
- [security regression] Tool “list_targets” was removed
- [security regression] Tool “search_man_pages” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] The server changed its declared name: manpage-mcp → manpage
- [functional regression] Tool coverage: 100% → 0%
- [functional regression] Tool coverage: 100% → 67%
- [functional regression] Schema quality: pass → fail
- [functional improvement] Schema quality: 441 → 165
- [functional] Schema quality: excellent → good
- [functional] Server version: 1.30.0 → 2.14.7
- [functional] New tool “get_manual”
- [functional] New tool “get_targets”
- [functional] New tool “search”

### 2026-10-12 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 75, +2)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 23. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-05 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-04 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-03 (score 72)

First indexed and scored.

## MCP tools (3)

### `get_targets` (~55 tokens)

List indexed distribution/release/repository/architecture scopes and counts.

Use the returned values verbatim; targets such as CentOS 8, EPEL 9 or
Fedora 43 are available only if they have been indexed.

Output parameters:

- `items` (array)

### `search` (~168 tokens)

Search manual text/metadata; return ranked hits, snippets and exact identities.

Latest indexed package versions are used unless package_version is supplied.
Omitted scope filters include all indexed distributions and releases.
Supply query for relevance-ranked text search, or manual_name without query
for name/alias lookup with Fedora-preferred recommendations and case-insensitive fallback.
Pass next_cursor with identical arguments for the next live page; results
can shift as indexing progresses. Filters are exact and case-sensitive.

Input parameters:

- `architecture`
- `cursor`
- `distribution`
- `limit` (integer)
- `locale` (string)
- `manual_name`
- `package`
- `package_version`
- `query`
- `release`
- `repository`
- `section`

Output parameters:

- `items` (array)
- `next_cursor`

### `get_manual` (~198 tokens)

Get full manual text by name, e.g. manual_name="ls"; no package needed.

manual_name is the command name (also matches aliases); package is an optional filter.
Tries exact casing first, then a case-insensitive name/alias match.
Search API selects latest indexed packages per scope, preferring Fedora
when distribution is omitted, then newest Fedora RPM version across scopes.
Explicit filters always apply; package_version can select historical manuals.
Exact command names (sections 1/8) precede other names and aliases within
the preferred distro. No locale fallback.
Returns manual text with a distro/release and package/version header.
Source-only manuals raise an error with extraction status.

Input parameters:

- `architecture`
- `distribution`
- `locale` (string)
- `manual_name` (string, required)
- `package`
- `package_version`
- `release`
- `repository`
- `section`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-manpage-mcp/manpage#diagnostics

## Score history

- 2026-10-17: 67
- 2026-10-16: 67
- 2026-10-15: 67
- 2026-10-14: 67
- 2026-10-13: 67
- 2026-10-12: 76
- 2026-10-11: 75
- 2026-10-10: 75
- 2026-10-05: 73
- 2026-10-04: 72
- 2026-10-03: 72

## Common questions

### What is the Manpage MCP server?

Manpage MCP is listed in the public MCP registry as ai.manpage/mcp. Search and read Linux manual pages with version-aware lookup and exact package provenance. This page covers its hosted endpoint (https://manpage.ai/mcp).

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

Manpage MCP scores 67 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 Manpage MCP server expose?

Manpage MCP exposes 3 tools: get_targets, search, get_manual. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.

### Does the Manpage MCP server require authentication?

No. We connected to Manpage MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Manpage MCP server still maintained?

Manpage MCP is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://manpage.ai/mcp
- Website: https://manpage.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-manpage-mcp/manpage.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-manpage-mcp/manpage.json
- HTML version of this page: https://verifymcp.io/servers/ai-manpage-mcp/manpage