"Payload CMS" matching MCP tools:

• agent_operators_set

  fomox402 — Last-Bidder-Wins on Solana

  Mutate the operator whitelist with an owner-signed payload. WHAT IT DOES: POSTs /v1/agents/:agent_wallet/operators with { payload, signature }. Broker enforces that the signer is the OWNER (agent_wallet itself) — operator-signed mutations of the whitelist are rejected even if the signer is otherwise authorised to write configs. Headless — the broker NEVER signs. WHEN TO USE: granting / revoking write access for a sidecar process, rotating an operator key, or wiping the whitelist before retiring an agent. OPS: add — append `operator` to the list (idempotent on existing entry) remove — drop `operator` from the list (idempotent on missing entry) set — replace the entire list with `operators` (use [] to wipe) PAYLOAD CANONICALISATION: broker re-stringifies `payload` with sorted keys and no whitespace before verifying the signature. Sign that exact form. RETURNS: OperatorsList after the mutation. FAILURE MODES: operators_set_failed (bad_signature) — payload != signed bytes operators_set_failed (signer_not_owner) — only the owner may mutate the list operators_set_failed (payload_expired) — broker 410 operators_set_failed (nonce_replayed) — duplicate nonce RELATED: agent_operators_list (read), agent_equip_set (the permission you're granting).

  Connector

• get_saved_visual_idea_preset

  Heista

  Get one saved visual ideas preset by id, including its full body payload (framework, agent config, etc.). Call the matching list tool first to discover ids. Free, read-only.

  Connector

• agent_operators_set

  fomox402

  Mutate the operator whitelist with an owner-signed payload. WHAT IT DOES: POSTs /v1/agents/:agent_wallet/operators with { payload, signature }. Broker enforces that the signer is the OWNER (agent_wallet itself) — operator-signed mutations of the whitelist are rejected even if the signer is otherwise authorised to write configs. Headless — the broker NEVER signs. WHEN TO USE: granting / revoking write access for a sidecar process, rotating an operator key, or wiping the whitelist before retiring an agent. OPS: add — append `operator` to the list (idempotent on existing entry) remove — drop `operator` from the list (idempotent on missing entry) set — replace the entire list with `operators` (use [] to wipe) PAYLOAD CANONICALISATION: broker re-stringifies `payload` with sorted keys and no whitespace before verifying the signature. Sign that exact form. RETURNS: OperatorsList after the mutation. FAILURE MODES: operators_set_failed (bad_signature) — payload != signed bytes operators_set_failed (signer_not_owner) — only the owner may mutate the list operators_set_failed (payload_expired) — broker 410 operators_set_failed (nonce_replayed) — duplicate nonce RELATED: agent_operators_list (read), agent_equip_set (the permission you're granting).

  Connector

• agent_equip_set

  fomox402 — Last-Bidder-Wins on Solana

  Write a STRAT config with a caller-signed payload (CAS-protected). WHAT IT DOES: POSTs /v1/agents/:agent_wallet/config with { payload, signature }. Broker verifies the signature against the agent's owner key OR any wallet on the operator whitelist (see agent_operators_list), checks `expected_version` against the current AgentConfig.version, and writes the new config atomically. Headless — the broker NEVER signs. WHEN TO USE: after a tower floor is claimed, push the STRAT config the tower v0 worker should run. Write again whenever you want to retune the strategy. Refetch with agent_equip_get on a 409 conflict and retry with the bumped expected_version. PAYLOAD CANONICALISATION: broker re-stringifies `payload` with sorted keys and no whitespace before verifying the signature. Sign that exact form. RETURNS: AgentConfig — same shape as agent_equip_get, with `version` incremented to the new high-water mark. FAILURE MODES: equip_set_failed (bad_signature) — payload != signed bytes equip_set_failed (signer_not_authorized) — signer is neither owner nor operator equip_set_failed (version_mismatch) — refetch + retry (broker 409) equip_set_failed (payload_expired) — broker 410 equip_set_failed (nonce_replayed) — broker rejected duplicate nonce RELATED: agent_equip_get (read current version), agent_operators_set (grant another wallet permission to write configs on this agent's behalf).

  Connector

• get_crisis_resources

  library

  Return the canonical 988 / 911 / Crisis Text Line payload. Surface this immediately whenever the user signals self-harm or imminent danger.

  Connector

• agent_equip_set

  fomox402

  Write a STRAT config with a caller-signed payload (CAS-protected). WHAT IT DOES: POSTs /v1/agents/:agent_wallet/config with { payload, signature }. Broker verifies the signature against the agent's owner key OR any wallet on the operator whitelist (see agent_operators_list), checks `expected_version` against the current AgentConfig.version, and writes the new config atomically. Headless — the broker NEVER signs. WHEN TO USE: after a tower floor is claimed, push the STRAT config the tower v0 worker should run. Write again whenever you want to retune the strategy. Refetch with agent_equip_get on a 409 conflict and retry with the bumped expected_version. PAYLOAD CANONICALISATION: broker re-stringifies `payload` with sorted keys and no whitespace before verifying the signature. Sign that exact form. RETURNS: AgentConfig — same shape as agent_equip_get, with `version` incremented to the new high-water mark. FAILURE MODES: equip_set_failed (bad_signature) — payload != signed bytes equip_set_failed (signer_not_authorized) — signer is neither owner nor operator equip_set_failed (version_mismatch) — refetch + retry (broker 409) equip_set_failed (payload_expired) — broker 410 equip_set_failed (nonce_replayed) — broker rejected duplicate nonce RELATED: agent_equip_get (read current version), agent_operators_set (grant another wallet permission to write configs on this agent's behalf).

  Connector

• create_post

  FavCRM

  Create a new CMS post (blog_post, page, or any custom post type). The post type must already exist — use list_post_types to discover, create_post_type to add a new one. excerpt = plain-text summary only (auto-derived from blocks if omitted). Structured custom fields go in meta, keyed by the field schema defined with create_post_type_field.

  Connector

• get_crisis_resources

  library

  Return the canonical 988 / 911 / Crisis Text Line payload. Surface this immediately whenever the user signals self-harm or imminent danger.

  Connector

• get_session_details

  MCPSpend

  Drill into a single session by ID. Returns the session header plus every tool call within it (capped at 500 to bound payload size).

  Connector

• get_crisis_resources

  library

  Return the canonical 988 / 911 / Crisis Text Line payload. Surface this immediately whenever the user signals self-harm or imminent danger.

  Connector

• get_crisis_resources

  library

  Return the canonical 988 / 911 / Crisis Text Line payload. Surface this immediately whenever the user signals self-harm or imminent danger.

  Connector

• get_crisis_resources

  mental-health-care

  Canonical crisis-resource payload (911, 988 Suicide & Crisis Lifeline, Crisis Text Line). Hardcoded — overrides any other tool when high-severity language is detected.

  Connector

• jwt-decoder

  Microapp

  Decode a JWT into its header and payload. Does NOT verify the signature — use this for inspection only, never to trust the token's claims.

  Connector

• scythian_get_descendants

  hub

  Fetch the full descendants payload — etymology, glosses and the reflex tree (Sarmatian→Alanic→Ossetian, Saka→Khotanese) — for a lemma identified by a search result's descendant handle (entry_id + word_class). Use this only when a search ran without inline payloads or left a match un-expanded — a default search already returns each match's payload inline. Returns Markdown plus the payload as structuredContent with the shape {"result": <payload>} per the declared outputSchema — switch on result.category ('descendants' | 'not_found') before reading the body. Content from en.wiktionary.org (CC BY-SA 4.0).

  Connector

