PressureDesk

Server Details

Read-only BUY / WAIT / AVOID spend gate for paid APIs, MCP endpoints, and x402 routes.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Unhealthy
Last Tested: 2026-09-06 09:15
Transport: Streamable HTTP
URL

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

9 tool updatesMay 20, 2026

Changedpressuredesk_agent_home1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "PressureDesk JSON response. The exact fields depend on the selected read-only route, but the result is always returned as structuredContent plus a text JSON copy.",
+  "properties": {
+    "decision": {
+      "additionalProperties": true,
+      "description": "BUY / WAIT / AVOID decision packet when the tool evaluates a paid target.",
+      "properties": {},
+      "type": "object"
+    },
+    "kind": {
+      "description": "Machine-readable response kind, for example source-health, agent-home, or tool-buyer-dossier.",
+      "type": "string"
+    },
+    "product": {
+      "description": "Product name when the response is a public product or route packet.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Readiness, payment, or request status when present.",
+      "type": "string"
+    },
+    "trustPacket": {
+      "additionalProperties": true,
+      "description": "Receipt, freshness, source, and safety-boundary information for agent spend decisions.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changedpressuredesk_evaluate_tool4 fields changed

addedInput schema / properties / priceUsd / description

Added value: +"Quoted target price in USD for this one prospective call."

addedInput schema / properties / target / description

Added value: +"Paid API, x402 endpoint, MCP server, or tool URL to evaluate before spend."

addedInput schema / properties / task / description

Added value: +"Buyer task or agent intent that explains why the target might be worth paying for."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "PressureDesk JSON response. The exact fields depend on the selected read-only route, but the result is always returned as structuredContent plus a text JSON copy.",
+  "properties": {
+    "decision": {
+      "additionalProperties": true,
+      "description": "BUY / WAIT / AVOID decision packet when the tool evaluates a paid target.",
+      "properties": {},
+      "type": "object"
+    },
+    "kind": {
+      "description": "Machine-readable response kind, for example source-health, agent-home, or tool-buyer-dossier.",
+      "type": "string"
+    },
+    "product": {
+      "description": "Product name when the response is a public product or route packet.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Readiness, payment, or request status when present.",
+      "type": "string"
+    },
+    "trustPacket": {
+      "additionalProperties": true,
+      "description": "Receipt, freshness, source, and safety-boundary information for agent spend decisions.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changedpressuredesk_founding_access1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "PressureDesk JSON response. The exact fields depend on the selected read-only route, but the result is always returned as structuredContent plus a text JSON copy.",
+  "properties": {
+    "decision": {
+      "additionalProperties": true,
+      "description": "BUY / WAIT / AVOID decision packet when the tool evaluates a paid target.",
+      "properties": {},
+      "type": "object"
+    },
+    "kind": {
+      "description": "Machine-readable response kind, for example source-health, agent-home, or tool-buyer-dossier.",
+      "type": "string"
+    },
+    "product": {
+      "description": "Product name when the response is a public product or route packet.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Readiness, payment, or request status when present.",
+      "type": "string"
+    },
+    "trustPacket": {
+      "additionalProperties": true,
+      "description": "Receipt, freshness, source, and safety-boundary information for agent spend decisions.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changedpressuredesk_freshness1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "PressureDesk JSON response. The exact fields depend on the selected read-only route, but the result is always returned as structuredContent plus a text JSON copy.",
+  "properties": {
+    "decision": {
+      "additionalProperties": true,
+      "description": "BUY / WAIT / AVOID decision packet when the tool evaluates a paid target.",
+      "properties": {},
+      "type": "object"
+    },
+    "kind": {
+      "description": "Machine-readable response kind, for example source-health, agent-home, or tool-buyer-dossier.",
+      "type": "string"
+    },
+    "product": {
+      "description": "Product name when the response is a public product or route packet.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Readiness, payment, or request status when present.",
+      "type": "string"
+    },
+    "trustPacket": {
+      "additionalProperties": true,
+      "description": "Receipt, freshness, source, and safety-boundary information for agent spend decisions.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changedpressuredesk_get_dossier2 fields changed

addedInput schema / properties / entityId / description

Added value: +"PressureDesk entity id to retrieve, such as a scored market or tool-buyer target id."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "PressureDesk JSON response. The exact fields depend on the selected read-only route, but the result is always returned as structuredContent plus a text JSON copy.",
+  "properties": {
+    "decision": {
+      "additionalProperties": true,
+      "description": "BUY / WAIT / AVOID decision packet when the tool evaluates a paid target.",
+      "properties": {},
+      "type": "object"
+    },
+    "kind": {
+      "description": "Machine-readable response kind, for example source-health, agent-home, or tool-buyer-dossier.",
+      "type": "string"
+    },
+    "product": {
+      "description": "Product name when the response is a public product or route packet.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Readiness, payment, or request status when present.",
+      "type": "string"
+    },
+    "trustPacket": {
+      "additionalProperties": true,
+      "description": "Receipt, freshness, source, and safety-boundary information for agent spend decisions.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changedpressuredesk_live_payment_status1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "PressureDesk JSON response. The exact fields depend on the selected read-only route, but the result is always returned as structuredContent plus a text JSON copy.",
+  "properties": {
+    "decision": {
+      "additionalProperties": true,
+      "description": "BUY / WAIT / AVOID decision packet when the tool evaluates a paid target.",
+      "properties": {},
+      "type": "object"
+    },
+    "kind": {
+      "description": "Machine-readable response kind, for example source-health, agent-home, or tool-buyer-dossier.",
+      "type": "string"
+    },
+    "product": {
+      "description": "Product name when the response is a public product or route packet.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Readiness, payment, or request status when present.",
+      "type": "string"
+    },
+    "trustPacket": {
+      "additionalProperties": true,
+      "description": "Receipt, freshness, source, and safety-boundary information for agent spend decisions.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changedpressuredesk_meta1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "PressureDesk JSON response. The exact fields depend on the selected read-only route, but the result is always returned as structuredContent plus a text JSON copy.",
+  "properties": {
+    "decision": {
+      "additionalProperties": true,
+      "description": "BUY / WAIT / AVOID decision packet when the tool evaluates a paid target.",
+      "properties": {},
+      "type": "object"
+    },
+    "kind": {
+      "description": "Machine-readable response kind, for example source-health, agent-home, or tool-buyer-dossier.",
+      "type": "string"
+    },
+    "product": {
+      "description": "Product name when the response is a public product or route packet.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Readiness, payment, or request status when present.",
+      "type": "string"
+    },
+    "trustPacket": {
+      "additionalProperties": true,
+      "description": "Receipt, freshness, source, and safety-boundary information for agent spend decisions.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changedpressuredesk_preview_latest1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "PressureDesk JSON response. The exact fields depend on the selected read-only route, but the result is always returned as structuredContent plus a text JSON copy.",
+  "properties": {
+    "decision": {
+      "additionalProperties": true,
+      "description": "BUY / WAIT / AVOID decision packet when the tool evaluates a paid target.",
+      "properties": {},
+      "type": "object"
+    },
+    "kind": {
+      "description": "Machine-readable response kind, for example source-health, agent-home, or tool-buyer-dossier.",
+      "type": "string"
+    },
+    "product": {
+      "description": "Product name when the response is a public product or route packet.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Readiness, payment, or request status when present.",
+      "type": "string"
+    },
+    "trustPacket": {
+      "additionalProperties": true,
+      "description": "Receipt, freshness, source, and safety-boundary information for agent spend decisions.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changedpressuredesk_source_health1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "PressureDesk JSON response. The exact fields depend on the selected read-only route, but the result is always returned as structuredContent plus a text JSON copy.",
+  "properties": {
+    "decision": {
+      "additionalProperties": true,
+      "description": "BUY / WAIT / AVOID decision packet when the tool evaluates a paid target.",
+      "properties": {},
+      "type": "object"
+    },
+    "kind": {
+      "description": "Machine-readable response kind, for example source-health, agent-home, or tool-buyer-dossier.",
+      "type": "string"
+    },
+    "product": {
+      "description": "Product name when the response is a public product or route packet.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Readiness, payment, or request status when present.",
+      "type": "string"
+    },
+    "trustPacket": {
+      "additionalProperties": true,
+      "description": "Receipt, freshness, source, and safety-boundary information for agent spend decisions.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

9 tool updatesMay 20, 2026
- First observedpressuredesk_agent_home
- First observedpressuredesk_evaluate_tool
- First observedpressuredesk_founding_access
- First observedpressuredesk_freshness
- First observedpressuredesk_get_dossier
- First observedpressuredesk_live_payment_status
- First observedpressuredesk_meta
- First observedpressuredesk_preview_latest
- First observedpressuredesk_source_health

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

GhostKey — Route Paid APIs with x402 A
com.scriptmasterlabs
Find paid APIs, check access policy and price, and route x402 requests. No autonomous spending.
Autonomous Agents Payments & Billing
41
Agent Reserve Protocol Authorization Firewall A
site.chatgpt.super-myna-7255.agent-reserve-protocol
Advisory policy preflight for AI-agent spend requests; never executes payments or accesses wallets.
Security Autonomous Agents
11
bitfence Risk Oracle A
io.github.bitfenceai
Pre-transaction token risk checks for autonomous agents on six chains. Read-only; paid via x402.
Blockchain Cryptocurrency Autonomous Agents
221
x402 Gateway — Inspect Paid API Terms B
com.scriptmasterlabs
Discover x402 paid APIs and inspect fresh payment requirements before authorizing spend.
Finance Blockchain Government Data
31

Related MCP Servers

@cubiczan/chp-mcp
Finance Autonomous Agents
icohangar-ops
A
license
A
quality
A
maintenance
Enables MCP clients to evaluate spend gates and manage human-in-the-loop approvals for CHP Profile B.
Updated 15 days ago (2026-08-22 16:54 UTC)
2
4
119
MIT
dingdawg-agent-wallet
Blockchain Cryptocurrency Autonomous Agents
dingdawg
F
license
Not graded
quality
D
maintenance
Provides MCP tools to enforce spend policies (allow, deny, step-up, allowlist) on agent wallets with an immutable audit trail.
Updated a month ago (2026-08-06 18:42 UTC)
-
A2A Identity Toll MCP
Security Autonomous Agents
clauxel
A
license
Not graded
quality
D
maintenance
Paid remote MCP gate for caller identity, agent scope, task intent, data class, policy verdicts, and audit receipts.
Updated 4 months ago (2026-05-20 08:25 UTC)
MIT
Budget Governor
Autonomous Agents CI/CD & DevOps Developer Tools
mightbesaad
A
license
Not graded
quality
C
maintenance
Budget & cost control for AI agents: hard per-agent spend caps, rate limits, idempotency, and human-in-the-loop approval — enforced before each LLM call, not after the invoice. One hosted MCP endpoint (no proxy or self-hosting), settled via x402 (USDC on Base).
Updated 3 months ago (2026-06-11 06:04 UTC)
MIT

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes (e.g., evaluate_tool, get_dossier, live_payment_status). However, freshness and source_health both touch on snapshot freshness, and meta/preview_latest both involve snapshot info, creating slight overlap.

Naming Consistency4/5

All tools use the consistent pressuredesk_ prefix and snake_case. However, naming patterns vary: some are verb_noun (evaluate_tool, get_dossier), others are noun_noun (agent_home) or adjective (freshness, meta), so not fully consistent.

Tool Count5/5

With 9 tools, the surface is well-scoped for a specialized evaluation and dossier service. It covers key operations without becoming unwieldy.

Completeness4/5

The set covers core workflows: product metadata, tool evaluation, dossiers, payment status, and health checks. Minor gaps include no entity listing or search, and no action tool for purchasing, but the read-only focus is intentional.

Resources

Need Help?

Server Details

Tool Schema Changelog

Frequently Asked Questions

Discussions

Related MCP Connectors

Related MCP Servers

@cubiczan/chp-mcp

dingdawg-agent-wallet

A2A Identity Toll MCP

Budget Governor

Glama MCP Gateway

TDQS

Resources