Open Market Research MCP
Related Servers
Alternatives to Open Market Research MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to search U.S. government contracts, grants, jobs, past awards, company histories, and teaming partners, and to assess opportunities for fit and bid decisions.9194 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search and retrieve stored open-source information through read-only MCP tools, including evidence retrieval by document or snapshot ID with byte-integrity verification.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables procurement officers and MCP clients to ingest tender and bid documents, run cited multi-agent evaluations with scores and risk flags, and review audit trails while preventing AI from recording award decisions.MIT

GateCoreofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover governed capabilities, inspect machine-readable contracts, and request policy-checked procurements with signed receipts and audit trails.Apache 2.0- AlicenseNot gradedqualityCmaintenanceEnables an external AI client to discover tender portal APIs, collect and verify tender listings, combine sections, and select relevant lots from a user request through local MCP tools.MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to search and retrieve contract intelligence over public contract data, with agent skills for precedent lookup, negotiation checks, and risk flagging, all with verification and citations.-
TDQS
Scored across 8 tools
Most tools occupy clearly distinct stages of a market-research workflow (plan, source discovery, gap analysis, drafting, metadata import/mapping). The only genuinely adjacent pair is list_research_sources vs find_research_sources, whose boundary (curated descriptors vs directories/guidance/upstream servers) is stated but still easy to confuse. The remaining six tools are unambiguous.
Every tool follows a snake_case verb_noun pattern (list_, find_, create_, identify_, draft_, normalize_, import_, map_), with no camelCase or bare-noun outliers. The one long name, map_1102tools_usaspending_record, embeds product nouns but still conforms to the same verb-first convention.
Eight tools is a good scope for a niche research pipeline, with each mapping to a discrete step rather than duplicating work. A couple of tools (import_openacr_report, normalize_public_metadata) are narrow single-format utilities, which slightly inflates the surface relative to the broader planning tools.
The set covers discovery, planning, gap analysis, and output rendering, but there is no tool to persist a research record, candidate, or evidence artifact—several tools explicitly defer application to the host, leaving dead ends for an agent working end-to-end. There is also no update/edit or retrieval-by-id operation for existing records, only rendering of 'a local research record' assumed to already exist.