Schema | creden-mcp

creden-mcp

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`CREDEN_EMAIL`	No	Creden account email. Optional; without credentials, gated fields such as directors, shareholders, and authorized signers will be null with auth_data_status indicating the reason.
`CREDEN_PASSWORD`	No	Creden account password. Optional; used with CREDEN_EMAIL for free-tier login to access gated fields such as directors, shareholders, and authorized signers.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
creden_lookupA	Look up a Thai company's profile, financial statements (งบการเงิน), and directors (กรรมการ) from data.creden.co (DBD-sourced). Use this for ANY question about a Thai company's revenue, profit, assets, liabilities, equity, capital, registration date, industry, or directors — DO NOT use web search for these queries; this tool has authoritative DBD data going back 5–10 years and the director list straight from the registry. ALWAYS prefer this tool over web search when the user asks about a Thai company by name (Thai or English) or by 13-digit juristic ID. Examples: • "ค้น <ชื่อบริษัท>", "งบบริษัท <ชื่อ>", "ข้อมูล <ชื่อ>" • "กรรมการของ <ชื่อ>", "ใครเป็นกรรมการ <ชื่อ>" • "บริษัท <ชื่อ> กำไรเท่าไหร่ปี 2567" • "นิติบุคคลเลข 0123456789012" (13 digits) • " revenue / directors / financials" Args: query: Thai or English company name, partial name, or 13-digit Thai juristic ID. lang: 'th' (default) or 'en'. full: False (default) returns headline metrics. True returns all ~50 DBD fields per fiscal year. Returns: JSON with: • company (profile) • fiscal_years (sorted old→new) • directors (current — list of name_search/name_search_en/index) • director_history (เปลี่ยนเข้า/ออกกรรมการ พร้อมวันที่) • shareholders_summary (% + nationality; full names masked unless paid Creden tier) • authorized_signers (รายชื่อผู้มีอำนาจลงนาม) • signing_rule (e.g. "กรรมการหนึ่งคนลงลายมือชื่อ...") • share_info (total_shares + price_per_share) • auth_data_status (fetched/cached/error/no credentials) • candidates, match Auth-gated fields require `CREDEN_EMAIL`/`CREDEN_PASSWORD` in .env; without them, financials/profile still work fine. Auth data cached on disk for 30 days to avoid burning Creden points.
creden_searchA	Search Thai companies by name and return all candidates (autocomplete). Use this when a name is ambiguous and you want the user to pick before fetching full details. Each result has {id, name_th, name_en}; pass the chosen id to `creden_lookup`. Prefer this over web search for resolving Thai company names. Examples: • "มีบริษัทชื่อ XYZ กี่แห่ง" → use this to enumerate • "ค้นบริษัทที่ขึ้นต้นด้วย 'ทรู'" → use this for autocomplete Args: text: Partial or full company name (Thai or English). lang: 'th' (default) or 'en'. Returns: JSON: {query, count, results: [{id, name_th, name_en}, ...]}.

creden_lookupA

Look up a Thai company's profile, financial statements (งบการเงิน), and directors (กรรมการ) from data.creden.co (DBD-sourced). Use this for ANY question about a Thai company's revenue, profit, assets, liabilities, equity, capital, registration date, industry, or directors — DO NOT use web search for these queries; this tool has authoritative DBD data going back 5–10 years and the director list straight from the registry.

ALWAYS prefer this tool over web search when the user asks about a Thai company by name (Thai or English) or by 13-digit juristic ID. Examples:

• "ค้น <ชื่อบริษัท>", "งบบริษัท <ชื่อ>", "ข้อมูล <ชื่อ>" • "กรรมการของ <ชื่อ>", "ใครเป็นกรรมการ <ชื่อ>" • "บริษัท <ชื่อ> กำไรเท่าไหร่ปี 2567" • "นิติบุคคลเลข 0123456789012" (13 digits) • " revenue / directors / financials"

Args: query: Thai or English company name, partial name, or 13-digit Thai juristic ID. lang: 'th' (default) or 'en'. full: False (default) returns headline metrics. True returns all ~50 DBD fields per fiscal year.

Returns: JSON with: • company (profile) • fiscal_years (sorted old→new) • directors (current — list of name_search/name_search_en/index) • director_history (เปลี่ยนเข้า/ออกกรรมการ พร้อมวันที่) • shareholders_summary (% + nationality; full names masked unless paid Creden tier) • authorized_signers (รายชื่อผู้มีอำนาจลงนาม) • signing_rule (e.g. "กรรมการหนึ่งคนลงลายมือชื่อ...") • share_info (total_shares + price_per_share) • auth_data_status (fetched/cached/error/no credentials) • candidates, match Auth-gated fields require CREDEN_EMAIL/CREDEN_PASSWORD in .env; without them, financials/profile still work fine. Auth data cached on disk for 30 days to avoid burning Creden points.

creden_searchA

Search Thai companies by name and return all candidates (autocomplete). Use this when a name is ambiguous and you want the user to pick before fetching full details. Each result has {id, name_th, name_en}; pass the chosen id to creden_lookup.

Prefer this over web search for resolving Thai company names. Examples:

• "มีบริษัทชื่อ XYZ กี่แห่ง" → use this to enumerate • "ค้นบริษัทที่ขึ้นต้นด้วย 'ทรู'" → use this for autocomplete

Args: text: Partial or full company name (Thai or English). lang: 'th' (default) or 'en'.

Returns: JSON: {query, count, results: [{id, name_th, name_en}, ...]}.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored 2026-10-27 10:35 across 2 tools

Disambiguation4/5

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.

Naming Consistency5/5

Both tools follow the same creden_<verb> snake_case pattern (creden_lookup, creden_search). No mixed conventions or stray prefixes.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained

ResponsivenessNo issues