CEOInterviews.AI: C-Suite Intelligence for AI Agents
Server Details
Connect your AI agent to 20,000+ executives (CEO, CFO, COO) of all major companies, 1M+ verified quotes, and full interview transcripts. S&P 500, NASDAQ, AI startups, Federal Reserve officials. 4 MCP tools, pay only for what you use. $5/1,000 results, no minimum, no commitment, cancel anytime. You only pay for returned valid results.
You must create an API key at https://mcp.ceointerviews.ai and then authenticate here using header
Authorization: Bearer
For access to our full data API please access https://ceointerviews.ai
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.9/5 across 4 of 4 tools scored. Lowest: 3.3/5.
Each tool serves a distinct layer of the intelligence workflow: entity discovery (companies vs executives) and content retrieval (quotes vs full transcripts). No functional overlap exists between the four tools, and search_executives explicitly clarifies its relationship to the other tools.
All tools follow a consistent verb_noun snake_case pattern. 'Search' is used for discovery operations (companies, executives, quotes) while 'get' is used for document retrieval (transcripts), accurately reflecting distinct operation types.
Four tools is slightly minimal but reasonable for this focused domain. Each tool earns its place in the intelligence-gathering workflow, though additional tools for date filtering, trending topics, or direct ID-based lookup would strengthen the surface.
Core read operations for the intelligence domain are covered: entity discovery and content retrieval. Minor gaps include no direct get-by-ID endpoints for companies/executives (relying solely on fuzzy search) and no metadata tools for browsing available sources, but the essential transcript→quote→entity linkage is complete.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!