creden-mcp
Related Servers
Alternatives to creden-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceProvides access to the Securities Exchange of Thailand (SET) to retrieve comprehensive financial statements for listed companies. It enables AI agents to query income statements, balance sheets, and cash flow statements with historical data support.113-

BizVerify MCP Serverofficial
AlicenseAqualityDmaintenanceEnables AI agents to verify and search business entities across US state and international company registries, providing real-time confirmation of legal existence, status, and filings.9MIT
global-databaseofficial
FlicenseNot gradedqualityBmaintenanceEnables LLM agents to access Global Database's company intelligence, including company profiles, financials, ownership, people search, prospecting, and KYB/compliance lookups against official registries.-- AlicenseNot gradedqualityBmaintenanceProvides real-time company verification and corporate intelligence by accessing global registries like UK Companies House, Singapore ACRA, and OpenCorporates. It enables AI agents to perform KYC tasks, retrieve company profiles, and conduct automated risk assessments for due diligence workflows.80 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables searching and retrieving detailed information about Thai juristic persons, foreign entities, financial statements, directors, shareholders, and statistics from the Department of Business Development data warehouse.2-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to look up Polish company registry data from KRS, including registry profiles, current and historical board, shareholder and proxy connections with dates, change timelines, financial statements, state aid and public contracts. All tools are read-only and reachable over a remote Streamable HTTP endpoint, with the same data also exposed through a REST API.MIT
TDQS
Scored across 2 tools
creden_search resolves ambiguous names into candidates, while creden_lookup fetches full company detail by name or 13-digit ID. The boundary is explicitly documented (search → pick id → lookup), though the two tools do overlap when a lookup is given a name instead of an ID.
Both tools follow the same creden_<verb> snake_case pattern (creden_lookup, creden_search). No mixed conventions or stray prefixes.
Two tools is thin even for a narrow read-only domain; a search+fetch pair covers the core flow but there is little room for argument. It is not a mismatch, just borderline.
Search plus a very rich lookup (profile, multi-year financials, directors, history, shareholders, signers) covers the stated purpose well. Remaining gaps (e.g. no bulk/list enumeration or tier/auth management surface) are minor and mostly handled by the lookup's own flags.