pulsenetwork

remittancepulse

RemittancePulse: Global remittance intelligence API covering the $700B+ annual global remittance market. 8 endpoints: corridor analysis (200+ corridors), provider comparison with true total cost (fee + FX markup), liv

Coverage: Global

Endpoints: • corridor ($0.08): Corridor intelligence • compare ($0.10): Provider comparison • rate ($0.05): FX rate and markup analysis • receive ($0.08): Receive-country guide • mobile ($0.08): Mobile money ecosystem • compliance ($0.10): Compliance and KYC intelligence • news ($0.08): Remittance industry news • diaspora ($0.10): Diaspora community intelligence • stablecoin-rails ($0.12): Stablecoin remittance rail comparison • rights ($0.05): Remittance-transfer rights check (Reg E Subpart B) — deterministic, no LLM • rights-letter ($2.00): Citation-locked remittance document — error notice / §1005.33(h) rebuttal / cancellation demand ($2) • rights-check ($0.25): Agent-tier preview of the $2 rights-letter — applicability verdict, deadlines, upsell

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	Receiving country — e.g. Philippines, India, Mexico, Nigeria, Bangladesh
`from`	No	Sending country — e.g. USA, UAE, UK, Canada, Germany
`lang`	No	lang
`issue`	No	issue
`topic`	No	regulatory \| providers \| fees \| technology \| all
`action`	Yes	Which endpoint to call. Options: corridor \| compare \| rate \| receive \| mobile \| compliance \| news \| diaspora \| stablecoin-rails \| rights \| rights-letter \| rights-check
`amount`	No	Amount to send in source currency
`method`	No	bank \| cash \| mobile \| wallet — or omit for all methods
`region`	No	East Africa \| West Africa \| South Asia \| Southeast Asia \| Latin America \| Middle East
`country`	No	country
`purpose`	No	purpose
`platform`	No	Specific platform — e.g. M-Pesa, GCash, bKash
`provider`	No	provider
`community`	No	e.g. Filipino, Indian, Mexican, Nigerian, Pakistani, Bangladeshi, Vietnamese
`fees_paid`	No	fees_paid
`principal`	No	principal
`send_date`	No	send_date
`to_country`	No	Receiving country — e.g. Mexico, Philippines, India, Nigeria, Kenya
`amount_paid`	No	amount_paid
`funded_with`	No	funded_with
`notice_date`	No	notice_date
`sender_name`	No	sender_name
`to_currency`	No	e.g. PHP, INR, MXN, NGN, PKR
`from_country`	No	Sending country — e.g. USA, UAE, UK, Germany
`sender_in_us`	No	sender_in_us
`sender_state`	No	sender_state
`sending_from`	No	Country sending from — tailors corridor-specific advice
`from_currency`	No	e.g. USD, GBP, EUR, AED, CAD
`remedy_choice`	No	remedy_choice
`date_available`	No	date_available
`recipient_name`	No	recipient_name
`business_sender`	No	business_sender
`funds_picked_up`	No	funds_picked_up
`actually_received`	No	actually_received
`figures_estimated`	No	figures_estimated
`payment_auth_time`	No	payment_auth_time
`recipient_country`	No	recipient_country
`scheduled_advance`	No	scheduled_advance
`transfer_reference`	No	transfer_reference
`cancel_request_time`	No	cancel_request_time
`disclosed_total_to_recipient`	No	disclosed_total_to_recipient
`provider_warned_before_payment`	No	provider_warned_before_payment

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 25, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: corridor | compare | rate | receive | mobile | compliance | news | diaspora | stablecoin-rails | rights | rights-letter"New value: +"Which endpoint to call. Options: corridor | compare | rate | receive | mobile | compliance | news | diaspora | stablecoin-rails | rights | rights-letter | rights-check"

changedInput schema / properties / action / enum

Previous value: -[
-  "corridor",
-  "compare",
-  "rate",
-  "receive",
-  "mobile",
-  "compliance",
-  "news",
-  "diaspora",
-  "stablecoin-rails",
-  "rights",
-  "rights-letter"
-]New value: +[
+  "corridor",
+  "compare",
+  "rate",
+  "receive",
+  "mobile",
+  "compliance",
+  "news",
+  "diaspora",
+  "stablecoin-rails",
+  "rights",
+  "rights-letter",
+  "rights-check"
+]

Changed27 schema fields changedJul 8, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: corridor | compare | rate | receive | mobile | compliance | news | diaspora | stablecoin-rails | remit_rights | remit_rights_letter"New value: +"Which endpoint to call. Options: corridor | compare | rate | receive | mobile | compliance | news | diaspora | stablecoin-rails | rights | rights-letter"

