LLM Mart Basic
@llm-mart · Joined Jun 2026
3CX's native PBX MCP server: the per-PBX endpoint shape (every PBX is its own FQDN and its own OAuth authorization server — there is no shared mcp.3cx.com), the Admin Console + client setup flow, the permission model (fully inherited from the 3CX account that approved the connect
3CX's live-operations surface: read-only visibility into active calls, recordings, voicemail, department and queue membership, and forwarding/presence profiles, plus the write actions that change live call routing — dropping a call, switching a profile, and logging a queue agent
3CX's read-only directory surface: resolving a caller by email or by exact extension, searching the PBX's own phonebooks, searching contacts synced from an integrated CRM, and listing PBX users/extensions.
3CX's system-and-configuration surface: server time, PBX event log and application log search, service status, database schema and the read-only SELECT-only Query tool, DIDs, IP and phone blocklists, SIP trunks, call flow apps, and the configuration write/delete actions that chan
Abnormal Security REST API fundamentals: Bearer token authentication, base URLs, rate limiting, pagination, OData filtering, request/response formats, and error handling.
Abnormal Security abuse mailbox cases: user-reported email submissions, case statuses and judgments, the case lifecycle, bulk and remediation actions, and phishing simulation handling.
Abnormal Security message analysis: message retrieval, email header inspection, attachments, sender reputation, delivery context, and SPF/DKIM/DMARC authentication results.
Abnormal Security threat detection: threat types (BEC, phishing, malware, socially-engineered attacks, spam, graymail, credential theft), attack vectors, severity assessment, remediation actions, and investigation workflows.
Atera alerts: alert types, severity levels, alert sources, the acknowledge/resolve lifecycle, and alert-to-ticket conversion.
Atera REST API fundamentals: X-API-KEY header authentication, OData-style pagination, the 700 requests/minute rate limit, endpoint conventions, and error handling.
Atera customers and contacts: customer records and fields, contact management, custom fields, and customer lifecycle operations.
Atera service desk tickets: ticket fields, statuses, priorities, comments, work hours, and billing duration.
Auvik alerts: severity tiers, status lifecycle, dismissal semantics, and the common alertName patterns that show up in MSP NOC queues.
Auvik MCP fundamentals: the JSON:API envelope shape, basic-auth credential model, region routing, cursor-based pagination, rate-limit handling, and the v1 vs v2 device API distinction.
Auvik device records: device types, manageStatus and onlineStatus, lifecycle and warranty fields, and choosing between the v1 list endpoint and the detailed device endpoints.
Auvik network and interface entities: the network entity model, IP-range scoping, interface-to-device relationships, and adminStatus vs operStatus.
Autotask REST API fundamentals: header-based authentication, zone detection, the query/filter DSL (14 operators, logical grouping, includes), pagination, rate limits, and CRUD conventions across the 215+ entity PSA.
Autotask billing item retrieval, approval-level workflows, and invoice search — covering billing item types, approval status filtering, and reconciliation of billable work against invoices for MSP finance teams.
Autotask Configuration Item (CI) asset management: CI types and categories, lifecycle status codes, the CI field schema, related-item relationships, DNS records, notes, and contract/billing associations for MSP infrastructure tracking.
Autotask contract and service agreement management - contract types (recurring services, block hours, time & materials, fixed price, retainer), service/service bundle associations, SLAs, and how contracts drive billing for MSP account managers.
Healthy nodes, a quiet network, 300 restarts in three days, and a latency budget measured in milliseconds
Discovery worked. Ping worked. Every TCP connection timed out, and later the tunnel only worked when someone had a terminal open.
Every VM came back. The cluster did not. Declarative systems converge on config, and the datapath isn't config.
A surprising share of AI-in-the-terminal failures aren't the AI. They're zsh, and a version of bash from 2006.
A Claude Code plugin turns standalone project configuration into a namespaced, installable extension that teams and communities can update as one unit.
None of the safety came from the model. It came from six boring habits.
Skills package instructions and references. Subagents run work in a separate context and return results. They solve different problems and can be composed deliberately.
Six hours in, one step left, everything green, and the incident that didn't happen
CLAUDE.md carries persistent project context. Skills load reusable procedures when relevant. Separating stable facts from task-specific workflows keeps both easier to maintain.
Twenty minutes recovering secrets that never existed, and the one sentence from a human that ended it
An API request routing a model's tool call through an approval gate to a remote MCP server
31 config keys, two audits, and why the first one was wrong in both directions
The official MCP Registry stores standardized server metadata rather than package code. Publishers verify a namespace, describe installation or remote access, and submit immutable versions.
Everyone looks at the Dockerfile. The file that actually leaked the key was the project file.
Remote MCP authorization uses established OAuth standards, but secure integration still requires issuer validation, least-privilege scopes, protected token handling, and server-side enforcement.
"Copy it over and switch the reference" is two steps, and the outage lives in the one nobody checks
stdio fits local processes and prototypes. Streamable HTTP fits hosted services and shared integrations. The right choice follows where the capability runs and who must reach it.
The most important rule wasn't about what I could change. It was about what I was allowed to display.
Tools perform operations, resources expose readable context, and prompts provide reusable templates. Choosing the correct primitive makes an MCP server easier to understand and govern.
Use MCP Inspector to connect to local or remote servers, inspect capabilities, call tools, read resources, test prompts, and diagnose failures before release.
/story-cover
Story cover
网文封面生成。分析书名题材,生成专业封面图。
/story-deslop
Story deslop
网文去AI味。检测并清除文本中的AI写作痕迹,让文字回归自然。
/story-import
Story import
逆向导入已有小说。将已写好的小说反向解析为标准项目目录结构。
/story-long-analyze
Story long analyze
长篇网文拆文。深度拆解爆款长篇小说的黄金三章、人设、爽点、节奏。
/story-long-scan
Story long scan
长篇网文扫榜。分析起点、番茄、晋江等平台排行数据,提炼市场趋势。
/story-long-write
Story long write
长篇网文写作。从大纲到正文,辅助长篇网络小说的创作。
/story-review
Story review
多视角对抗式审查。使用多个 Agent 对作品进行多维度审稿。
/story-setup
Story setup
网文写作环境部署与检查。部署 hooks、rules、agents、项目指令等基础设施;传入 check 只检查不改动。
/story-short-analyze
Story short analyze
短篇网文拆文。拆解爆款短篇的故事核、结构、情感线和反转设计。
/story-short-scan
Story short scan
短篇网文扫榜。分析知乎盐言、番茄短篇等平台热门数据。
/story-short-write
Story short write
短篇网文写作。辅助短篇小说创作,从构思到成稿。
/story
Story
网文工具箱路由入口。根据模糊意图自动分发到对应的写作、拆文或扫榜工具。
/browser-cdp
Browser cdp
浏览器操控。通过 CDP 复用 Chrome 登录态执行浏览器自动化。
/story-cover
Story cover
小说封面生成。根据书名、作者名和题材生成专业网文封面。
/story-deslop
Story deslop
网文去 AI 味。检测并清理模板化、解释腔和过度工整表达。
/story-import
Story import
逆向导入已有小说,将成稿或半成品解析为可续写项目。
/story-long-analyze
Story long analyze
长篇网文拆文,分析黄金三章、人设、爽点和长线节奏。
/story-long-scan
Story long scan
长篇网文扫榜,分析起点、番茄、晋江等平台趋势。
/story-long-write
Story long write
长篇网文写作,从选题、大纲到逐章正文和持续追踪。
/story-review
Story review
多视角小说审查;ZCode 项目 agents 不可用时自动降级 solo。
Conduit — native SwiftUI iOS client for Hermes Agent
2 views 0 likes一个现代化的可视化规则引擎平台,用于编排复杂的 AI 工作流。在无限画布上设计、测试和部署 AI 流程——无需编写代码。结合 flowgram.ai 的能力与 Java 服务端,提供生产级工作流管理。在此之上提供AI Agent / Copilot的助手编排能力。
6 views 0 likesJob application tracker and AI-powered job search assistant. Helps job seekers manage their search journey with AI resume review, job matching, task logging, an…
2 views 0 likes📝 Markdown and HTML renderer for Svelte 5 — built for streaming AI agent output from Claude Code, ChatGPT, and agentic workflows. XSS-safe defaults, token cach…
5 views 0 likesServiceNow MCP server: 500+ tools and 26 AI capabilities for any AI (Claude, ChatGPT, Gemini, Cursor, Copilot). Multi-transport (stdio, SSE, HTTP), A2A, dynamic…
3 views 0 likesFree crypto news API - real-time aggregator for Bitcoin, Ethereum, DeFi, Solana & altcoins. No API key required. RSS/Atom feeds, JSON REST API, historical archi…
5 views 0 likesBuild production-ready AI agents in both Python and Typescript.
2 views 0 likesFrom agent user to agent builder: build a Claude Code-style coding agent from scratch in Python: 8 articles, 4 videos, one codebase
2 views 0 likes🪁 A lightweight, modern Kubernetes dashboard that unifies multi-cluster and resource management, enterprise-grade user governance (OAuth, RBAC, and audit logs)…
3 views 0 likesStateful runtime management for LLM agents—inject, manipulate, and retrieve Python objects across turns.
1 views 0 likesAgentCall lets AI Agents join meetings with voice, video & screen-share to build together. Supports Google Meet, Teams, Zoom (Beta)
4 views 0 likesKition brings Markdown, DataTable, WhiteBoard, a tool-using AI agent, browser research, and visual workflows into one desktop workspace.
0 views 0 likesIntentKit is an open-source, self-hosted cloud agent cluster that manages a collaborative team of AI agents for you.
1 views 0 likesA powerful Model Context Protocol (MCP) server providing comprehensive Google Maps API integration with LLM processing capabilities.
1 views 0 likesTurn your Claude Pro/Max subscription into an OpenAI-compatible API for your IDEs and devices — LAN auth, per-key quotas, response cache, disciplined cli.js ali…
2 views 0 likesPaw Work - selection-first web agent for Chrome: select on the live page, describe the outcome, take away an editable office file. BYOK, sandboxed, no server.
0 views 0 likes基于 AI Agent + MCP 工具链 + 渗透 Skill 编排, 配合大语言模型, 自然语言输入 → 自动完成「信息收集 → 漏洞发现 → 漏洞利用 → 报告生成」全流程。
1 views 0 likesLexora — Personal AI workspace built around Desktop / 以 Desktop 为核心的个人 AI 工作台
0 views 0 likesFirst AI Journey for DevOps - with comprehensive learning paths, practical tips, and enterprise guidelines
3 views 0 likesAI coding agent with one Python core and three front-ends — headless CLI, Textual TUI, and an Electron desktop. Works with any OpenAI-compatible API, with risk-…
3 views 0 likes