• intel_stack

  TunnelMind Data API

  Fetches up to 32KB of the domain's HTML and response headers from the edge, then fingerprints the content for known CMS platforms, JavaScript frameworks, CDN providers, and analytics tools. Detection is based on meta generator tags, script src patterns, response headers, and cookie names. Use this tool when: - You need to know what CMS (WordPress, Drupal, Shopify) a site runs. - You are assessing a domain's infrastructure before a security review. - You want to identify analytics or marketing tools a site embeds. Do NOT use this tool when: - You want HTTP headers and security posture — use `intel_http` instead. - You want tracker database classification — use `get_domain` instead. - You need robots.txt AI policy — use `intel_robots` instead. Inputs: - `domain` (query, required): Domain to fingerprint. Returns: - `cms`: detected content management system, or null. - `frameworks`: JavaScript/backend frameworks detected. - `cdn`: CDN provider detected, or null. - `analytics`: analytics and tracking tools detected. - `meta_generators`: raw meta generator tag values. Cost: - Free. No API key required. Latency: - Typical: 2-4s (HTML fetch), p99: 7s.

  Connector

• validate_request

  Trillboards DOOH Advertising

  Validate a proposed request payload against the registered Zod schema for an operation, returning the exact canonical error envelope the HTTP surface would emit. WHEN TO USE: - Before calling a write endpoint, to catch payload bugs locally. - Debugging 400 validation_error responses. RETURNS: - valid: true when the payload would pass Zod validation. - When invalid, the canonical { error: { type, code, message, param, doc_url, details[] } } envelope is included under `error`. EXAMPLE: validate_request({ path: "/v1/data/query", method: "POST", payload: { dataset: "inference_outcomes", limit: 9999 } })

  Connector

• read_canvas

  Agent Canvas Arena

  Global situational awareness. Returns the full 32x32 grid and reservoir stats. Warning: This is a heavy payload (1024 pixels). Use for broad scanning of opportunities.

  Connector

• get_descendants_scythian

  scythian

  Fetch the full descendants payload — etymology, glosses and the reflex tree (Sarmatian→Alanic→Ossetian, Saka→Khotanese) — for a lemma identified by a search result's descendant handle (entry_id + word_class). Use this only when a search ran without inline payloads or left a match un-expanded — a default search already returns each match's payload inline. Returns Markdown plus the payload as structuredContent with the shape {"result": <payload>} per the declared outputSchema — switch on result.category ('descendants' | 'not_found') before reading the body. Content from en.wiktionary.org (CC BY-SA 4.0).

  Connector

• scope_award_matter

  Scope (Legal)

  Award a dispatched matter to a chosen vendor. Locks the booking, notifies the vendor (push + email), and schedules a Stripe Connect invoice that fires when the matter completes (buyer review auto-accepts at 5 days). Returns a confirmation payload with actions taken and accurate next steps. Demo mode echoes the response shape without firing notifications or capturing payment. DocuSign engagement-letter generation, calendar invites, and CMS push-back are roadmap and intentionally not included in the action list.

  Connector

• check_realization

  governance-platform

  Run structural realization analysis on a payload. Embeds the payload via the Blueprint's declared embedding schema, projects it onto the Blueprint's reference subspace, and returns a realization score, residual, projection angle, and full report. The Blueprint must include a `realization` configuration block (see RealizationConfig in Platform_Agent.realization.schema). If no realization config is present, the report status is "skipped" and the payload is treated as unconstrained by the realization layer. For Blueprints using basis mode "auto", the first N payloads bootstrap the reference subspace; until the bootstrap pool is full, the report status is "skipped". After bootstrap, every subsequent payload is projected against the locked subspace and receives a real score. Args: api_key: GeodesicAI API key (starts with gai_) structured_data: payload to analyze blueprint: Blueprint name (defaults to "default") Returns: dict with keys: status: "pass" | "review" | "skipped" realization_score: float in [0, 1], higher = better fit residual: ||v - P_U(v)|| angle_degrees: angle between v and P_U(v) in_subspace: bool — residual < tolerance basis_mode: "vectors" | "auto" | "uninitialized" basis_dimension: k of the reference subspace vector_dimension: D of the embedded payload report: full RealizationReport dict (may include invariance/stability stacks if enabled)

  Connector