pulsenetwork

onchainpulse

OnchainPulse: Intelligence API for the onchain financial transition. Decodes legislation, tracks RWA tokenization, models sector scenarios, guides onchain integration. All endpoints require x402 payment (USDC on Ba

Coverage: Global

Endpoints: • legislation ($0.15): Translate crypto bills to plain English with sector impact • rwa ($0.15): Survey the real-world-asset market across asset classes • scenario ($0.20): Model sector impact scenarios with if/then analysis • transition ($0.10): Guide practical onchain onboarding by organization type • monitor ($0.10): Monitor institutional onchain activity, weekly briefs • compliance ($0.15): Map regulatory compliance duties by jurisdiction • tokenize ($0.15): Explain how to tokenize any asset type, step by step • glossary ($0.05): Decode any onchain finance or regulatory term plainly • snapshot ($0.10): Summarize the onchain transition in a weekly macro brief • memecoin ($0.015): Scan a Solana memecoin pre-trade, deterministic verdict • evmtoken ($0.015): Scan an EVM token pre-trade, multi-chain, deterministic • rwa-risk ($0.25): Assess issuer and redemption risk for a named RWA product • gold-check ($0.15): Compare tokenized gold products: PAXG vs XAUT • etf-flows ($0.15): Track US spot crypto ETF flows with per-issuer detail • clarity-watch ($0.10): Track CLARITY Act status, CFTC/SEC split, passage odds • vault-apy ($0.02): Live USDC yield panel on Base — onchain lending rates + realized Morpho vault APY, deterministic • asatoken ($0.015): Scan an Algorand ASA pre-trade, deterministic verdict • exit-depth ($0.02): Estimate sell-side depth of a v3 pool at 1-25% price impact • holder-map ($0.02): Map holder concentration with LP/burn/contract labeling • narrative-check ($0.15): Check a project's public claims against observed chain data • receipts ($0.35): One-call composite token due-diligence report • honeypot ($0.005): Check honeypot sellability flags, half a cent • liquidity ($0.005): Check token DEX liquidity and momentum, half a cent • rh-launches ($0.01): Live Uniswap-launchpad launch feed on Robinhood Chain, one cent • iso-receipt ($0.05): ISO 20022 camt.054-style receipt for an on-chain settlement (signed, verifiable) • rwa-bnb ($0.15): Rank every RWA protocol by its BNB Chain TVL slice • yield-check ($0.05): Reality-check a dividend/reflection token's promised yield against live volume • token-safety ($0.015): Token safety check for any token on 10 chains — is this token safe to buy? Deterministic CLEAR/CAUTION/AVOID verdict, chain auto-detected

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Bill name or topic (e.g. 'GENIUS Act', 'stablecoin regulation', 'MiCA')
`tx`	No	Transaction hash of the settlement
`url`	No	Project's public website URL or domain
`lang`	No	Response language (ISO 639-1 code)
`mint`	No	SPL token mint address (base58)
`pool`	No	v3-compatible pool address to read directly (overrides token resolution)
`sort`	No	bnb_tvl (default) \| change_7d \| share
`term`	No	Term to explain (e.g. 'atomic settlement', 'MiCA', 'CASP', 'yield bearing stablecoin', 'RWA')
`type`	No	Type of transition
`asset`	No	Which ETF complex to analyze
`chain`	No	EVM chain (default base; robinhood = Robinhood Chain)
`limit`	No	max launches to return, 1-50 (default 25); newest first
`scope`	No	scope parameter
`token`	No	ERC-20 token address — primary pool auto-resolved via DexScreener
`topic`	No	topic parameter
`vault`	No	Optional address of ANY ERC-4626 vault on Base to read alongside the standard panel.
`action`	No	Type of analysis
`period`	No	period parameter
`sector`	No	Sector to focus on, or 'all' for comprehensive coverage
`window`	No	Trailing window in days for realized ERC-4626 vault APY (share-price delta, annualized).
`address`	No	ERC-20 token contract address (0x + 40 hex)
`context`	No	Additional context about the user's situation
`product`	No	Product to analyze
`tax_pct`	No	Stated total transaction tax percent (default 1)
`trigger`	No	The development to model (e.g. 'GENIUS Act passes', 'DTCC full tokenization launch', 'MiCA enforcement begins')
`use_case`	No	What the entity wants to do (e.g. 'issue a stablecoin', 'operate a crypto exchange', 'accept USDC payments')
`framework`	No	Specific framework to focus on (e.g. 'MiCA', 'GENIUS Act')
`timeframe`	No	timeframe parameter
`asset_type`	No	Asset type to analyze (e.g. 'real estate', 'equity', 'bond', 'private credit', 'art')
`asset_class`	No	Specific asset class focus (e.g. 'US Treasuries', 'real estate', 'private credit')
`holding_pct`	No	Holding as percent of supply for per-holder math
`min_tvl_usd`	No	Exclude protocols below this BNB-chain TVL in USD (default 10000)
`perspective`	No	Account-holder address: its inflows become credits, outflows debits
`jurisdiction`	No	Jurisdiction to focus on
`payout_share_pct`	No	Percent of tax paid to holders (default 100)
`promised_daily_usd`	No	Promised whole-pool daily payout in USD to compare

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 6, 2026

changedInput schema / properties / chain / description

Previous value: -"EVM chain (default base)"New value: +"EVM chain (default base; robinhood = Robinhood Chain)"

addedInput schema / properties / holding_pct

Added value: +{
+  "description": "Holding as percent of supply for per-holder math",
+  "type": "string"
+}

addedInput schema / properties / min_tvl_usd

Added value: +{
+  "description": "Exclude protocols below this BNB-chain TVL in USD (default 10000)",
+  "type": "string"
+}

addedInput schema / properties / payout_share_pct

Added value: +{
+  "description": "Percent of tax paid to holders (default 100)",
+  "type": "string"
+}

addedInput schema / properties / promised_daily_usd

Added value: +{
+  "description": "Promised whole-pool daily payout in USD to compare",
+  "type": "string"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "bnb_tvl (default) | change_7d | share",
+  "type": "string"
+}

addedInput schema / properties / tax_pct

Added value: +{
+  "description": "Stated total transaction tax percent (default 1)",
+  "type": "string"
+}

Changed3 schema fields changedAug 4, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "max launches to return, 1-50 (default 25); newest first",
+  "type": "string"
+}

