Data · Remote MCP server
Webhound
Budgeted reports and datasets with Hound, Webhound's DeepSeek V4 Pro + GPT-5.4 research harness.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.webhound/webhound- Version
- 0.5.2
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-26
- Updated
- 2026-07-26
- Publisher
- ai.webhound
- Namespace
- Namespace verified by the MCP Registry via the domain webhound.ai · how
- Listed under
- DeepSeek MCP servers
- Website
- www.webhound.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.webhound.ai/api/v2/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | webhound-mcp | 0.5.2 | stdio |
How to connect Webhound
Webhound is a remote MCP server: there is nothing to install. Its endpoint is https://api.webhound.ai/api/v2/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: webhound-mcp version 0.5.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y webhound-mcp@0.5.2. It reads the environment variable WEBHOUND_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"webhound": {
"command": "npx",
"args": [
"-y",
"webhound-mcp@0.5.2"
],
"env": {
"WEBHOUND_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Web Search APIWeb search returning structured results - titles, URLs, snippets. x402 micropayment. | Remote · SSELive check: ✗ no handshake |
| Web Search API for all your agents and LLMsLive web search, image search, topic filters and full-text fetch over our own crawled index. | Remote · HTTPLive check: sign-in required |
| Web Validator by DigestSEOAudit public webpages and supplied markup for HTML, CSS, SEO, JSON-LD, and link issues. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| web-retrieval-mcpMCP web search + tiered web fetch for AI agents (Exa, Firecrawl), SSRF-guarded, cross-platform. | Local · stdio |
| WebLensScrape, crawl, map and extract the web. Pay per call in USDC, no account or API key. | Remote · HTTPLive check: ✓ handshake |
| WebMCP TodayYour agent gets trustworthy tools on sites without WebMCP - data-only packages you approve. | Local · stdio |
| WebPeelFetch any web page as clean, AI-ready markdown with HTTP-to-browser escalation. | Local · stdio |
| WebReaperAI-native web scraper: scrape, crawl and map any site to clean markdown over stdio. MIT-licensed. | Local · stdio |