Search for:
Why this server?
Enables users to validate the existence of email addresses through a simple FastMCP tool, offering JSON responses.
Why this server?
MCP for working with GraphQL servers which typically return data in JSON format.
Why this server?
Allows the use of Kagi's API for web searching and content enrichment through methods like fastgpt, enrich/web, and enrich/news, which often return data in JSON format.
Why this server?
An MCP server for connecting agentic systems to search systems via searXNG, which will return search results in JSON format.
Why this server?
A server that allows AI agents to interact with the Tally API to access DAO governance data, proposals, and metadata using Model Context Protocol (MCP), built with TypeScript and GraphQL, often resulting in JSON responses.
Why this server?
A Model Context Protocol (MCP) server that provides JSON-RPC functionality through OpenRPC, which uses JSON for data serialization.
Why this server?
Access to many public datasets right from your LLM application, which often return data in JSON format.
Why this server?
A TypeScript-based MCP server utilizing the UseScraper API to provide web scraping capabilities, allowing users to extract content from webpages in various formats, including JSON.
Why this server?
A Model Context Protocol (MCP) server that provides search and crawl functionality using Search1API, which will return search results in JSON format.
Why this server?
Enables integration with Google Drive for listing, reading, and searching over files, supporting various file types with automatic export for Google Workspace files. metadata is in JSON format.