addedInput schema / properties / perspective

Added value: +{
+  "description": "Account-holder address: its inflows become credits, outflows debits",
+  "type": "string"
+}

addedInput schema / properties / tx

Added value: +{
+  "description": "Transaction hash of the settlement",
+  "type": "string"
+}

Changed3 schema fields changedJul 28, 2026

addedInput schema / properties / pool

Added value: +{
+  "description": "v3-compatible pool address to read directly (overrides token resolution)",
+  "type": "string"
+}

addedInput schema / properties / token

Added value: +{
+  "description": "ERC-20 token address — primary pool auto-resolved via DexScreener",
+  "type": "string"
+}

addedInput schema / properties / url

Added value: +{
+  "description": "Project's public website URL or domain",
+  "type": "string"
+}

Changed2 schema fields changedJul 21, 2026

addedInput schema / properties / vault

Added value: +{
+  "description": "Optional address of ANY ERC-4626 vault on Base to read alongside the standard panel.",
+  "type": "string"
+}

addedInput schema / properties / window

Added value: +{
+  "description": "Trailing window in days for realized ERC-4626 vault APY (share-price delta, annualized).",
+  "type": "string"
+}

Changed2 schema fields changedJul 14, 2026

changedInput schema / properties / product / description

Previous value: -"Focus on one product"New value: +"Product to analyze"

removedInput schema / properties / risk

Removed value: -{
-  "description": "Risk tolerance for recommendations framing",
-  "type": "string"
-}

Changed4 schema fields changedJul 11, 2026
- changedInput schema / properties / period / description
```
Previous value: -"period"New value: +"period parameter"
```
- changedInput schema / properties / scope / description
```
Previous value: -"scope"New value: +"scope parameter"
```
- changedInput schema / properties / timeframe / description
```
Previous value: -"timeframe"New value: +"timeframe parameter"
```
- changedInput schema / properties / topic / description
```
Previous value: -"topic"New value: +"topic parameter"
```

Changed1 schema field changedJul 6, 2026

addedInput schema / properties / asset

Added value: +{
+  "description": "Which ETF complex to analyze",
+  "type": "string"
+}

First observedJul 6, 2026

TDQS

C2.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It usefully discloses that all endpoints require x402 payment in USDC on Base and gives per-endpoint pricing, which is real added context. However, it says nothing about read-only vs mutating behavior, return format, or limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

For a router exposing 30 endpoints the length is somewhat justified, but the opening sentence is marketing copy rather than front-loaded operational detail, and per-endpoint price annotations pad the text. Structure is acceptable but not economical.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex tool: 36 parameters, 30 endpoints, no annotations, no output schema. The description lists endpoints but never explains how to invoke them — which parameters each endpoint expects — nor what it returns. For this complexity the description leaves a significant gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 36 parameters, making 3 the baseline. The description's endpoint list loosely maps some parameters to features (legislation→q, rwa→asset_class, scenario→trigger) but does not explicitly tie parameters to endpoints or add semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a broad mission statement ('Intelligence API for the onchain financial transition') and then lists 30 named endpoints. It conveys the domain and capability surface but never states a focused verb+resource for the tool as a whole, and gives no differentiation from the many sibling *pulse tools. This is a vague, menu-style purpose rather than a crisp one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description enumerates endpoints with prices but offers no when-to-use guidance: nothing says which endpoint to pick for a given task, nor when to prefer this tool over a sibling, nor which parameters belong to which endpoint. It is a catalog, not usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All pulsenetwork tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

onchainpulse

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources