pure.mdのモデル コンテキスト プロトコル (MCP) サーバーにようこそ。
pure.md を使えば、スクリプト、API、アプリ、エージェントなどからMarkdown形式のウェブコンテンツに確実にアクセスできます。URLの先頭にpure.md/を付けるだけです。ボット検出を回避し、SPA向けにJavaScriptをレンダリングするほか、HTML、PDF、画像などを純粋なMarkdown形式に変換できます。Markdownコンテンツ用のCDNのように、同じリソースへの将来のリクエストに対するレスポンスをグローバルにキャッシュすることで、オリジンウェブサーバーの負荷を軽減します。
puremd-mcp がないと、ローカル エージェントは Web コンテンツの取得に失敗する可能性があります。puremd -mcp は、Cursor、Windsurf、Claude Desktop などの MCP クライアントに pure.md の機能を採用する方法を教え、Web のブロック解除および検索機能を提供します。
puremd-mcp には 2 つのツールが付属しています。
unblock-url - ブロックされずにWebページからマークダウンを抽出する
search-web - クエリをウェブで検索し、結果をマークダウンに連結します
Anthropicが開発したモデルコンテキストプロトコル（ MCP）は、AIシステムがツールのエコシステムとシームレスに連携できるようにするオープンスタンダードです。これにより、Cursor、Windsurf、Claude DesktopなどのMCPクライアントは、さまざまなAPIやその他の機能の使い方を学習できます。
APIキーの生成は、より高いレート制限を解除するためのオプションのステップです。pure.md MCPサーバーを匿名で使用したい場合は、 PUREMD_API_KEY値を空文字列（ "" ）に設定してください。
pure.mdで新しいアカウントを登録しましょう。登録は無料です。
ダッシュボードで新しいAPIトークンを生成します
トークンをコピーし、MCPクライアントの設定ファイルのPUREMD_API_KEY値に使用します（下記参照）。
Related MCP server: mult-fetch-mcp-server
~/.cursor/mcp.jsonファイルに次のコードを追加します。
{
"mcpServers": {
"pure.md": {
"command": "npx",
"args": ["-y", "puremd-mcp"],
"env": {
"PUREMD_API_KEY": "<TOKEN>"
}
}
}
}./codeium/windsurf/model_config.jsonファイルに以下を追加します。
{
"mcpServers": {
"pure.md": {
"command": "npx",
"args": ["-y", "puremd-mcp"],
"env": {
"PUREMD_API_KEY": "<TOKEN>"
}
}
}
}~/Library/Application\ Support/Claude/claude_desktop_config.jsonファイルに以下を追加します。
{
"mcpServers": {
"pure.md": {
"command": "npx",
"args": ["-y", "puremd-mcp"],
"env": {
"PUREMD_API_KEY": "<TOKEN>"
}
}
}
}Smithery経由で Claude Desktop 用の puremd-mcp を自動的にインストールするには:
npx -y @smithery/cli install @puremd/puremd-mcp --client claude| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
search-webunblock-urlScored across 2 tools
The two tools have clearly distinct purposes: 'search-web' appears to perform web searches, while 'unblock-url' likely handles URL unblocking or access. There is no overlap in functionality, making them easily distinguishable.
Both tools follow a consistent verb-noun pattern with hyphen separation (e.g., 'search-web', 'unblock-url'), and they use clear, action-oriented verbs. There are no deviations in naming style.
With only 2 tools, the server feels thin and likely incomplete for a web-related domain. This minimal set suggests significant gaps in coverage, such as missing operations for browsing, filtering, or managing search results.
Inferred as a web search/access server, the toolset is severely incomplete. It lacks core operations like retrieving search results, handling pagination, or managing blocked URLs beyond unblocking. This will likely cause agent failures in typical workflows.
Turn any public website into an MCP server for agents to search, read and navigate.
MCP server for Firecrawl — web search, scraping, and biomedical/arXiv paper search.
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
Docs: https://docs.keenable.ai/mcp-server Keenable is a free, remote MCP server that gives agents access to the web index. Search the web with ranked results and date/site filters, then fetch any indexed page as clean markdown. Works out of the box with no account or API key.
