Longbridge MCP integration for AI agents.
Connect AI agents to Longbridge through 80 structured actions, including get market temperature, ah premium, and ah premium intraday. Review authentication…
- ACTION CONTRACTS
- 80
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Longbridge integration exposes
The Longbridge Agent App exposes 80 provider-backed actions for finance and data work. Its current contract lets an authorized agent get the current longbridge market sentiment temperature for a market, list longbridge a/h premium k-line records for a dual-listed security, and list longbridge intraday a/h premium records for a dual-listed security. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Longbridge account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Longbridge capabilities.
Showing 12 of 80 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_market_temperatureREADGet the current Longbridge market sentiment temperature for a market.
INPUTS: market
ah_premiumREVIEWList Longbridge A/H premium K-line records for a dual-listed security.
INPUTS: symbol / period / count
ah_premium_intradayREVIEWList Longbridge intraday A/H premium records for a dual-listed security.
INPUTS: symbol
anomalyREVIEWList Longbridge quote change and anomaly records.
INPUTS: market / size / symbol
broker_holdingREVIEWList top Longbridge broker holdings for a security.
INPUTS: symbol / period
broker_holding_dailyREVIEWList daily Longbridge broker holding history for a broker and security.
INPUTS: symbol / brokerId
broker_holding_detailREVIEWGet detailed Longbridge broker holdings for a security.
INPUTS: symbol
business_segmentsREVIEWGet Longbridge business segment data for a security.
INPUTS: symbol
business_segments_historyREVIEWList Longbridge business segment history for a security.
INPUTS: symbol / report / category
buybackREVIEWGet Longbridge buyback data for a security.
INPUTS: symbol
companyREVIEWGet Longbridge company overview and profile data for a security.
INPUTS: symbol
consensusREVIEWGet Longbridge financial consensus estimates for a security.
INPUTS: symbol
INPUT CONTRACTS
Know what the action needs before it runs.
get_market_temperature
marketOPTIONAL- The Longbridge market code.
ah_premium
symbolREQUIRED- The Longbridge security symbol, such as AAPL.US or 700.HK.
periodREQUIRED- The A/H premium K-line period.
countREQUIRED- The number of records to request.
ah_premium_intraday
symbolREQUIRED- The Longbridge security symbol, such as AAPL.US or 700.HK.
anomaly
marketREQUIRED- The Longbridge market code.
sizeOPTIONAL- The number of records to request.
symbolOPTIONAL- The Longbridge security symbol, such as AAPL.US or 700.HK.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Market Temperature
Get the current Longbridge market sentiment temperature for a market. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_market_temperatureVerify with Ah Premium
List Longbridge A/H premium K-line records for a dual-listed security. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
ah_premiumSAFETY BOUNDARY
Operate Longbridge with explicit limits
- Authorize Longbridge with OAuth 2.0 and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Longbridge data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- The sampled contract declares provider scopes including `4`, `6`, `10`, and `11`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Longbridge task completed successfully.
CONNECTION MODEL
OAuth 2.0
Longbridge uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 18
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 62
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Longbridge.