changedInput schema / properties / action / enum

Previous value: -[
-  "corridor",
-  "compare",
-  "rate",
-  "receive",
-  "mobile",
-  "compliance",
-  "news",
-  "diaspora",
-  "stablecoin-rails",
-  "remit_rights",
-  "remit_rights_letter"
-]New value: +[
+  "corridor",
+  "compare",
+  "rate",
+  "receive",
+  "mobile",
+  "compliance",
+  "news",
+  "diaspora",
+  "stablecoin-rails",
+  "rights",
+  "rights-letter"
+]

addedInput schema / properties / actually_received

Added value: +{
+  "description": "actually_received",
+  "type": "string"
+}

addedInput schema / properties / amount_paid

Added value: +{
+  "description": "amount_paid",
+  "type": "string"
+}

addedInput schema / properties / business_sender

Added value: +{
+  "description": "business_sender",
+  "type": "string"
+}

addedInput schema / properties / cancel_request_time

Added value: +{
+  "description": "cancel_request_time",
+  "type": "string"
+}

changedInput schema / properties / date_available / description

Previous value: -"Disclosed Date Available from the receipt (YYYY-MM-DD) — starts the 180-day clock"New value: +"date_available"

addedInput schema / properties / disclosed_total_to_recipient

Added value: +{
+  "description": "disclosed_total_to_recipient",
+  "type": "string"
+}

changedInput schema / properties / fees_paid / description

Previous value: -"Fees paid USD"New value: +"fees_paid"

addedInput schema / properties / figures_estimated

Added value: +{
+  "description": "figures_estimated",
+  "type": "string"
+}

addedInput schema / properties / funded_with

Added value: +{
+  "description": "funded_with",
+  "type": "string"
+}

addedInput schema / properties / funds_picked_up

Added value: +{
+  "description": "funds_picked_up",
+  "type": "string"
+}

changedInput schema / properties / issue / description

Previous value: -"never_arrived | arrived_late | arrived_short | wrong_person_paid | sender_typo_number | want_to_cancel | scam_recipient | want_documentation"New value: +"issue"

addedInput schema / properties / notice_date

Added value: +{
+  "description": "notice_date",
+  "type": "string"
+}

addedInput schema / properties / payment_auth_time

Added value: +{
+  "description": "payment_auth_time",
+  "type": "string"
+}

changedInput schema / properties / principal / description

Previous value: -"Transfer amount USD"New value: +"principal"

changedInput schema / properties / provider / description

Previous value: -"Western Union, Wise, Remitly, MoneyGram, Xoom…"New value: +"provider"

addedInput schema / properties / provider_warned_before_payment

Added value: +{
+  "description": "provider_warned_before_payment",
+  "type": "string"
+}

addedInput schema / properties / recipient_country

Added value: +{
+  "description": "recipient_country",
+  "type": "string"
+}

addedInput schema / properties / recipient_name

Added value: +{
+  "description": "recipient_name",
+  "type": "string"
+}

changedInput schema / properties / remedy_choice / description

Previous value: -"refund | resend (default refund)"New value: +"remedy_choice"

addedInput schema / properties / scheduled_advance

Added value: +{
+  "description": "scheduled_advance",
+  "type": "string"
+}

addedInput schema / properties / send_date

Added value: +{
+  "description": "send_date",
+  "type": "string"
+}

addedInput schema / properties / sender_in_us

Added value: +{
+  "description": "sender_in_us",
+  "type": "string"
+}

addedInput schema / properties / sender_name

Added value: +{
+  "description": "sender_name",
+  "type": "string"
+}

changedInput schema / properties / sender_state / description

Previous value: -"CA adds Fin. Code §2102"New value: +"sender_state"

addedInput schema / properties / transfer_reference

Added value: +{
+  "description": "transfer_reference",
+  "type": "string"
+}

Changed9 schema fields changedJul 7, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: corridor | compare | rate | receive | mobile | compliance | news | diaspora | stablecoin-rails"New value: +"Which endpoint to call. Options: corridor | compare | rate | receive | mobile | compliance | news | diaspora | stablecoin-rails | remit_rights | remit_rights_letter"

changedInput schema / properties / action / enum

Previous value: -[
-  "corridor",
-  "compare",
-  "rate",
-  "receive",
-  "mobile",
-  "compliance",
-  "news",
-  "diaspora",
-  "stablecoin-rails"
-]New value: +[
+  "corridor",
+  "compare",
+  "rate",
+  "receive",
+  "mobile",
+  "compliance",
+  "news",
+  "diaspora",
+  "stablecoin-rails",
+  "remit_rights",
+  "remit_rights_letter"
+]

