mcpbeat Sign in

Manpage MCP Server

answering

Manpage MCP is answering right now. Last checked 9 min ago. It exposes 4 tools.

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

Uptime history 9 days of history · worst day 95%
9 days agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
502 ms
Response time
average over 24h
open, no key
Access
streamable-http

Manpage MCP does not always answer

Over the last week it answered 99.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add mcp --transport http https://manpage.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://manpage.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://manpage.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://manpage.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://manpage.ai/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

man
get_man_page
Read a manual. Required fields depend on the retrieval mode: 1. Name lookup: name. Example: {"name":"ls"}. Optional product pins a distro. Without OS/version filters, select the newest upstream version across active catalogs. Different packages or sections remain ambiguous; provenance identifies the chosen distro. 2. ID lookup: page_id copied from a previous result; omit name-based filters. 3. Continuation: cursor copied from get_man_page.next_cursor; omit name-based filters. A matching page_id may also be supplied. max_chars is optional in every mode. With product, os_version defaults to latest (null also means latest): the newest numbered release with readable documentation for the requested architecture/locale. Pass an explicit release such as 44 to pin it. Responses identify the actual OS release. A missing manual never falls back to an older OS. page_id and cursor retain their own release. Version accepts exact EVR (2:1.35-9.fc44), version-release (1.35-9.fc44), or upstream version (1.35). No operators or ranges: >=1.35 is invalid. RPM ~ and ^ characters are allowed in exact versions. Omit version for current documentation. An unavailable version never falls back; alternatives list only readable manuals. Ambiguity returns page_id choices. Alternatively pass only page_id from search, or only cursor to continue a long page. max_chars bounds each response; next_cursor=null means finished.
search_man_pages
Find manuals by topic, command prefix or literal option such as --recursive. Required field: query, including when continuing a search. All other fields are optional. Example: {"query":"compress files"}. Read a result with get_man_page(page_id=...). Returns context-preserving excerpts and page_id values for get_man_page. Aliases of the same document are grouped. Without product, an exact manual-name match selects the newest upstream version per package/name/section across active OS catalogs. Equal versions use deterministic distro ties; unrelated implementations stay separate. Topic/prefix searches use the newest numbered release per product for architecture/locale. Pass os_version=null to search all releases without collapsing distro variants. An explicit release pins OS selection. Current package builds are searched by default. Set historical=true to include readable older package versions within the selected OS releases, without automatic upstream-version selection. Responses name the actual OS targets searched. Repeat the query/filters with next_page to continue; null means finished or the configured page cap was reached.
give
give_feedback
Report unexpected tool errors, missing capabilities, confusing output, or unclear docs. Only message is required. Describe your goal, what you tried, what you expected, and any workaround. Feedback is saved for the maintainers to review.
targets
list_targets
List OS releases with readable manuals. Required fields: none; call with {}. Use product and os_version from a result in get_man_page or search_man_pages. An empty list means no current documentation is available.

Endpoints

URLTransportStateLatencyChecked
https://manpage.ai/mcp streamable-http answering 579 ms 9 min ago

Alternatives to Manpage MCP

same job, measured the same way
Simlir MCP Server
by simlir

Simlir MCP server for semantic product search, visual search, and exact product lookup.

15 installs/wk local only
Vigil Website MCP
by blvigil

Search and read public Vigil pages with source URLs.

6 tools answering
Ace Website MCP
by ace-bl

Search and read public Ace pages with source URLs.

6 tools answering
Black Label Real Estate Website MCP
by blbestate

Search and read public Black Label Real Estate pages with source URLs.

12 tools answering
npm
by mikusnuz

MCP server for npm package management — publish, version, search, audit, and more

199 installs/wk local only
S
Sunset Website MCP
by sunsetmixing

Search and read public Sunset pages with source URLs.

6 tools answering
Black Label Bots Website MCP
by blacklabelbots

Search and read public Black Label Bots pages with source URLs.

10 tools answering
BL Sign Website MCP
by blacklabeltec

Search and read public BL Sign pages with source URLs.

3 tools answering

Manpage MCP — questions

Answers built from our own checks of this server.

What can Manpage MCP do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_man_page, give_feedback, list_targets, search_man_pages. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Manpage MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 502 ms. The bar chart above shows every period we have measured.
How do I connect Manpage MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Manpage MCP need an API key?
No. Manpage MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Manpage MCP?
It answers our handshake in 502 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.