Deep Search MCP Server

Created By
joaomja year ago
A deep web search MCP using LinkUp API.
Overview

What is Deep Search MCP?

Deep Search MCP is a TypeScript-based server that enables deep web searches using the LinkUp API, providing structured results and demonstrating core MCP concepts.

How to use Deep Search MCP?

To use Deep Search MCP, install the dependencies, build the server, and configure it with your LinkUp API key. You can run it in development mode for auto-rebuild or in production mode.

Key features of Deep Search MCP?

  • Tools for performing deep web searches
  • Structured results from LinkUp API
  • Configurable server settings
  • Debugging support with MCP Inspector

Use cases of Deep Search MCP?

  1. Conducting deep web searches for research purposes.
  2. Integrating deep search capabilities into applications.
  3. Analyzing structured data from deep web sources.

FAQ from Deep Search MCP?

  • What is the LinkUp API?

The LinkUp API provides access to deep web search capabilities and structured data.

  • How do I obtain an API key?

You can obtain an API key by signing up for the LinkUp API service.

  • Can I run this server in production?

Yes, you can run the server in production mode after proper configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
joaomj
Star
1
Language
JavaScript
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