addedInput schema / properties / date_available

Added value: +{
+  "description": "Disclosed Date Available from the receipt (YYYY-MM-DD) — starts the 180-day clock",
+  "type": "string"
+}

addedInput schema / properties / fees_paid

Added value: +{
+  "description": "Fees paid USD",
+  "type": "string"
+}

addedInput schema / properties / issue

Added value: +{
+  "description": "never_arrived | arrived_late | arrived_short | wrong_person_paid | sender_typo_number | want_to_cancel | scam_recipient | want_documentation",
+  "type": "string"
+}

addedInput schema / properties / principal

Added value: +{
+  "description": "Transfer amount USD",
+  "type": "string"
+}

addedInput schema / properties / provider

Added value: +{
+  "description": "Western Union, Wise, Remitly, MoneyGram, Xoom…",
+  "type": "string"
+}

addedInput schema / properties / remedy_choice

Added value: +{
+  "description": "refund | resend (default refund)",
+  "type": "string"
+}

addedInput schema / properties / sender_state

Added value: +{
+  "description": "CA adds Fin. Code §2102",
+  "type": "string"
+}

First observedJul 6, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It mentions some traits (e.g., 'deterministic, no LLM' for rights, 'agent-tier preview' for rights-check) but omits critical operational details like data freshness, rate limits, authentication needs, or error behavior. The truncated sentence and endpoint count inconsistency further undermine clarity.

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

Conciseness2/5

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

The description is verbose, includes a pricing list, and is truncated mid-sentence ('liv'). The initial claim of '8 endpoints' conflicts with the 12 endpoints listed, making the structure confusing. It is not front-loaded with the core message and contains redundant details.

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?

For a tool with 42 parameters and 12 endpoints, the description does not explain how to combine parameters for each action, nor does it describe expected return values (no output schema). It fails to give enough context for an agent to correctly invoke the tool beyond knowing that it covers remittance data.

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

Parameters2/5

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

Although schema coverage is 100%, many parameter descriptions are tautological (e.g., 'issue', 'purpose', 'provider'). The tool description does not map parameters to specific endpoints or explain semantic relationships among the 42 parameters, leaving agents without meaningful guidance beyond the schema's weak descriptions.

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

Purpose4/5

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

The description clearly identifies the tool as a global remittance intelligence API, distinguishing it from sibling pulse tools by domain. However, it lacks a specific action verb (e.g., 'query' or 'analyze') and contains an inconsistency: it says '8 endpoints' but lists 12.

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?

No guidance is provided on when to use this tool versus alternative pulse tools. The description lists endpoints with use cases (e.g., corridor analysis, provider comparison) but does not explicitly state when to choose remittancepulse over siblings or which endpoint to pick for a given scenario.

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

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

B3.2/5.0

Disambiguation4/5

Each tool has a unique domain prefix (e.g., airdroppulse, alphapulse, arbipulse) making them mostly distinguishable at a glance. A few adjacent verticals like careerpulse vs talentpulse or marketpulse vs dealpulse have overlapping themes, but their descriptions clarify the distinct focus. The utility tools (catalog_search, discover, get_openapi_spec, x402_troubleshoot) are also clearly distinct in role. However, the sheer number of similar 'pulse' names could still cause misselection without reading descriptions.

Naming Consistency4/5

The dominant naming convention is `<domain>pulse` (e.g., climatepulse, cryptopulse, edupulse), which is highly consistent and predictable. Exceptions like catalog_search, discover, get_openapi_spec, x402_troubleshoot, and stateedge break the pattern, but these are few and serve obvious utility purposes. Overall, the convention is clear and easily learnable.

Tool Count2/5

With 80 tools, the server presents an extremely large and potentially overwhelming surface. While each tool represents a distinct intelligence vertical and navigation aids exist (catalog_search, discover, get_openapi_spec), the count far exceeds the typical 3-15 range for coherent agent use and even the 'heavy' 16-25 range. The burden of selecting the correct vertical from 80 options is significant, despite clear naming.

Completeness5/5

The server offers an exceptionally broad and deep coverage of domains, from finance and health to agriculture and gaming. Each vertical includes multiple endpoints that address core operations for its domain, such as search, analysis, comparisons, deterministic checks, and even action-oriented tools like letter generators and physical mail. The presence of free discovery and troubleshooting tools fills potential gaps, leaving no obvious dead ends in the overall tool surface.

remittancepulse

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources