Retrieve parent plurk and normalized replies for a specific thread using provided credentials to access conversation context.
510,535 tools. Updated 2026-09-04 06:48
"Plurk" matching MCP tools:
- Create new Plurk posts with secure authentication while automatically enforcing daily posting limits to maintain controlled social media activity.
- Post replies to Plurk threads using the plurk-mcp server. Reply to owned threads or explicit mentions with provided credentials and content.
- Retrieve the authenticated Plurk user profile using provided API credentials to access account information and context.
- Score an engram's statement, domain, and tags against scope covers to suggest matching registered scopes. Returns ranked candidates; advisory only.Apache 2.0
- Persist multiple engrams in a single batch call, applying sequential deduplication and isolating per-item failures, so bulk knowledge storage takes one request instead of many.Apache 2.0
Matching MCP Servers
- FlicenseAqualityDmaintenanceA secure Model Context Protocol server for interacting with Plurk, allowing agents to read account context, post updates, and manage replies. It includes built-in safety guardrails such as daily post limits and reply cooldowns to ensure controlled execution.6
- AlicenseAqualityCmaintenanceA Model Context Protocol server for Plunk, the open-source self-hosted email platform. Provides 84 tools for transactional email, contacts, campaigns, segments, templates, workflows, events, and analytics through the Plunk API.11272MIT
- Search stored engrams by BM25 keyword matching to retrieve relevant agent memory entries.Apache 2.0
- Diagnose PLUR engine health: check embedding model load, hybrid search operation, and remote-store auth token expiry. Run first when recall feels off or engrams stop syncing.Apache 2.0
- Upload an image to Plunk for use in templates or campaigns by providing base64-encoded bytes, filename, and MIME type.MIT
- Pin or unpin engrams to control which memories are always loaded. Pinned engrams bypass relevance filtering, ensuring critical rules and principles are available every session.Apache 2.0
- Review a pack before installing it—see its manifest, engram list, security scan, and warnings to make an informed decision.Apache 2.0
- List configured engram stores with scope, path, and engram counts. Includes self-describing scope metadata to help you choose the right memory scope.Apache 2.0
- Discover which scopes your remote token is authorized for and identify any not yet registered locally. Optionally register all authorized-but-unregistered shared-family scopes in one step, while skipping personal scopes.Apache 2.0
- Use a contact's public ID from unsubscribe links to re-subscribe them without needing their regular UUID.MIT
- Inject relevant context using hybrid BM25 and embedding search. Falls back to BM25 when embeddings are unavailable, ensuring reliable context selection for tasks.Apache 2.0
- Register a new engram store as a filesystem path or remote URL with token, and associate it with a scope. Use it to add team or read-only stores to an agent's memory.Apache 2.0
- Report a procedural engram failure to trigger LLM-based procedure evolution, using the failure context to revise and improve the procedure. Only for procedural engrams.Apache 2.0
- Track an event for a contact, creating the contact if needed, to drive automation workflows and audience segments.MIT
- Persist a reusable learning, preference, or correction into agent memory; add tags, scope, validity dates, and superseded entries to keep recall relevant.Apache 2.0
- Install an engram pack from a directory path. Run a security scan to block secrets, detect conflicts with existing engrams, and record install metadata in the registry.Apache 2.0