Skip to main content
Glama
enesjakozh
bmorphism

Marginalia MCP Server

by bmorphism
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Servidor MCP de Marginalia

Un servidor MCP (Model Context Protocol) que proporciona acceso a Marginalia Search , un motor de búsqueda centrado en encontrar contenido no comercial y joyas ocultas de Internet.

Características

  • Busque en la web utilizando la API de búsqueda de Marginalia

  • Parámetros de búsqueda configurables, incluidos índice y recuento de resultados

  • Protección de limitación de velocidad con mensajes de error útiles

  • Creado con el SDK de MCP para una integración perfecta

Related MCP server: web-search-mcp

Instalación

npm install
npm run build

Configuración

El servidor se puede configurar mediante variables de entorno:

  • MARGINALIA_API_KEY : Su clave API de búsqueda de Marginalia (opcional, el acceso público es predeterminado)

Para solicitar una clave API dedicada, comuníquese con: kontakt@marginalia.nu

Uso

El servidor proporciona la siguiente herramienta MCP:

buscar

Busca en la web usando Marginalia Busca con los siguientes parámetros:

  • query (obligatoria): cadena de consulta de búsqueda

  • index (opcional): Número de índice de búsqueda (corresponde al menú desplegable en la GUI principal)

  • count (opcional): Número de resultados a devolver (1-100, predeterminado: 10)

Ejemplo de uso a través de MCP:

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

Formato de respuesta

Los resultados de la búsqueda se devuelven en el siguiente formato:

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

Manejo de errores

El servidor incluye un manejo robusto de errores para:

  • Limitación de velocidad (503 respuestas)

  • Solicitudes no válidas

  • Errores de red

  • Errores específicos de la API

Agregar compatibilidad con texto a voz

Para habilitar las capacidades de conversión de texto a voz mediante el servidor MCP, agregue la siguiente configuración:

Para Cline (extensión de VSCode)

Agregar a ~/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"]
    }
  }
}

Para Claude Desktop

Agregar a ~/Library/Application Support/Claude/claude_desktop_config.json :

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

El servidor MCP ofrece funciones de conversión de texto a voz con múltiples voces e idiomas. Herramientas disponibles:

  • speak : Leer un texto en voz alta usando una voz y velocidad específicas.

  • list_voices : enumera todas las voces de texto a voz disponibles

Licencia

Licencia MIT: consulte el archivo LICENCIA para obtener más detalles

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
Deploy Server
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

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

Resources

Related MCP Connectors

Related MCP Servers

  • SearxNG MCP Server

    Sacode
    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

  • web-search-mcp

    cctv2333
    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.
    -
  • rabbytte-mcp by marklanetech

    rabbytte-mcpofficial

    marklanetech
    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

  • marginalia

    pipeworx-io
    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

Appeared in Searches