{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-lineline-bot-mcp-server","slug":"npm-lineline-bot-mcp-server","name":"@line/line-bot-mcp-server","type":"mcp","url":"https://www.npmjs.com/package/@line/line-bot-mcp-server","page_url":"https://unfragile.ai/npm-lineline-bot-mcp-server","categories":["mcp-servers"],"tags":["line","bot","mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-lineline-bot-mcp-server__cap_0","uri":"capability://tool.use.integration.line.official.account.message.sending.via.mcp.protocol","name":"line official account message sending via mcp protocol","description":"Enables Claude and other MCP clients to send text, template, and rich messages to LINE users through the LINE Messaging API by translating MCP tool calls into authenticated LINE API requests. Implements the MCP server specification to expose LINE's message endpoints as standardized tools, handling OAuth token management and request serialization automatically.","intents":["Send automated notifications to LINE users from an AI agent without building custom API integration code","Trigger LINE bot responses based on Claude's reasoning and planning decisions","Build conversational workflows where Claude composes and sends LINE messages programmatically"],"best_for":["Teams building LINE bots with Claude as the decision-making layer","Developers integrating LINE messaging into multi-channel AI agent workflows","Non-technical founders prototyping LINE bot automations with Claude"],"limitations":["Requires valid LINE Official Account credentials and Channel Access Token — no fallback or mock mode documented","MCP protocol overhead adds latency compared to direct LINE API calls; suitable for async workflows but not real-time interactive messaging","No built-in message queuing or retry logic — failures propagate directly to the MCP client","Limited to LINE Messaging API capabilities; does not expose LINE Bot Designer or LIFF features"],"requires":["LINE Official Account with Channel ID and Channel Access Token","MCP client supporting tool calling (Claude 3.5+, other MCP-compatible LLMs)","Node.js 16+ runtime environment","Network access to LINE Messaging API endpoints (api.line.me)"],"input_types":["text (message content)","structured JSON (template objects, quick reply payloads)","user IDs or group/room IDs (recipient identifiers)"],"output_types":["HTTP response status (success/failure)","message ID (if returned by LINE API)","error details (if message send fails)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-lineline-bot-mcp-server__cap_1","uri":"capability://tool.use.integration.mcp.tool.schema.generation.for.line.message.types","name":"mcp tool schema generation for line message types","description":"Automatically generates MCP-compliant tool schemas that map LINE Messaging API message types (text, template, flex, quick reply) into callable functions with proper parameter validation and type hints. Uses JSON Schema to define input constraints, allowing MCP clients to understand available message capabilities and validate payloads before sending.","intents":["Enable Claude to discover what types of LINE messages it can send and their required parameters","Validate message payloads client-side before sending to LINE API, reducing failed requests","Generate type-safe tool definitions that guide LLM reasoning about message structure"],"best_for":["Developers building multi-message-type LINE bots where Claude needs to choose message formats dynamically","Teams using MCP clients that require explicit tool schemas for proper function calling","Builders who want LLM-friendly documentation of LINE message capabilities"],"limitations":["Schema generation is static and tied to the version of LINE Messaging API supported by this package — updates require package version bump","Does not validate complex nested structures (e.g., Flex Message JSON) beyond basic schema validation","No support for custom message types or extensions beyond official LINE Messaging API"],"requires":["MCP client that supports JSON Schema-based tool definitions","Knowledge of LINE Messaging API message type specifications"],"input_types":["configuration (LINE channel credentials)","message type selection (text, template, flex, etc.)"],"output_types":["JSON Schema objects (tool definitions)","MCP tool metadata (name, description, parameters)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-lineline-bot-mcp-server__cap_2","uri":"capability://tool.use.integration.line.webhook.event.routing.and.mcp.context.propagation","name":"line webhook event routing and mcp context propagation","description":"Receives incoming LINE webhook events (messages, joins, follows) via HTTP POST, parses the LINE signature for authenticity verification, and exposes event data as context or tool inputs to MCP clients. Implements LINE's webhook signature validation using HMAC-SHA256 to ensure requests originate from LINE's servers before processing.","intents":["Trigger Claude-based responses when users send messages to the LINE bot","Pass user context (user ID, message content, event type) to Claude for reasoning and decision-making","Build reactive workflows where incoming LINE events drive agent behavior"],"best_for":["Teams building event-driven LINE bots where Claude responds to user messages in real-time","Developers integrating LINE webhooks into multi-step agent workflows","Builders who need secure webhook handling with LINE signature verification"],"limitations":["Webhook processing is synchronous — long-running Claude reasoning may cause LINE webhook timeout (default 3 seconds); requires async job queue for complex workflows","No built-in event deduplication — duplicate webhook deliveries from LINE are processed multiple times unless client implements idempotency","Limited to events supported by LINE Messaging API webhooks; does not cover LINE Bot Designer or LIFF events","Requires public HTTPS endpoint with valid certificate — cannot run behind HTTP or self-signed certs"],"requires":["Public HTTPS endpoint with valid TLS certificate","LINE Channel Secret for webhook signature verification","Webhook URL registered in LINE Official Account settings","MCP client capable of receiving and processing webhook context"],"input_types":["JSON (LINE webhook payload)","HTTP headers (X-Line-Signature for verification)"],"output_types":["parsed event objects (user ID, message text, event type)","context for MCP client (user metadata, conversation history if stored)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-lineline-bot-mcp-server__cap_3","uri":"capability://tool.use.integration.line.user.profile.and.group.metadata.retrieval","name":"line user profile and group metadata retrieval","description":"Fetches user profile data (name, avatar, status message) and group/room metadata from the LINE Messaging API and exposes it as MCP tool outputs or context. Implements caching of profile data to reduce API calls and handles rate limiting from LINE's API gracefully.","intents":["Retrieve user information to personalize Claude's responses based on LINE user profile","Get group or room metadata to understand conversation context (group name, member count)","Build user-aware workflows where Claude adapts behavior based on LINE user attributes"],"best_for":["Developers building personalized LINE bots that reference user names or attributes in responses","Teams needing group context awareness in multi-user LINE conversations","Builders who want to reduce API calls through profile caching"],"limitations":["Profile data is cached with unknown TTL — stale data may be served if user updates their profile between cache refreshes","Rate limiting from LINE API is not explicitly handled; high-volume profile lookups may trigger 429 errors","User profile data availability depends on user privacy settings and bot permissions — some fields may be null","No support for custom user attributes or LINE Bot Designer user data"],"requires":["LINE Channel Access Token with user profile read permissions","User ID or group/room ID (obtained from webhook events or message context)"],"input_types":["user ID (string)","group/room ID (string)"],"output_types":["JSON object (user profile: displayName, pictureUrl, statusMessage)","JSON object (group metadata: groupId, groupName, groupIcon)"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-lineline-bot-mcp-server__cap_4","uri":"capability://tool.use.integration.line.rich.menu.and.quick.reply.management.via.mcp","name":"line rich menu and quick reply management via mcp","description":"Exposes LINE's rich menu and quick reply APIs as MCP tools, allowing Claude to create, update, or delete rich menus and quick reply buttons programmatically. Translates MCP tool calls into LINE Messaging API requests with proper JSON serialization for menu structure and button definitions.","intents":["Dynamically create or update LINE rich menus based on Claude's reasoning about user context","Attach quick reply buttons to messages sent by Claude to guide user interactions","Build adaptive UI experiences where menu structure changes based on conversation state"],"best_for":["Teams building interactive LINE bots where Claude controls the UI menu structure","Developers who want to dynamically adjust quick replies based on agent reasoning","Builders creating context-aware LINE experiences with adaptive menus"],"limitations":["Rich menu changes are global to the LINE bot — cannot be user-specific without complex workarounds","Quick reply buttons are limited to 13 buttons per message by LINE API constraints","No preview or validation of rich menu JSON before deployment — malformed menus fail silently","Rich menu updates have eventual consistency — changes may not appear immediately to all users"],"requires":["LINE Channel Access Token with rich menu and quick reply permissions","Knowledge of LINE rich menu JSON structure and button action types"],"input_types":["JSON (rich menu structure with areas and buttons)","JSON (quick reply button definitions with action types)"],"output_types":["rich menu ID (on creation)","success/failure status","error details (if menu creation fails)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-lineline-bot-mcp-server__cap_5","uri":"capability://tool.use.integration.line.broadcast.and.multicast.messaging.for.bulk.delivery","name":"line broadcast and multicast messaging for bulk delivery","description":"Implements LINE's broadcast and multicast APIs as MCP tools, allowing Claude to send messages to multiple users or groups in a single API call. Handles recipient list management and message payload serialization for bulk delivery scenarios.","intents":["Send notifications to all LINE bot followers without iterating through individual user IDs","Deliver targeted messages to a subset of users based on Claude's segmentation logic","Implement announcement workflows where Claude composes and broadcasts messages to large audiences"],"best_for":["Teams building notification systems or announcement bots on LINE","Developers who need to reach large user bases efficiently without per-user API calls","Builders creating marketing or engagement workflows with bulk messaging"],"limitations":["Broadcast messages are sent to all followers — no filtering or segmentation at the API level; requires client-side logic","Multicast is limited to 500 recipients per request — larger audiences require multiple API calls","No delivery confirmation or read receipts for broadcast messages","Broadcast messages may be rate-limited by LINE if sent too frequently"],"requires":["LINE Channel Access Token with broadcast/multicast permissions","User IDs or group IDs for multicast (broadcast requires no recipient list)"],"input_types":["message payload (text, template, or flex message)","recipient list (array of user/group IDs for multicast)"],"output_types":["request ID (for tracking broadcast delivery)","success/failure status","error details (if delivery fails)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-lineline-bot-mcp-server__cap_6","uri":"capability://memory.knowledge.line.conversation.state.persistence.and.context.management","name":"line conversation state persistence and context management","description":"Provides a mechanism to store and retrieve conversation state (user preferences, conversation history, session data) associated with LINE user IDs, enabling Claude to maintain context across multiple message exchanges. Implementation details (in-memory, database, external store) are abstraction-dependent but expose a key-value interface to MCP clients.","intents":["Store user preferences or conversation state so Claude can reference them in future messages","Maintain multi-turn conversation context without relying on LINE's message history","Build stateful workflows where Claude's responses depend on prior interactions"],"best_for":["Teams building conversational LINE bots that need to remember user preferences or history","Developers implementing multi-turn workflows where Claude needs persistent context","Builders creating personalized experiences that adapt based on conversation history"],"limitations":["No built-in persistence layer specified — state storage depends on deployment environment (in-memory loses data on restart)","No automatic cleanup or TTL for stored state — stale data accumulates without explicit deletion","Concurrent message handling may cause race conditions if state updates are not atomic","No encryption or access control for stored state — sensitive data requires application-level protection"],"requires":["External storage backend (database, cache, or file system) if persistence is required","User ID as the key for state lookups"],"input_types":["user ID (string)","state data (JSON object or arbitrary data)"],"output_types":["stored state (JSON object)","null (if no state exists for user)"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":25,"verified":false,"data_access_risk":"high","permissions":["LINE Official Account with Channel ID and Channel Access Token","MCP client supporting tool calling (Claude 3.5+, other MCP-compatible LLMs)","Node.js 16+ runtime environment","Network access to LINE Messaging API endpoints (api.line.me)","MCP client that supports JSON Schema-based tool definitions","Knowledge of LINE Messaging API message type specifications","Public HTTPS endpoint with valid TLS certificate","LINE Channel Secret for webhook signature verification","Webhook URL registered in LINE Official Account settings","MCP client capable of receiving and processing webhook context"],"failure_modes":["Requires valid LINE Official Account credentials and Channel Access Token — no fallback or mock mode documented","MCP protocol overhead adds latency compared to direct LINE API calls; suitable for async workflows but not real-time interactive messaging","No built-in message queuing or retry logic — failures propagate directly to the MCP client","Limited to LINE Messaging API capabilities; does not expose LINE Bot Designer or LIFF features","Schema generation is static and tied to the version of LINE Messaging API supported by this package — updates require package version bump","Does not validate complex nested structures (e.g., Flex Message JSON) beyond basic schema validation","No support for custom message types or extensions beyond official LINE Messaging API","Webhook processing is synchronous — long-running Claude reasoning may cause LINE webhook timeout (default 3 seconds); requires async job queue for complex workflows","No built-in event deduplication — duplicate webhook deliveries from LINE are processed multiple times unless client implements idempotency","Limited to events supported by LINE Messaging API webhooks; does not cover LINE Bot Designer or LIFF events","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.24,"ecosystem":0.38999999999999996,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.903Z","last_scraped_at":"2026-05-03T14:23:37.942Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-lineline-bot-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=npm-lineline-bot-mcp-server"}},"signature":"80UxgmQnazjoQIlEiuypZvxANbpFbxPGnJfCTG9beuiOXvXZGzlw4Aj/Az//rmcKu4g6S8/I7FNWEOYnAF4/Ag==","signedAt":"2026-06-23T06:43:14.761Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-lineline-bot-mcp-server","artifact":"https://unfragile.ai/npm-lineline-bot-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=npm-lineline-bot-mcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}