OpenSincera MCP Server
Related Servers
Alternatives to OpenSincera MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables querying Google Ads Transparency data for advertiser suggestions, creatives, and ad history through a hosted API with built-in anti-bot handling.-
- AlicenseNot gradedqualityBmaintenanceEnables interaction with Sam's Club Sponsored Ads APIs through spec-driven endpoint discovery and an authenticated proxy with automatic RSA-SHA256 request signing.MIT
- AlicenseNot gradedqualityAmaintenanceEnables searching and retrieving researcher profiles, works, affiliations, funding, and peer review records from the ORCID registry via MCP, supporting STDIO or Streamable HTTP.283 npm3Apache 2.0
- FlicenseAqualityDmaintenanceEnables programmatic management of NewsBreak advertising campaigns, ad sets, ads, and assets via the NewsBreak Advertising API.141-
- -licenseNot gradedqualityNot gradedmaintenanceProvides access to the OpenAlex API, enabling search and retrieval of scholarly works, authors, sources, and more.-
- AlicenseAqualityCmaintenanceEnables interaction with the public Digital Asset Scan API to analyze digital assets, list assets, retrieve methodology, and poll asynchronous analysis jobs over MCP.4MIT
TDQS
Scored across 4 tools
The first three tools (get_publisher_by_domain, get_publisher_by_id, get_publisher_metadata) have overlapping purposes, as they all retrieve publisher information with only slight variations in input parameters, which could cause confusion for an agent. However, the health_check tool is clearly distinct, providing a separate API connection check function.
The tool names follow a consistent verb_noun pattern (e.g., get_publisher_by_domain, health_check), with all using snake_case. The only minor deviation is that health_check uses a compound noun without a preceding verb like 'get', but it still fits the general naming convention.
With only 4 tools, the server feels thin for its apparent domain of publisher analytics, as it lacks operations for updating, creating, or deleting data, which limits functionality. However, the count is reasonable for a basic read-only interface.
The tool set is severely incomplete for a publisher analytics domain, as it only provides read operations (get and health check) without any create, update, or delete capabilities. This creates significant gaps that could lead to agent failures when full lifecycle management is needed.