Skip to main content
Glama
bmorphism

Marginalia MCP Server

by bmorphism

Marginalia MCP 서버

비상업적 콘텐츠와 인터넷의 숨겨진 보물을 찾는 데 중점을 둔 검색 엔진인 Marginalia Search 에 대한 액세스를 제공하는 MCP(Model Context Protocol) 서버입니다.

특징

  • Marginalia Search API를 사용하여 웹 검색

  • 인덱스 및 결과 수를 포함한 구성 가능한 검색 매개변수

  • 유용한 오류 메시지를 통한 속도 제한 보호

  • 원활한 통합을 위해 MCP SDK를 사용하여 구축됨

Related MCP server: web-search-mcp

설치

지엑스피1

구성

서버는 환경 변수를 사용하여 구성할 수 있습니다.

  • MARGINALIA_API_KEY : Marginalia 검색 API 키(선택 사항, 기본적으로 공개 액세스)

전용 API 키를 요청하려면 kontakt@marginalia.nu 로 문의하세요.

용법

서버는 다음과 같은 MCP 도구를 제공합니다.

찾다

다음 매개변수를 사용하여 Marginalia Search를 사용하여 웹을 검색하세요.

  • query (필수): 검색 쿼리 문자열

  • index (선택 사항): 검색 인덱스 번호(기본 GUI의 드롭다운에 해당)

  • count (선택 사항): 반환할 결과 수(1-100, 기본값: 10)

MCP를 통한 사용 예:

const result = await mcp.useTool("marginalia", "search", {
  query: "interesting non-commercial websites",
  count: 5
});

응답 형식

검색 결과는 다음 형식으로 반환됩니다.

{
  "query": "your search query",
  "license": "license information",
  "results": [
    {
      "url": "result url",
      "title": "page title",
      "description": "page description"
    }
    // ... more results
  ]
}

오류 처리

서버에는 다음에 대한 강력한 오류 처리 기능이 포함되어 있습니다.

  • 속도 제한(503개 응답)

  • 잘못된 요청

  • 네트워크 오류

  • API 관련 오류

텍스트 음성 변환 지원 추가

say MCP 서버를 사용하여 텍스트-음성 기능을 활성화하려면 다음 구성을 추가하세요.

Cline(VSCode 확장 프로그램)의 경우

~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json 에 추가:

{
  "mcpServers": {
    "say": {
      "command": "node",
      "args": ["/Users/barton/worlds/servers/src/say-mcp-server/build/index.js"]
    }
  }
}

클로드 데스크탑용

~/Library/Application Support/Claude/claude_desktop_config.json 에 추가:

{
  "mcpServers": {
    "say": {
      "command": "node",
      "args": ["/Users/barton/worlds/servers/src/say-mcp-server/build/index.js"]
    }
  }
}

say MCP 서버는 여러 음성 및 언어의 텍스트 음성 변환 기능을 제공합니다. 사용 가능한 도구는 다음과 같습니다.

  • speak : 지정된 음성과 속도를 사용하여 텍스트를 소리내어 읽습니다.

  • list_voices : 사용 가능한 모든 텍스트 음성 변환 음성을 나열합니다.

특허

MIT 라이선스 - 자세한 내용은 라이선스 파일을 참조하세요.

Available Tools

1 tool
search-marginaliaC

Search the web using Marginalia Search

ParametersJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results to return
indexNoSearch index (corresponds to dropdown in main GUI)
queryYesSearch query

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Search the web' but fails to describe key behaviors such as rate limits, authentication needs, result format, or error handling. This leaves significant gaps in understanding how the tool operates beyond basic functionality.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—a single sentence that directly states the tool's function without any fluff or redundancy. It is front-loaded and wastes no words, making it efficient for quick comprehension by an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It covers the basic purpose but misses critical context like behavioral traits, result format, and error handling. For a search tool with three parameters and no structured output information, this minimal description leaves too many operational details unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, documenting all three parameters (query, count, index) clearly. The description adds no additional semantic context beyond what the schema provides, such as examples or usage tips. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't need to heavily.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Search the web using Marginalia Search.' It specifies the verb ('Search') and the resource ('the web'), and mentions the specific search engine ('Marginalia Search'). However, since there are no sibling tools, it cannot differentiate from alternatives, which prevents a perfect score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without indicating scenarios where it might be preferred or avoided, leaving the agent with no usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedsearch-marginalia

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'search-marginalia' has a clear and distinct purpose of searching the web using Marginalia Search, leaving no room for confusion or misselection.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'search-marginalia' follows a clear verb_noun pattern, and with no other tools to compare, there are no deviations or inconsistencies in naming conventions.

Tool Count2/5

A single tool for a web search server is too few for the apparent scope, as it lacks basic functionality like filtering results, handling pagination, or accessing specific search features. This minimal toolset feels thin and limits the server's utility, making it borderline inadequate for typical search-related tasks.

Completeness2/5

The tool surface is severely incomplete for a web search domain. While 'search-marginalia' provides a core search function, there are significant gaps such as no ability to refine searches, view result details, or manage search history. This will likely cause agent failures when more complex search operations are needed.

Maintenance

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    B
    quality
    C
    maintenance
    Provides web search capabilities using SearxNG, allowing AI assistants like Claude to search the web with a privacy-respecting metasearch engine.
    1
    11
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    Provides ad-filtered web search and full-page content reading, including multi-page and JavaScript-rendered pages, with source verification and configurable search providers.
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables assistants to search and ask questions against a human-curated search engine index, returning vetted sites with titles, URLs, descriptions, tags, and cited answers. Runs locally over stdio with no API key or signup required.
    53 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables independent web search over a non-commercial, non-SEO index that favors text-heavy, ad-light pages, useful for niche technical and historical topics.
    432 npm
    MIT