The 4get MCP Server provides seamless access to the 4get meta search engine API, enabling comprehensive search across multiple content types with production-ready features.
Core Search Functions:
Web Search: Full web search with extended mode, featured answers, and spelling corrections
Image Search: Image discovery with filters, thumbnails, and metadata
News Search: Recent news articles with publication dates and thumbnails
Pagination Support: Navigate results using next page tokens across all search types
Advanced Features:
Engine Selection: Choose from 20+ search engines including DuckDuckGo, Google, Brave, Yandex, and Baidu
Smart Caching: TTL-based response caching with configurable size limits for improved performance
Retry Logic: Automatic retry with exponential backoff for rate limiting and network errors
Rich Results: Comprehensive formatting with related searches, spelling corrections, and featured answers
Customizable Parameters: Fine-tune searches with language, region, filters, and date ranges via extra_params
Production Ready:
High Configurability: 11+ environment variables for performance tuning
Robust Architecture: Connection pooling, comprehensive error handling, and validation
LLM Integration: Seamless integration with AI assistants and IDEs like Cursor and OpenAI Codex
Direct API Access: Bundled asynchronous Python client for programmatic use beyond MCP protocol
Provides access to the 4get Meta Search engine API, enabling web search, image search, and news search capabilities with features like pagination, featured answers, related searches, and comprehensive result formatting
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@4get MCP Server search for latest AI news from the past week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A MCP server that provides seamless access to the 4get Meta Search engine API for LLM clients via FastMCP.
🔍 Multi Search Functions: Web, image, and news search with comprehensive result formatting
⚡ Smart Caching: TTL-based response caching with configurable size limits
🔄 Retry Logic: Exponential backoff for rate-limited and network errors
🏗️ Production Ready: Connection pooling, comprehensive error handling, and validation
📊 Rich Responses: Featured answers, related searches, pagination support, and more
🧪 Well Tested: Extensive test suite including integration tests with real API, unit tests, and more
⚙️ Highly Configurable: 11+ environment variables for fine-tuning
🎯 Engine Shorthands: Pick a 4get scraper via the engine parameter without memorizing query strings
Related MCP server: 4get MCP Server
Python 3.13+
uv for dependency management
# Install dependencies
uv sync
# Run the server
uv run -m mcp_4get
# Or use mise
mise runThe server is highly configurable via environment variables. All settings have sensible defaults for the public https://4get.ca instance.
Variable | Description | Default |
| Base URL for the 4get instance |
|
| Optional pass token for rate-limited instances | unset |
| Override User-Agent header |
|
| Request timeout in seconds |
|
Variable | Description | Default |
| Cache lifetime in seconds |
|
| Maximum cached responses |
|
| Max concurrent connections |
|
| Max persistent connections |
|
Variable | Description | Default |
| Maximum retry attempts |
|
| Base retry delay in seconds |
|
| Maximum retry delay in seconds |
|
uv run -m mcp_4get# With custom configuration
export FOURGET_BASE_URL="https://my-4get-instance.com"
export FOURGET_PASS="my-secret-token"
export FOURGET_CACHE_TTL="300"
export FOURGET_MAX_RETRIES="5"
uv run -m mcp_4getYou can integrate the 4get MCP server with popular IDEs and AI assistants. Here are configuration examples:
Add this to your Cursor MCP configuration (~/.cursor/mcp.json):
{
"mcpServers": {
"4get": {
"command": "uvx",
"args": [
"mcp_4get@latest"
],
"env": {
"FOURGET_BASE_URL": "https://4get.ca"
}
}
}
}Add this to your Codex MCP configuration (~/.codex/config.toml):
[mcp_servers.4get]
command = "uvx"
args = ["mcp_4get@latest"]
env = { FOURGET_BASE_URL = "https://4get.ca" }Note: Replace /path/to/your/mcp-4get with the actual path to your project directory.
The server exposes three powerful search tools with comprehensive response formatting:
fourget_web_searchfourget_web_search(
query: str,
page_token: str = None, # Use 'npt' from previous response
extended_search: bool = False, # Enable extended search mode
engine: str = None, # Pick a scraper from the supported engine list
extra_params: dict = None # Language, region, etc.
)Response includes: web[], answer[], spelling, related[], npt
fourget_image_searchfourget_image_search(
query: str,
page_token: str = None, # Use 'npt' from previous response
engine: str = None, # Pick a scraper from the supported engine list
extra_params: dict = None # Size, color, type filters
)Response includes: image[], npt
fourget_news_searchfourget_news_search(
query: str,
page_token: str = None, # Use 'npt' from previous response
engine: str = None, # Pick a scraper from the supported engine list
extra_params: dict = None # Date range, source filters
)Response includes: news[], npt
All MCP tools accept an optional engine argument that maps directly to the 4get scraper query parameter. This shorthand overrides any scraper value you may include in extra_params.
Value | Engine |
| DuckDuckGo |
| Brave |
| Mullvad (Brave) |
| Yandex |
| |
| Google CSE |
| Mullvad (Google) |
| Startpage |
| Qwant |
| Ghostery |
| Yep |
| Greppr |
| Crowdview |
| Mwmbl |
| Mojeek |
| Baidu |
| Coc Coc |
| Solofield |
| Marginalia |
| wiby |
| Curlie |
If you need to pass additional 4get query parameters (such as country or language), continue to supply them through extra_params.
All tools support pagination via the npt (next page token):
# Get first page
result = await client.web_search("python programming")
# Get next page if available
if result.get('npt'):
next_page = await client.web_search("ignored", page_token=result['npt'])You can reuse the bundled async client outside MCP for direct API access:
import asyncio
from mcp_4get.client import FourGetClient
from mcp_4get.config import Config
async def main() -> None:
client = FourGetClient(Config.from_env())
data = await client.web_search(
"model context protocol",
options={"scraper": "mullvad_brave"},
)
for result in data.get("web", []):
print(result["title"], "->", result["url"])
asyncio.run(main())This allows you to integrate 4get search capabilities directly into your Python applications without going through the MCP protocol.
Rate Limiting (429): Exponential backoff with jitter
Network Errors: Connection failures and timeouts
Non-retryable: HTTP 404/500 errors fail immediately
FourGetAuthError: Rate limited or invalid authentication
FourGetAPIError: API returned non-success status
FourGetTransportError: Network or HTTP protocol errors
FourGetError: Generic client errors
All settings are validated on startup with clear error messages for misconfigurations.
Based on the real 4get API, responses include rich metadata:
{
"status": "ok",
"web": [
{
"title": "Example Result",
"description": "Result description...",
"url": "https://example.com",
"date": 1640995200,
"type": "web"
}
],
"answer": [
{
"title": "Featured Answer",
"description": [{"type": "text", "value": "Answer content..."}],
"url": "https://source.com",
"table": {"Key": "Value"}
}
],
"spelling": {
"type": "no_correction",
"correction": null
},
"related": ["related search", "terms"],
"npt": "pagination_token_here"
}This project uses several tools to streamline the development process:
mise is used for managing project-level dependencies and environment variables. mise helps ensure consistent development environments across different machines.
To get started with mise:
Install mise by following the instructions on the official website.
Run mise install in the project root to set up the development environment.
Environment Variable Overrides: You can override any environment variable by creating a .mise.local.toml file in the project root:
[env]
FOURGET_BASE_URL = "https://your-custom-4get-instance.com"
FOURGET_CACHE_TTL = "300"
# Add any other environment variables you want to overrideThis file is automatically loaded by mise and allows you to customize your local development environment without modifying the shared configuration files.
UV is used for dependency management and packaging. It provides a clean, version-controlled way to manage project dependencies.
To set up the project with UV:
Install UV using mise, or by following the instructions on the official website.
Run uv sync to install project dependencies.
Add this to your Cursor MCP configuration (~/.cursor/mcp.json):
{
"mcpServers": {
"4get": {
"command": "uv",
"args": [
"run",
"--project",
"/path/to/your/mcp-4get",
"-m",
"src"
],
"env": {
"FOURGET_BASE_URL": "https://4get.ca"
}
}
}
}Add this to your Codex MCP configuration (~/.codex/config.toml):
[mcp_servers.4get]
command = "uv"
args = ["run", "--project", "/path/to/your/mcp-4get", "-m", "src"]
env = { FOURGET_BASE_URL = "https://4get.ca" }Note: Replace /path/to/your/mcp-4get with the actual path to your project directory.
Comprehensive test suite with unit, integration, and performance tests:
# Run all tests
uv run pytest
# Run only fast unit tests (exclude integration)
uv run pytest -m "not integration"
# Run integration tests with real 4get API
uv run pytest -m integration
# Run with coverage
uv run pytest --cov=src
# Run specific test categories
uv run pytest tests/test_cache.py # Cache behavior tests
uv run pytest tests/test_client.py # Client and retry logic tests
uv run pytest tests/test_integration.py # Real API integration testsUnit Tests: Fast, deterministic tests using mock transports
Integration Tests: Real API tests with rate limiting and resilience validation
Cache Tests: TTL expiration, eviction policies, concurrent access
Retry Tests: Exponential backoff, error handling, timeout scenarios
Configuration Tests: Validation logic and environment variable parsing
The tests follow FastMCP testing guidelines with comprehensive fixtures and proper isolation.
Setup: See Development and Quick Start sections
Tests: See Testing section
Linting: uv run ruff check
Format: uv run ruff format
GPLv3 License - see LICENSE file for details.
Search for images using the 4get meta search engine. Returns image results with URLs, thumbnails, and metadata. Supports pagination via the 'npt' token and various image filters.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| page_token | No | ||
| engine | No | Optional search engine override (maps to 4get "scraper" query parameter). | |
| extra_params | No |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations (readOnlyHint, idempotentHint) are consistent. The description adds behavioral details: pagination via 'npt' token and support for image filters, which are beyond annotations. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three well-structured sentences that front-load the main purpose. No redundant or unnecessary words. Efficient and clear.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the main purpose and high-level features but lacks detail on extra_params usage and token handling. With output schema present, return values need not be explained, but additional context for filter parameters would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is low (25%). The description explains query implicitly and mentions pagination token, providing some context for page_token. However, engine and extra_params are not elaborated (engine has schema description but no further context in description, extra_params is free-form with no guidance).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Search for images using the 4get meta search engine.' It specifies the output (URLs, thumbnails, metadata) and features (pagination, filters). The name and context distinguish it from sibling tools (news and web search).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this vs. alternatives. The description implies it is for image search, but does not provide scenarios or exclusions. Usage context is clear but not comparative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search for news articles using the 4get meta search engine. Returns recent news with titles, URLs, descriptions, publication dates, and thumbnails. Supports pagination via the 'npt' token.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| page_token | No | ||
| engine | No | Optional search engine override (maps to 4get "scraper" query parameter). | |
| extra_params | No |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly and idempotent. Description adds return field list and pagination mechanism ('npt' token), providing useful behavioral context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences; no wasted words. Front-loaded with purpose and includes key details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Provides core purpose and pagination info but omits details on engine and extra_params. Output schema exists but not visible; still, description could be more complete given low parameter documentation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is low (25%). Description mentions page_token indirectly via 'npt' but does not explain engine, extra_params, or their purpose. Fails to compensate for low coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Search for news articles' using a specific engine, and lists returned fields. Name and description distinguish from sibling tools (image/web search).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use vs siblings. While the name implies news context, the description does not state usage conditions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search the web using the 4get meta search engine. Returns web results with titles, URLs, descriptions, and optional featured answers. Supports pagination via the 'npt' token and extended search mode.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| page_token | No | ||
| extended_search | No | ||
| engine | No | Optional search engine override (maps to 4get "scraper" query parameter). | |
| extra_params | No |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent behavior. The description adds value by mentioning pagination via 'npt' token and extended search mode, but does not elaborate on side effects, rate limits, or error handling. It is adequate but not extensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, front-loads the core purpose, and contains no redundant information. Every sentence adds necessary context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers key outputs and pagination, which is sufficient for a search tool with an output schema. However, it lacks details on error conditions or constraints, leaving minor gaps in completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With only 20% schema description coverage, the description partially compensates by explaining pagination (related to page_token) and extended search mode. However, it does not address the query, engine, or extra_params parameters, leaving gaps in understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it searches the web using the 4get meta search engine and specifies the return fields (titles, URLs, descriptions, featured answers). The tool name and the context of sibling tools (image and news search) make the purpose distinct, though not explicitly differentiated in the description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this web search tool versus the image or news search siblings. The description assumes the agent infers context from the tool name, which is insufficient for clear decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.2fourget_image_search3 fields changedInput schema / $defsRemoved value: -{
- "SearchEngine": {
- "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
- "enum": [
- "ddg",
- "brave",
- "mullvad_brave",
- "yandex",
- "google",
- "google_cse",
- "mullvad_google",
- "startpage",
- "qwant",
- "ghostery",
- "yep",
- "greppr",
- "crowdview",
- "mwmbl",
- "mojeek",
- "baidu",
- "coccoc",
- "solofield",
- "marginalia",
- "wiby",
- "curlie"
- ],
- "type": "string"
- }
-}Input schema / additionalPropertiesAdded value: +falseInput schema / properties / engine / anyOfPrevious value: -[
- {
- "$ref": "#/$defs/SearchEngine"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
+ "enum": [
+ "ddg",
+ "brave",
+ "mullvad_brave",
+ "yandex",
+ "google",
+ "google_cse",
+ "mullvad_google",
+ "startpage",
+ "qwant",
+ "ghostery",
+ "yep",
+ "greppr",
+ "crowdview",
+ "mwmbl",
+ "mojeek",
+ "baidu",
+ "coccoc",
+ "solofield",
+ "marginalia",
+ "wiby",
+ "curlie"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]fourget_news_search3 fields changedInput schema / $defsRemoved value: -{
- "SearchEngine": {
- "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
- "enum": [
- "ddg",
- "brave",
- "mullvad_brave",
- "yandex",
- "google",
- "google_cse",
- "mullvad_google",
- "startpage",
- "qwant",
- "ghostery",
- "yep",
- "greppr",
- "crowdview",
- "mwmbl",
- "mojeek",
- "baidu",
- "coccoc",
- "solofield",
- "marginalia",
- "wiby",
- "curlie"
- ],
- "type": "string"
- }
-}Input schema / additionalPropertiesAdded value: +falseInput schema / properties / engine / anyOfPrevious value: -[
- {
- "$ref": "#/$defs/SearchEngine"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
+ "enum": [
+ "ddg",
+ "brave",
+ "mullvad_brave",
+ "yandex",
+ "google",
+ "google_cse",
+ "mullvad_google",
+ "startpage",
+ "qwant",
+ "ghostery",
+ "yep",
+ "greppr",
+ "crowdview",
+ "mwmbl",
+ "mojeek",
+ "baidu",
+ "coccoc",
+ "solofield",
+ "marginalia",
+ "wiby",
+ "curlie"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]fourget_web_search3 fields changedInput schema / $defsRemoved value: -{
- "SearchEngine": {
- "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
- "enum": [
- "ddg",
- "brave",
- "mullvad_brave",
- "yandex",
- "google",
- "google_cse",
- "mullvad_google",
- "startpage",
- "qwant",
- "ghostery",
- "yep",
- "greppr",
- "crowdview",
- "mwmbl",
- "mojeek",
- "baidu",
- "coccoc",
- "solofield",
- "marginalia",
- "wiby",
- "curlie"
- ],
- "type": "string"
- }
-}Input schema / additionalPropertiesAdded value: +falseInput schema / properties / engine / anyOfPrevious value: -[
- {
- "$ref": "#/$defs/SearchEngine"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
+ "enum": [
+ "ddg",
+ "brave",
+ "mullvad_brave",
+ "yandex",
+ "google",
+ "google_cse",
+ "mullvad_google",
+ "startpage",
+ "qwant",
+ "ghostery",
+ "yep",
+ "greppr",
+ "crowdview",
+ "mwmbl",
+ "mojeek",
+ "baidu",
+ "coccoc",
+ "solofield",
+ "marginalia",
+ "wiby",
+ "curlie"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]v1.0.0fourget_image_search2 fields changedInput schema / $defsAdded value: +{
+ "SearchEngine": {
+ "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
+ "enum": [
+ "ddg",
+ "brave",
+ "mullvad_brave",
+ "yandex",
+ "google",
+ "google_cse",
+ "mullvad_google",
+ "startpage",
+ "qwant",
+ "ghostery",
+ "yep",
+ "greppr",
+ "crowdview",
+ "mwmbl",
+ "mojeek",
+ "baidu",
+ "coccoc",
+ "solofield",
+ "marginalia",
+ "wiby",
+ "curlie"
+ ],
+ "type": "string"
+ }
+}Input schema / properties / engineAdded value: +{
+ "anyOf": [
+ {
+ "$ref": "#/$defs/SearchEngine"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional search engine override (maps to 4get \"scraper\" query parameter)."
+}fourget_news_search2 fields changedInput schema / $defsAdded value: +{
+ "SearchEngine": {
+ "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
+ "enum": [
+ "ddg",
+ "brave",
+ "mullvad_brave",
+ "yandex",
+ "google",
+ "google_cse",
+ "mullvad_google",
+ "startpage",
+ "qwant",
+ "ghostery",
+ "yep",
+ "greppr",
+ "crowdview",
+ "mwmbl",
+ "mojeek",
+ "baidu",
+ "coccoc",
+ "solofield",
+ "marginalia",
+ "wiby",
+ "curlie"
+ ],
+ "type": "string"
+ }
+}Input schema / properties / engineAdded value: +{
+ "anyOf": [
+ {
+ "$ref": "#/$defs/SearchEngine"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional search engine override (maps to 4get \"scraper\" query parameter)."
+}fourget_web_search2 fields changedInput schema / $defsAdded value: +{
+ "SearchEngine": {
+ "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
+ "enum": [
+ "ddg",
+ "brave",
+ "mullvad_brave",
+ "yandex",
+ "google",
+ "google_cse",
+ "mullvad_google",
+ "startpage",
+ "qwant",
+ "ghostery",
+ "yep",
+ "greppr",
+ "crowdview",
+ "mwmbl",
+ "mojeek",
+ "baidu",
+ "coccoc",
+ "solofield",
+ "marginalia",
+ "wiby",
+ "curlie"
+ ],
+ "type": "string"
+ }
+}Input schema / properties / engineAdded value: +{
+ "anyOf": [
+ {
+ "$ref": "#/$defs/SearchEngine"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional search engine override (maps to 4get \"scraper\" query parameter)."
+}fourget_image_searchfourget_news_searchfourget_web_searchScored across 3 tools
Each tool targets a distinct search type (images, news, web) with clear descriptions, eliminating any ambiguity for agents.
All tools follow a consistent 'fourget_<type>_search' pattern, making it easy to predict the purpose from the name.
Three tools cover the essential search functionalities for a meta search engine without unnecessary bloat or deficiency.
The set covers core web, image, and news searches. Adding video or other search types could enhance completeness, but it's not a critical gap.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
LLM-ready web search + instant answers + URL-to-clean-text fetch for agents and RAG.
Search Google straight from your AI agent. Web results, images, videos, news, products, scholarly ar
Web search, news, page retrieval, sitemaps, and trending topics through Search1API.
Search the web, images, videos, news, and local businesses with robust filters, freshness controls…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yshalsager/mcp-4get'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
