Connect to triSearch's secure MCP in minutes. Use cached demo searches to test the workflow first, then order live searches through your triSearch account when you’re ready. No complex process and hassle free single endpoint
Have an triSearch account? Use the endpoint below to connect your agent and start placing orders straight away.
MCP Endpoint (Standard)
https://trisearch.com.au
MCP Endpoint (Search and Invoke — for limited-context agents)
https://trisearch.com.au
Not sure which endpoint to use?
Standard Mode
The full list of available services is presented to your agent on connection. The agent sees every service and can invoke any of them directly. This is the default and works well with capable models that can reason across a broad set of options.
Search and Invoke
If your agent has limited context capacity, or you have a large number of services enabled, the Gateway can expose a lightweight search-first pattern instead. Only a single discovery tool is presented initially. The agent describes what it needs, the Gateway identifies the right service, and the agent then invokes it.
This frees up context for the model and is recommended when working with smaller or more cost-sensitive models, or when the number of available services would otherwise consume significant token budget.
Which should I use? Start with Standard Mode. If you notice your agent struggling with service selection, or you want to reduce token usage, ask your InfoTrack representative to switch to Search and Invoke.
NEW TO TRISEARCH
Create your account today
Not a client yet? Set up an triSearch account and accept the terms. Your MCP access activates right away, and you can start placing demo orders you’re ready.
Authenticate with a triSearch API key, passed as an ApiKey Authorization header. Generate a key from the Manage API keys page in your triSearch account, then register the triSearch Gateway as a remote MCP server.
Anthropic Claude or Cowork
Click the link below, then click Add to add triSearch as a custom connector.
Click the Add to Claude link, press Connect, and sign in with your triSearch credentials. Your tools load automatically.
04.
Run a demo search
Use a demo client reference (DEMO-001, DEMO-002, or DEMO-003) to run test orders at no cost. Switch to your own client reference when you’re ready to go live.
Demo searches, free to run
Demo searches behave exactly like live orders but will not incur a cost, so you can build and test your full workflow before placing real orders. Place them under one of the demo client references below.
Always use a demo client reference
Demo orders only work under one of these references. Use any other reference and the order runs live and you will be charged.
Run a title search for title reference 1863/1000001
Get an on-file ASIC extract for Hancock Prospecting Pty Limited, ACN 008 676 417
Run a PPSR organisation search for Hancock Prospecting Pty Limited, ACN 008 676 417
Your agent discovers the available tools, selects the right one, and confirms any cost with you before placing an order. The full set of valid test inputs is below.
FULL SET OF VALID TEST INPUTS
Title Search: Land title lookup by title reference.
Test input
Reference
Demo title reference
1863/1000001
ASIC organisation extract: Organisation extract current & historical
The extract type is an argument that changes the result. Most test entities are available on-file; some also support current and historical.
No. Use your InfoTrack account to access the shared MCP endpoint and test with cached demo searches. No staging account or staging endpoint is required.
Are cached demo searches live searches?
No. Cached demo searches return prepared sample results for onboarding and testing. Live searches use current data and are billed through your InfoTrack account.
When can I order live searches?
After your InfoTrack account is active and your connector is set up, you can order live searches through your account when you need current results.
What do I need to connect triSearch to Claude?
You need your InfoTrack MCP URL, your InfoTrack API key, and access to Claude custom connectors.
Who can add the connector in Claude Team or Enterprise?
An Owner or Primary Owner may need to add the connector for the organisation first. Individual users can then connect and enable it in their own Claude workspace.
What if our AI app will be used by triSearch clients?
Your clients can create their own API keys and use the shared MCP endpoint. You can keep building and testing while any partner or revenue-share agreement is handled separately.
When do we need a dedicated MCP endpoint?
Most users can start with the shared MCP endpoint. A dedicated endpoint is created for partners who need customised tooling or revenue-share arrangements after the commercial agreement is complete.
Learn more about triSearch AI
Simply fill in your details and we will be in touch soon.