Reasoning MCP server
PubNub MCP Server
Version history of discovered tools, schemas, and declared agent authority.
OBSERVED INTERFACE
Capability surface
Modelara’s observed declarations are shown separately from its derived effect classifications.
- 6
- 1
- 2
- 8
Unknown means Valyd could not determine the capability's effect confidently from the declared interface and static evidence. It is not treated as safe.
- Package
- @pubnub/mcp@2.3.15
- Registry
- npm
- Published
- Nov 12, 2026
- Integrity
sha512-JxKmPxrq+b2oLg4KQUUutw1b7ojUw5WMrWb7HKi1J1bwz36iKtw4upcXr3kAo+usvwpxEy73bnZJ8bVTlDLkvQ==- Analyzer
- modelara v0.1.8 · policy not recorded
17 capabilities
| Capability | Type | Derived effect | First observed in Valyd coverage | Last changed |
|---|---|---|---|---|
get_chat_sdk_documentationpubnub-mcp-server:tool:get_chat_sdk_documentationObserved interface and hashesRetrieve Chat SDK documentation for building chat/messaging applications. **When to use:** - Building ANY chat or messaging application (1:1, group, channels) - Need typing indicators, read receipts, @mentions, unread counts - Want message threads, reactions, pinned messages, moderation - Need user/channel management with chat-specific features - Prefer rapid development with intuitive methods like sendText(), startTyping(), join() **Do NOT use for:** - Non-chat real-time apps (IoT, gaming state, analytics) → use "get_sdk_documentation" - Conceptual guides → use "how_to" **Example features:** - messages-send-receive, messages-threads, messages-reactions - channels-create, channels-join, channels-typing-indicator - users-mentions, users-presence Returns code examples and API references for the specified language/feature. Input schemasha256:627c35bfd75543d9ed42d7def4e352c14166c0250cd59fd983677777aa68d03dOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | 2.3.15 | |
get_general_migration_guidepubnub-mcp-server:tool:get_general_migration_guideObserved interface and hashesRetrieve general migration guides for cross-cutting PubNub platform changes. **When to use:** - Migrating to a new encryption standard (e.g. 256-bit encryption) - Upgrading push notification setup (e.g. APNs HTTP/2, FCM v1) - Migrating to new API versions (e.g. Access Manager v3, Objects v2) - Replacing deprecated features (e.g. legacy webhooks) **Do NOT use for:** - SDK version upgrades (e.g. JavaScript v7→v8) → use "get_sdk_migration_guide" - General SDK documentation → use "get_sdk_documentation" Returns the migration guide content for the specified slug. Input schemasha256:77314c99b32d5069848d877b05b38f87523efa35fedeae60570d8ffada881111Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
get_pubnub_messagespubnub-mcp-server:tool:get_pubnub_messagesObserved interface and hashesFetches historical messages from one or more PubNub channels. Call this tool whenever you need to access past message history. Provide a list of channel names. Returns message content and metadata in JSON format. Supports pagination with start/end timetokens and count limit. Input schemasha256:2b04fce5198d5354a808fd037903691831ca183de3c93a6f511c34a005c24f46Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
get_pubnub_presencepubnub-mcp-server:tool:get_pubnub_presenceObserved interface and hashesRetrieves real-time presence information. Use 'channels'/'channelGroups' for HereNow (occupancy/users in channel) and/or 'uuid' for WhereNow (channels a user is in). Returns presence data in JSON format. Requires publish and subscribe keys from your PubNub keyset. Input schemasha256:a0aad41a97b9a6943cd017024c8b7c180f0ca72f3b5962fae5f2aa6dc9a55258Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
get_sdk_documentationpubnub-mcp-server:tool:get_sdk_documentationObserved interface and hashesRetrieve Core SDK documentation for low-level real-time features. **When to use:** - Building NON-CHAT real-time apps (IoT, gaming state sync, live analytics, notifications) - Need fine-grained control over pub/sub, presence, storage, or access management - Implementing custom real-time patterns - Need API reference for specific SDK methods (publish, subscribe, history, etc.) - Storing and syncing application state (users, channels, memberships, custom entities) → use feature "data-sync" (DataSync is the successor to App Context; prefer it over "appcontext-*" features where available) - For Python SDK usage always request about sync or asyncio version of langauge. **Do NOT use for:** - Chat/messaging apps → use "get_chat_sdk_documentation" instead - Conceptual guides → use "how_to" Returns code examples, API references, and implementation guides for the specified language/feature combination. Input schemasha256:88c1aad7d6ab4f6deb7998946f03ac5bdb62241cde3ae11d37bb66ea54370e7aOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | 2.3.15 | |
get_sdk_migration_guidepubnub-mcp-server:tool:get_sdk_migration_guideObserved interface and hashesRetrieve SDK migration guides for upgrading between PubNub SDK versions. **When to use:** - Upgrading a PubNub SDK to a newer major version - Need step-by-step instructions for migrating breaking changes - Refactoring a codebase after a PubNub SDK version bump **Do NOT use for:** - General SDK documentation → use "get_sdk_documentation" - Chat SDK documentation → use "get_chat_sdk_documentation" Returns the migration guide content for the specified language and target version. Input schemasha256:104bb0e1a1b4f6d71adcd940dcad7a30b75130b0dbbcdee01642eafb0baabb48Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
get_usage_metricspubnub-mcp-server:tool:get_usage_metricsObserved interface and hashesFetches usage metrics from the PubNub Admin API for an account, app, or keyset. **Parameters:** - entityType: 'account', 'app', or 'keyset' - entityId: The ID of the entity - from: Start date (inclusive) in YYYY-MM-DD format - to: End date (exclusive) in YYYY-MM-DD format - metrics: Array of metric names to retrieve **Available Metric Categories:** - Core transactions: txn_total, mtd_txn_total, replicated, signals, edge - MAU/UUID: mtd_uuid, uuid, pn_uuid - Messages: msgs_total, publish, subscribe_msgs, history_msgs, files_msgs, push_msgs - Storage: bytes_stored, bytes_stored_messages, bytes_stored_files, etc. - Access Manager: accessmanager_grants_transactions, accessmanager_audits_transactions - Functions: executions, kv_read_transactions, kv_write_transactions - History: history_transactions, history_with_actions_transactions - Message Actions: message_actions_add_transactions, message_actions_get_transactions - Objects/App Context: objects_create_user_transactions, objects_get_user_transactions, etc. - Presence: presence_herenow_transactions, presence_wherenow_transactions - Push Notifications: apns_sent_transactions, gcm_sent_transactions - Subscribe: subscribe_transactions, subscribe_heartbeats_transactions - Publish: publish_transactions, publish_bytes - Signal: signal_transactions - Files: files_publish_transactions, files_get_file_transactions Input schemasha256:a2eb82a45bf82f598d989b33df293fcc84e056186c998934355568168582ed88Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
how_topubnub-mcp-server:tool:how_toObserved interface and hashesRetrieve conceptual guides for specific PubNub use cases and integrations. **When to use:** - Learning how to implement a specific use case (gaming, healthcare, IoT) - Need step-by-step integration guide for a platform (Unity, Unreal etc) - Understanding PubNub features in context (presence, push notifications, functions) **Do NOT use for:** - API reference or code samples of a specific PubNub features → use `get_sdk_documentation` or `get_chat_sdk_documentation` - General best practices → use `write_pubnub_app` Input schemasha256:cd67b391c8fe226b9653e32d9fce983e862c260640656d89f26d8209f6255f2aOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
insightspubnub-mcp-server:tool:insightsObserved interface and hashesQueries PubNub Insights — read-only aggregated analytics scoped to an account, app, or keyset. **Entity scoping:** Every query requires an entityType ('account', 'app', or 'keyset') and an entityId. For 'account' and 'app', the entityId is the numeric ID. For 'keyset', the entityId is the subscribe key (sub-c-...). Two endpoints, picked automatically by metric name: - /v2/insights → aggregated metrics (unique_channels, unique_users, messages, etc.) - /v2/insights/top → ranked metrics (top_20_channels, top_20_users, top_10_message_types, etc.) TOOL SELECTION GUIDE — Insights Claude Behavior: 1. Group-aware: Insights metrics are organized into 5 functional groups — Channels, Users, Messages, User Behavior, Devices. When a user asks an analytic question, pick the right group first and then the specific metric. See the how-to guides: how_to(slug="get-insights-api-access"), channels, users, messages, user-behavior-and-devices, filters. 2. Period rules (enforced at runtime): - Duration metrics (avg_user_duration, unique_users_by_duration_timeframe, top_*_channels_with_user_duration) → period=hourly ONLY. - Top-N metrics (top_20_*, top_1000_*) → hourly or daily ONLY (no weekly/monthly). - Country metrics → hourly or daily ONLY. - new_vs_recurring_users → daily / weekly / monthly only (NOT hourly). - All other metrics → all four periods supported. 3. Top metrics REQUIRE category. Without it, the call errors. Valid categories: by_messages, by_chats, by_subscribers, by_users_with_messages, by_users_with_chats, by_subscribed_channels, all. 4. Top-metric filtering uses `filters` (JSON), not `filter`. Use `filters` on top_20_* / top_1000_* for thresholds (count_messages gt), allowlists (channel_name in), and prefixes (uuid startsWith). Use `filter` only on channel_patterns. 5. UTC timestamps. fromDate and toDate are YYYY-MM-DD in UTC. Always frame the response with the date range and timezone so the user has unambiguous context. 6. Top-N counts CANNOT be summed across periods. If the user asks for "top channels this week" and you query with period=daily, return one ranking per day, not a weekly sum. 7. Default to period=daily for most queries. It supports the widest set of metrics and gives a clean trend view. Use hourly only when intra-day granularity is needed or for duration metrics. 8. Account must be on Insights Premium. Free plan has no API access. Pro existing customers may need to upgrade from Standard to Premium. If a 403 comes back, surface this as the likely cause. 9. The tool does not write or store anything. Insights is strictly read-only. Input schemasha256:99e35933e6fb9f9ea910d8b94c0f8c17d714165380e7f557bdda06ed2aac3d54Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
manage_app_contextpubnub-mcp-server:tool:manage_app_contextObserved interface and hashesManages PubNub App Context (Objects API) for users, channels, and memberships. Supports CRUD operations including get, set, remove, and getAll. Use this tool to manage user profiles, channel metadata, and membership relationships in your PubNub application. Input schemasha256:6b9a833a252a0332e13756e0b330bcee91f702672da7fd65cf52a4189ee37d43Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
manage_appspubnub-mcp-server:tool:manage_appsObserved interface and hashesManages PubNub apps with operations: list, create, update. - 'list': List all apps on your account. - 'create': Create a new app. User must provide data.name. - 'update': Update an existing app name. User must provide data.id and data.name. Input schemasha256:a9668e633ba79f3cf2726798600b6365b1ea0a668fbf8e8082401de3cbcfcb07Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
manage_functionspubnub-mcp-server:tool:manage_functionsObserved interface and hashesManages PubNub Functions v2 via the Functions Admin API (admin-api.pubnub.com/v2/faas). Covers the full resource surface: packages, revisions, deployments, KV store, secrets, scheduled events, catalog (blueprints), and account limits. **Resources and operations** (the handler validates the resource/operation pair): - package: list, get, create, update, delete, list-revisions - revision: get, create, update, delete, list-functions, list-deployments, list-test-inputs, create-test-input, update-test-input, delete-test-input - deployment: create, get, delete, start, stop, rolling-update, intersected, stop-by - kv-store: list, get, set, delete, increment, decrement (use kv_type: string | json | counter) - secret: list, set, delete - scheduled-event: list, get, create, update, delete - catalog: list-blueprints, get-blueprint, list-function-blueprints, list-parameters, list-all-parameters, get-parameter, import - limit: get-running-deployments **Core model (v2):** a Package groups Functions and tracks immutable Revisions. A Revision is deployed to a keyset as a Deployment, which you then start/stop. To ship a Function end-to-end: (1) package create (creates the initial revision + functions), (2) deployment create with the packageRevisionId on the target keyset, (3) deployment start. Use rolling-update to swap a running deployment to a new revision with no downtime. **Authentication:** uses the same Service Integration key as manage_illuminate (PUBNUB_API_KEY env var, or an OAuth Bearer token in HTTP mode). Permissions follow the Admin API model (each operation is annotated in the FaaS OpenAPI spec, the canonical source): packages, revisions, test-inputs, limits, and blueprint import require functions.package:read|write on the ACCOUNT; deployments and scheduled events require functions.package-deployment:read|write on the KEYSET; KV store and secrets require keyset:read|write on the KEYSET. (These are Admin API permission scopes, not portal user roles.) TOOL SELECTION GUIDE — Functions Claude Behavior: 1. Keyset scoping differs by resource. kv-store and secret operations take subscribe_key (sub-c-..., sent as the subkey query param) — it must be provided as an argument. deployment create, deployment intersected, and catalog import take the NUMERIC keyset id as keyset_id (deployment lifecycle ops start/get/delete take only the deployment id; stop also accepts an optional force flag, and intersected accepts an optional function_type filter). scheduled-event operations take no keyset (the keyset is derived from the referenced deployment). Package, revision, catalog-read, and limit operations are account-scoped. 2. ID chain — capture and reuse: package create → packageId + revision id; deployment create → deployment id. revision list-functions → function revision ids (needed for test inputs). 3. KV store vs Vault: kv-store is the Functions KV database (string/json/counter). Use increment/ decrement only with kv_type="counter". secret manages the Vault (encrypted; values are never returned by list). These mirror the require('kvstore') and require('vault') modules used in Function code — see how_to(slug="use-pubnub-functions-kvstore-module") and "...vault-module". 4. Deployment lifecycle is stateful and has side effects. Account has a running-deployments limit (check via resource=limit, operation=get-running-deployments). Starting a deployment consumes the limit. NEVER delete a package, revision, or deployment without explicit user confirmation; a package must be stopped before it can be deleted. 5. Authoring vs managing: this tool MANAGES Functions resources. To WRITE the JavaScript handler code, follow how_to(slug="develop-pubnub-functions") and the module guides. Function code must be a default export with the correct signature for its eventType (request/response for On Request, request for Before/After events, event for On Interval) and must return the matching completion call. 6. Catalog: use list-blueprints to browse templates, then import to create a package (and deploy to a keyset) from a blueprint. Inspect required parameters via list-function-blueprints / list-parameters before importing. 7. Function logs: a running Function's console.log/console.error output is PUBLISHED to the channel output-rev-<functionRevisionId>-key-<keysetId> (there is no log API). To read logs, subscribe to that channel with the subscribe_and_receive_pubnub_messages tool (or any SDK). Get functionRevisionId from revision list-functions; keysetId is the numeric keyset id. 8. Errors: the API returns a FAAS-* envelope ({ errors: [{ code, message }] }). Surface the code and message. Common cases: 403/FAAS-1027 (the Service Integration lacks the required permission scope for the operation — e.g. functions.package-deployment:write on the keyset), running-deployment limit reached, and "package must be stopped before deletion". Input schemasha256:b730c3f8aa30abb56ad02f5976d6b39f209318e3dbdeabc1775430a759f01632Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
manage_illuminatepubnub-mcp-server:tool:manage_illuminateObserved interface and hashesManages PubNub Illuminate resources with operations: list, get, create, update, delete, activate, deactivate, get-fields, execute-adhoc, publish-fake-data, verify-query, check-action-log, raw-snapshot, aggregate, field-health, and custom-query. Supports full CRUD for: Business Objects, Metrics, Queries, Decisions, and Dashboards. **Operations:** - list: GET all resources of a given type - get: GET one resource by id - create: POST a new resource (Decisions use automatic 2-step POST→PUT workflow) - update: PUT/replace a resource - delete: DELETE a resource (Business Object delete cascades to all associated resources) - activate / deactivate: toggle isActive (Business Object) or enabled (Decision) - get-fields: fetch Query output field definitions (required before building a Query Decision) - execute-adhoc: run a one-off Query pipeline without saving it - publish-fake-data: generate type-aware fake PubNub messages and publish them to test Decisions. Fetches BO field schema and produces realistic values per field type. Payloads are NESTED to match each field's JSONPath (e.g. `$.message.body.application.user_id` produces `{ application: { user_id: ... } }`, not the flat key `"application.user_id"`), so JSONPath resolution works against nested BO schemas. Pass secret_key when the keyset has Access Manager enabled — initializing with the secret key grants root permissions and bypasses 403 errors. Alternatively pass auth_key with a token from grantToken(). Failures are reported per-message; partial publishes return success with a 'failures' array. NOTE: Illuminate ingests with a 20–30 second delay — wait before querying after publish. - verify-query: execute a saved Query by id and return results (confirms data is flowing) - check-action-log: fetch recent Decision action log entries to verify a Decision fired - raw-snapshot: return the most recent rows from a Business Object via ad-hoc query - aggregate: group and count BO data by user/channel or custom group_by fields - field-health: check which BO fields are populated vs empty (reveals JSONPath mismatches) - custom-query: run a fully custom ad-hoc pipeline **ID Dependency Chain — always capture before proceeding:** Business Object → id, fields[*].id Metric → id, measureId, dimensionIds Query → id, then call get-fields for output field IDs Decision → id, inputFields[*].id, outputFields[*].id, actions[*].id Dashboard → id, charts[*].id **Critical Decision rules:** hitType ('SINGLE'|'MATCH_ALL') and executeOnce (boolean) are required — omitting causes HTTP 500. Handler auto-injects safe defaults (hitType=SINGLE, executeOnce=false, activeFrom=now, activeUntil=now+2yr). executionFrequency (NOT 'evaluationFrequency' — that name is invalid) is the decision evaluation cadence in seconds: it schedules evaluation for METRIC/QUERY decisions, and for BUSINESSOBJECT decisions must stay a plan-supported value (commonly 3600), never null (a null value passes the API but makes the portal reject saves). Per-action throttling goes on rules[].actionValues[].executionLimit*, not on executionFrequency. The 2-step create workflow resolves field/action names → UUIDs in: action templates (both output variable names AND input field names — input names are sentinel-substituted pre-POST and restored post-POST), inputValues.inputFieldId, outputValues.outputFieldId, outputValues.value (dollar-brace), actionValues.actionId, and actionValues.executionLimitInputFieldIds. Use names everywhere. If the PUT step fails the handler deletes the orphaned scaffold automatically. **CRITICAL — QUERY decision input field naming:** For sourceType=QUERY decisions, each inputField.name MUST exactly match the source query's output field alias (case-sensitive, including underscores). Illuminate binds query result rows to decision inputs by NAME — not by sourceId. If names don't match, the decision will be created and activated successfully but will silently NEVER fire even with valid data. Always run get-fields on the source query first and copy the 'field' values verbatim into your decision's inputFields[].name. **Business Object limits (handler pre-flights and rejects on violation):** - name: 1-100 characters - fields[].name: 1-50 characters - max 100 fields per BO - **max 5 TEXT_LONG fields per BO** (use TEXT, which holds 256 chars, for shorter strings) - keep `description` to ONE concise sentence (~under 200 chars). The API does NOT reject long descriptions, but an overly long one breaks the Admin portal Business Object detail page (it fails to render) — treat 'concise' as a hard rendering requirement, not a style preference. **Decision action types:** - PUBNUB_PUBLISH (portal label: Publish) — requires ALL four fields nested inside 'template': pubkey, subkey, channel, body. - WEBHOOK_EXECUTION (Webhook) - APPCONTEXT_SET_USER_METADATA (portal label: Update User) - APPCONTEXT_SET_CHANNEL_METADATA (portal label: Update Channel) - APPCONTEXT_SET_MEMBERSHIP_METADATA (portal label: Update Membership) All action config goes INSIDE the action's 'template' object — never as top-level action props. Putting PUBNUB_PUBLISH channel/body at the action top level does NOT error but stores template:null, which then breaks the portal Decisions page ('There was a problem loading your Decisions'). Metric/query filters can only reference dimensions (a filtered field must be in dimensionIds), else 400 'Filter fields must be dimensions'. **Decision action default:** When the user doesn't specify what action to fire, default to actionType='PUBNUB_PUBLISH' with a message body that includes the relevant input/output values via dollar-brace template references. PUBNUB_PUBLISH requires no external infrastructure and is trivially verifiable via check-action-log or by subscribing to the target channel. Only use WEBHOOK when the user has provided a specific URL. NEVER delete without explicit user confirmation. TOOL SELECTION GUIDE — Illuminate Claude Behavior: 1. Intent-first: Always start from the user's desired outcome. Ask what they want to achieve before suggesting Business Objects, Metrics, or Decisions. 2. Preview-first: Before creating any resources, describe automation in 1-2 sentences and show a conditions → actions decision table. Ask for confirmation before building. 3. Predefined templates: For spam (flooding/cross-posting) and ranking (Top N/Bottom N), use the Query Builder predefined templates. Never recreate these from scratch. 4. Built-in BO fields: For chat/moderation/ranking, User/Channel/Message/Message Type are auto-created. Never ask users to define them. 5. Start simple: Minimal decision for the core goal; add complexity only when requested. 6. PubNub extension: For delayed checks, scheduling, or orchestration beyond Illuminate, suggest PubNub Functions or pub/sub as the first extension path. Input schemasha256:827d7571c80fd89646fc50553b354e379d8d8c6c87f994b4e50417634fc584f3Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
manage_keysetspubnub-mcp-server:tool:manage_keysetsObserved interface and hashesManages PubNub keysets with operations: get, list, create, update. - 'get': Get a specific keyset information, including its current config (message persistence, App Context, files, presence including presence rules, etc.). User needs to provide the keyset id. - 'list': List all keysets for your account or a specific app. - 'create': Create a new keyset. New keyset is created with Message Persistence, App Context, Files, and Presence enabled by default; the user must provide name, production, and config with nested objects (messagePersistence, appContext, files, presence), and if any required parameter is missing, you must ask the user to provide it. - 'update': Update an existing keyset. User needs to provide the keyset id and the config to update. Only provided fields are changed. presence.rules replaces the stored rules entirely: before changing rules, call 'get' and send the full list including the existing rules to keep. If 'get' returns presence.rules as "UNREADABLE", the existing rules cannot be read back; tell the user that sending rules will overwrite them and ask before proceeding. Input schemasha256:b7001df0ca2a29a5840bbe883df24baa05375cea5e212dd0448a7c7e006d67feOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
send_pubnub_messagepubnub-mcp-server:tool:send_pubnub_messageObserved interface and hashesSend a message or signal to a PubNub channel in real-time. Supports both regular messages and lightweight signals. Plain strings are automatically wrapped in a 'text' field. Requires publish and subscribe keys from your PubNub keyset. Input schemasha256:bed00b0dd13c84da833bf687f86af850161f7163c0b399b8bf70431d0024b391Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
subscribe_and_receive_pubnub_messagespubnub-mcp-server:tool:subscribe_and_receive_pubnub_messagesObserved interface and hashesSubscribe to a PubNub channel and receive messages in real-time. Specify the number of messages (default 1) and/or a timeout (default 10s, max 30s) to wait for. Requires publish and subscribe keys from your PubNub keyset. Input schemasha256:773d42ff4e874d987b31269700b892c9432ef6e4e1fc6fdd37860575630e3025Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed | |
write_pubnub_apppubnub-mcp-server:tool:write_pubnub_appObserved interface and hashesRetrieve PubNub best practices guide covering: 1) Architecture & project setup (environments, payload sizes), 2) Security (Access Manager tokens, least privilege, PII hygiene), 3) Channel & data modeling (naming conventions, message schemas), 4) Publish/Subscribe patterns, 5) History usage, 6) Client reliability (reconnect, idempotency, ordering), 7) Functions/edge logic, 8) Presence & state, 9) App Context, 10) Mobile specifics (push notifications, caching), 11) Web specifics (tab lifecycle, Service Workers), 12) Observability & ops, 13) Performance & cost optimization. Call this tool when building PubNub applications to ensure robust, scalable, and secure implementations. Input schemasha256:3178d649f32f96ea850da50c27c062f5c20cbef86dec2f5af0587dff56ebdb67Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 2.3.12 | No change observed |
No capabilities match these filters.
STATIC COMPARISONS
Release history
- 2.3.14 2.3.15REVIEW0 added0 removed2 schema0 write0 destructive0 unknown
- 2.3.12 2.3.14PASS0 added0 removed0 schema0 write0 destructive0 unknown