pure.md 의 MCP(Model Context Protocol) 서버에 오신 것을 환영합니다.
pure.md를 사용하면 스크립트, API, 앱, 에이전트 등이 마크다운 형식의 웹 콘텐츠에 안정적으로 액세스할 수 있습니다. URL에 pure.md/ 접두사를 추가하기만 하면 됩니다. 봇 탐지를 피하고 SPA용 JavaScript를 렌더링하며, HTML, PDF, 이미지 등을 순수 마크다운으로 변환할 수 있습니다. 마크다운 콘텐츠용 CDN처럼, 동일한 리소스에 대한 향후 요청에 대한 응답을 전역적으로 캐시하여 원본 웹 서버의 부하를 줄여줍니다.
puremd-mcp가 없으면 로컬 에이전트가 웹 콘텐츠를 가져오지 못할 수 있습니다. puremd-mcp는 Cursor, Windsurf, Claude Desktop과 같은 MCP 클라이언트에게 pure.md의 기능을 도입하여 웹 차단을 해제하고 검색하는 기능을 제공하는 방법을 알려줍니다.
puremd-mcp에는 두 가지 도구가 포함되어 있습니다.
unblock-url - 차단되지 않고 웹 페이지에서 마크다운을 추출합니다.
search-web - 웹에서 쿼리를 검색하고 결과를 마크다운으로 연결합니다.
Anthropic에서 개발한 모델 컨텍스트 프로토콜(Model Context Protocol)은 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 파일에 다음을 추가합니다.
지엑스피1
./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.
