ClinicalIntelPulse: Pharmaceutical pipeline and clinical trial intelligence API. Synthesizes 400,000+ registered trials from ClinicalTrials.gov with FDA OpenFDA, PubMed, and real-time news. All endpoints require x402 pay Coverage: Global Endpoints: • pipeline-scan ($0.15): Phase 2/3 pipeline scan...
AI agents call clinicalintelpulse to retrieve information from Pulsenetwork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lang | string | — | Response language |
depth | string | — | depth |
focus | string | — | focus |
phase | string | — | phase |
stage | string | — | stage |
action | string | Yes | Which endpoint to call. Options: pipeline-scan | approval-outlook | sponsor-intel | disease-landscape | trial-brief | mechanism-map | global-trials | failure-an |
agency | string | — | agency |
nct_id | string | — | NCT identifier — e.g. NCT04368728 |
region | string | — | region |
status | string | — | status |
country | string | — | Optional country filter — e.g. 'United States' | 'Germany' | 'Australia' |
horizon | string | — | horizon |
Parameters from the server's own tool schema.
ClinicalIntelPulse is a read-only intelligence API that queries and synthesizes existing public and semi-public clinical data sources. No endpoints create, modify, delete data, or execute arbitrary code. The financial component (x402 USDC payment per query) is a billing mechanism, not a financial transaction that moves user funds for user-specified purposes—it is a fixed consumption cost.
From the tool's definition Tool description states it 'Synthesizes 400,000+ registered trials from ClinicalTrials.gov with FDA OpenFDA, PubMed, and real-time news.' All named endpoints are queries: 'pipeline-scan', 'approval-outlook', 'sponsor-intel', 'disease-landscape',…
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
ClinicalIntelPulse: Pharmaceutical pipeline and clinical trial intelligence API. Synthesizes 400,000+ registered trials from ClinicalTrials.gov with FDA OpenFDA, PubMed, and real-time news. All endpoints require x402 pay Coverage: Global Endpoints: • pipeline-scan ($0.15): Phase 2/3 pipeline scan • approval-outlook ($0.25): FDA/EMA approval probability • sponsor-intel ($0.20): Pharma/biotech pipeline intelligence • disease-landscape ($0.35): Full disease landscape report • trial-brief ($0.10): Clinical trial deep dive by NCT ID • mechanism-map ($0.20): Drug target and MOA landscape • global-trials ($0.15): Global clinical trial landscape • failure-analysis ($0.20): Clinical trial failure analysis • patient-finder ($0.10): Recruiting trial finder (plain language) • deal-signal ($0.35): Biotech M&A and licensing deal signals. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.
clinicalintelpulse accepts 12 parameters: lang, depth, focus, phase, stage, action, agency, nct_id, region, status, country, horizon. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for clinicalintelpulse: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Pulsenetwork. Nothing to install.
clinicalintelpulse is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the clinicalintelpulse rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for clinicalintelpulse. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
clinicalintelpulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
clinicalintelpulse is one line of Pulsenetwork's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →