search-fetch-server MCP Server

Created By
nexon33a year ago
Overview

search-fetch-server MCP Server

what is search-fetch-server MCP Server?

The search-fetch-server MCP Server is a TypeScript-based implementation of the Model Context Protocol (MCP) that allows users to manage a simple notes system with features for searching, creating, and summarizing notes.

how to use search-fetch-server MCP Server?

To use the server, install the necessary dependencies, build the server, and configure it with your application (such as Claude Desktop) to manage notes effectively.

key features of search-fetch-server MCP Server?

  • Resource Management: Access and manage text notes using note:// URIs with metadata.
  • Note Creation: Create and store new text notes with a title and content.
  • Fetching Content: Fetch content from a specified URL, with optional markdown conversion using Puppeteer.
  • Search Functionality: Perform DuckDuckGo searches and retrieve results in JSON format.
  • Summarization: Generate summaries of stored notes using structured prompts.

use cases of search-fetch-server MCP Server?

  1. Create and manage personal notes for easy retrieval.
  2. Fetch and summarize online articles or resources for research.
  3. Implement a searchable note-taking application for team collaboration.

FAQ from search-fetch-server MCP Server?

  • What is MCP?

    The Model Context Protocol is a framework for context-aware applications that can manage and share data across different environments.

  • Can I use this server for larger applications?

    Yes, it can be integrated into larger applications that require note management and contextual data retrieval.

  • Is there support for other mime types?

    Currently, it uses plain text mime type for content access; additional mime types can be implemented as needed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nexon33
Star
-
Language
-
License
-

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago