MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external systems and pull live monitoring data. Generator Labs runs a hosted MCP server so tools like Claude, ChatGPT, Cursor, and GitHub Copilot can read your monitoring data and run on-demand checks. No integration code required.
What Is MCP?
MCP is to AI tools what USB-C is to peripherals. Before USB-C, every device needed its own cable. Before MCP, every AI tool needed custom integration code to talk to external systems. MCP standardizes the connection: one protocol, one server endpoint, any MCP-aware client.
The protocol defines how an AI tool discovers capabilities (tools), calls them, and gets results. It uses JSON-RPC 2.0 over HTTP and supports both API key and OAuth authentication.
MCP was created by Anthropic and is now supported across Claude Desktop, Claude.ai, ChatGPT, Cursor, VS Code with Copilot, and other tools. It is an open standard hosted at the modelcontextprotocol.io GitHub organization.
What the Generator Labs MCP Server Does
Each connected AI client automatically discovers the available tools. They span four areas:
RBL monitoring. List hosts, check current listings, drill into per-source detail, run manual checks, and view listing history. The AI can tell you which of your IPs are currently blacklisted, why, and on which sources.
Certificate monitoring. List monitors, find expiring certificates, look up error state, and generate compliance audits. The AI can show you every cert expiring in the next 30 days, grouped by environment or severity.
Notifications. List contacts, contact groups, webhooks, and recent alerts. The AI can tell you who got paged and whether the delivery succeeded.
Account. Account summary with plan, balance, host counts, and recent activity.
Example: Debugging a Blacklist Issue
Here is how a real interaction might go. You paste a hostname into Claude:
"Check if mail.example.com is listed on any RBL and show me the details."
Behind the scenes, Claude calls rbl_manual_check to trigger an on-demand scan, then polls rbl_check_status for results. When the check completes, Claude calls rbl_get_listing_details on any flagged sources and rbl_list_sources to resolve internal IDs to human-readable names. What you see is a single answer listing each blacklist that flagged the host, what each source reported, and how long the lookups took.
No portal logins, no tabbing through screens, no manual copy-paste.
Example: Certificate Renewal Audit
"Audit my certs for the next 90 days."
Claude calls cert_compliance which returns a structured audit covering renewal hygiene, fingerprint stability, and configuration drift. The AI summarizes the findings, highlights certs that need action, and can even suggest next steps based on the patterns it sees.
How to Connect
The MCP endpoint is at https://api.generatorlabs.com/4.0/mcp. You can connect using either an API key or OAuth, depending on your tool.
Claude Desktop (API Key)
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"generator-labs": {
"type": "http",
"url": "https://api.generatorlabs.com/4.0/mcp",
"headers": {
"Authorization": "Basic <your-base64-credentials>"
}
}
}
}
Combine your Account SID and Auth Token as AC1234...:abcdef... and Base64-encode the result.
Claude.ai / ChatGPT (OAuth)
Both support MCP via custom connectors. Add a connector with the URL above, click Connect, and complete the OAuth flow in your browser. You choose which API application the grant binds to and which scopes to approve.
What MCP Is Not
MCP is not a replacement for the REST API. It is a conversational interface for querying and auditing. You cannot create or modify monitors through MCP. For automation and scripting, the REST API and SDKs are the right tools. MCP is for asking your AI assistant a question about your infrastructure and getting an answer immediately.
See the AI monitoring page | MCP configuration | Full tool reference | Sign up