footnote-mcp
Related Servers
Alternatives to footnote-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that builds structured research source packs for a topic, extracting verified facts, quotes, numbers, dates, and primary links with a coverage map of claims across sources.2MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for web intelligence extraction that provides 55 tools for extracting structured data, design systems, accessibility audits, and more from websites.49 npm2MIT
- AlicenseAqualityCmaintenanceAn MCP server for web search, web fetching, and Context7 documentation tools with proxy support, designed for internal network environments.413 npm4MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server for content creation that extracts video transcripts, scrapes web articles, and performs web searches.-
- AlicenseAqualityCmaintenanceAn MCP server for web content extraction, providing tools to fetch clean text, extract links, query by CSS selector, and search the web via DuckDuckGo.4MIT
- AlicenseBqualityNot gradedmaintenanceProvides advanced Google Custom Search functionality, web content extraction, and specialized research tools such as search analytics, multi-site search, and fact checking. Works as an MCP server compatible with any MCP client.10MIT
TDQS
Scored across 42 tools
Most tools have clearly distinct purposes, but there is some overlap among table-extraction tools (web_extract_tables vs browser_extract_tables) and search tools (web_search, web_search_recent, web_deep_search, scholarly_search). However, descriptions differentiate them effectively.
Tool names follow a mix of patterns: many start with 'web_' or 'browser_', but there is no consistent verb_noun structure. Some names are compound verbs (e.g., 'reconcile_time_series', 'locate_claim_span'), while others are descriptive nouns (e.g., 'startup_health_check'). This inconsistency can be confusing.
42 tools is high for a single server, but the domain (web research, extraction, validation) is broad. Each tool seems purposeful, but the count pushes the boundary of what is manageable and may lead to agent confusion.
The tool set covers a wide range of operations: search, fetch, extract, parse, browser interaction, data validation, evidence handling, and recipe management. Minor gaps exist (e.g., no explicit tool for complex browser workflows beyond tables), but overall it is comprehensive.