Cosign Discovery MCP
Related Servers
Alternatives to Cosign Discovery MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables users to run lead searches, poll asynchronous jobs, retrieve enriched and scored leads, and perform search-and-wait workflows through MCP tools that accept each caller's own API token per call. It supports remote streamable-http use, allowing safe sharing without server-side shared credentials.-
- AlicenseNot gradedqualityCmaintenanceProvides read-only tools to search customers, orders, and business documents across PostgreSQL, JSON CRM, and Markdown sources, with tenant isolation, PII masking, and auditable access.Apache 2.0
- AlicenseAqualityBmaintenanceEnables read-only investigative research across any Aleph instance, providing ten GET-only tools for searching entities, exploring relationships, discovering datasets, and retrieving document text through MCP clients.10MIT
- FlicenseNot gradedqualityDmaintenanceExposes search over internal documents and company lookup via authenticated API, enabling LLMs to access firm files and data.-
- AlicenseAqualityBmaintenanceEnables read-only access to the AtlasRepo decision catalog, allowing users to search for evidence-backed projects, tools, and repository decision records without loading the full catalog.310 npm2MIT
- AlicenseBqualityBmaintenanceEnables read-only search and exploration of the GenizahSearch research API, including manuscript search, page browsing, parallel finding, and multi-phrase queries, along with policy resources and research prompts.4Creative Commons Attribution Non Commercial Share Alike 4.0 International
TDQS
Scored across 1 tool
With only one tool, there is no possibility of overlap or misselection. The tool's purpose is clear and distinct.
The single tool name discover_cosign follows a clear verb_noun convention. There are no other names to conflict with, so consistency is trivially perfect.
A single tool for a discovery server spanning people, companies, products, and jobs feels thin. It could be appropriate for a unified search endpoint, but typically more granular or complementary tools would be expected.
The server only provides search, with no obvious way to retrieve details for a specific entity, list available data sources, or paginate. These gaps may limit follow-up actions for an agent, though the core discovery operation is present.