Lode
REMOTE · TRYLODE.IO
Check before installing an integration: sourced facts on Xero, QuickBooks, HubSpot, Vercel apps
Available components
Last scanned (19 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1993 tokens (~221/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability check failed: schema churn in the 7 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +48
- Stability: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “report_choice” rewrote its description, which is the text the model reads security
- Schema quality: 137 → 221 ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: 77% → 100% ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: good → excellent functional
- “find_integrations” added an optional parameter “budget” cosmetic
- “find_integrations” added an optional parameter “company_stage” cosmetic
- “find_integrations” added an optional parameter “existing_stack” cosmetic
- “find_integrations” added an optional parameter “framework” cosmetic
- “report_choice” added an optional parameter “existing_stack” cosmetic
- “report_choice” added an optional parameter “failure_reason” cosmetic
- “report_choice” added an optional parameter “framework” cosmetic
- “report_choice” added an optional parameter “outcome” cosmetic
- “report_choice” added an optional parameter “switched_to” cosmetic
- 20 Nov 26 −42
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Transport: pass → fail ▼ security
- Stability: 0.17 → fail ▼ security
- Authorization: unverified → partial ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 137 → 172 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- “find_integrations” changed the type of “limit”: integer → number ▼ functional
- “get_changes” changed the type of “limit”: integer → number ▼ functional
- Tool coverage: 77% → 100% ▲ functional
- Schema quality: good → excellent functional
- Server version: 0.9.0 → 0.10.0 functional
- New tool “report_choice” functional
- New tool “report_error” functional
- New tool “request_coverage” functional
- “compare_integrations” reworded the description of “ids” cosmetic
- “find_integrations” reworded the description of “ecosystem” cosmetic
- “find_integrations” reworded the description of “limit” cosmetic
- “find_integrations” reworded the description of “needs” cosmetic
- “find_integrations” reworded the description of “region” cosmetic
- “get_changes” reworded the description of “limit” cosmetic
- 19 Nov 26 +42
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compare_integrations” rewrote its description, which is the text the model reads security
- Tool “find_integrations” rewrote its description, which is the text the model reads security
- Tool “get_integration” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.17 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 18 Nov 26 −42
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 0
- Tool “list_ecosystems” rewrote its description, which is the text the model reads security
- 15 Nov 26 +41
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 77 functional
- First check of Schema quality: good functional
- Server version: 0.8.0 → 0.9.0 functional
- 14 Nov 26 25
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://trylode.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trylode.io | CN=YE1,O=Let's Encrypt,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 53bd270fe076fedba60efb178de0d31fb20 |
| SANs: trylode.io, www.trylode.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trylode.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| trylode.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trylode.io/mcp | Verified | 200 | |
| http (plaintext) | http://trylode.io/mcp | HTTPS enforced | 301 | https://trylode.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_integrations Compare integrations ~75
Use when choosing between apps for the same job. Side-by-side facts for 2-4 integrations: sync coverage, cheapest price per currency, regions, setup time and limitations.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | 2 to 4 integration ids "{app}--{ecosystem}"; extra ids beyond 4 are ignored |
No output schema declared.
No examples provided.
find_integrations Find integrations for a buyer ~480
Use before recommending or installing an integration: find apps that integrate with an ecosystem (xero, quickbooks-online, hubspot, vercel, netlify), filtered and ranked for a buyer profile per Lode ranking policy (fit, not size or features). Returns score, match reasons and ties. Only published (verified) records are ranked; records still under review can be fetched by id with get_integration.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string|number | – | Monthly budget for this tool in USD, as a number or one of: free, under-50, 50-200, 200-1000, over-1000 |
| category | string | – | Category slug, e.g. "inventory", "crm", "payroll" |
| company_stage | string | – | One of: solo, startup, smb, mid-market, enterprise |
| ecosystem | string | yes | Ecosystem slug, e.g. "xero", "quickbooks-online", "hubspot", "vercel", "netlify" (names like "QuickBooks" are accepted) |
| existing_stack | array | – | Apps and platforms the buyer already uses, e.g. ["supabase","nextjs","vercel","stripe"] (up to 12). Results mark any app already in the stack. Product names only, never people or company names |
| framework | string | – | The app's framework, one of: nextjs, react, remix, astro, sveltekit, nuxt, vue, angular, express, nestjs, django, flask, fastapi, rails, laravel, spring, dotnet, go, react-native, flutter, other |
| limit | number | – | Results to return, 1 to 25 (default 10) |
| needs | array | – | Sync objects the buyer must have, from the ecosystem vocabulary (see list_ecosystems), e.g. ["invoices","inventory-levels"]; labels and common synonyms such as "customers" are accepted |
| region | string | – | Buyer country: AU, NZ, UK, US, CA, IE, ZA, SG (GB, country names and locale tags such as en-GB are accepted); filters to apps that support it. Prices are compared in local currency for AU, NZ, UK, US… |
No output schema declared.
No examples provided.
get_changes Recent changes ~164
What changed in Lode records, newest first: prices, sync capabilities, limits, regions and verification status. Each event has the old and new value, when Lode observed it, the sources behind it and a cause (new-coverage, lode-update, or source-change-likely when the cited page also changed).
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Ecosystem slug, e.g. "vercel" |
| id | string | – | Integration id "{app}--{ecosystem}" |
| include_new_coverage | boolean | – | Include "added to Lode" events (default false) |
| limit | number | – | 1 to 100 (default 25) |
| since | string | – | ISO date, e.g. "2026-11-01" |
No output schema declared.
No examples provided.
get_integration Get integration facts ~85
Use before installing, provisioning or recommending a specific integration, or to check a claim about it. Gets the full verified record for one app + ecosystem pair: what syncs, pricing by currency, regions, requirements, limitations, connection safety, sources.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Integration id "{app}--{ecosystem}", e.g. "shopify--xero" |
No output schema declared.
No examples provided.
get_vendor Get vendor ~75
One company across every ecosystem Lode covers: its stable vendor id, domains, and its integration on each platform (for example Stripe on Xero and on Vercel). Look up by vendor id, domain, or name.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Vendor id ("stripe"), domain ("stripe.com") or name ("Stripe") |
No output schema declared.
No examples provided.
list_ecosystems List ecosystems ~45
List the platforms Lode covers, with their sync-object vocabulary and how many integrations are published (verified) and how many are listed in total, including records held for review.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
report_choice Report which app was chosen ~409
Call after comparing integrations, once the buyer has picked one (or none), if the user agrees. Tells Lode which app was chosen and the main reason, from a fixed list. Returns the chosen app's verified setup facts (setup guide, steps where recorded, limitations). Call again with outcome once you have tried the integration: whether it worked, and if not, why and what you switched to. Choices are counted in aggregate and never affect Lode's rankings. Lode keeps only these fields, the time, the kind of client and an anonymous caller code.
| Name | Type | Req | Description |
|---|---|---|---|
| chosen | string | yes | The id chosen, or "none" |
| considered | array | yes | Integration ids that were compared, "{app}--{ecosystem}" (1 to 4) |
| existing_stack | array | – | Apps and platforms the buyer already uses, e.g. ["supabase","nextjs"] (product names only) |
| failure_reason | string | – | If failed or abandoned, one of: auth, api-error, docs, missing-feature, plan-required, pricing, region, sdk, limits, other |
| framework | string | – | One of: nextjs, react, remix, astro, sveltekit, nuxt, vue, angular, express, nestjs, django, flask, fastapi, rails, laravel, spring, dotnet, go, react-native, flutter, other |
| needs | array | – | Sync objects the buyer needed |
| outcome | string | – | After trying it, one of: integrated, failed, abandoned, not-tried |
| reason | string | – | Main reason, one of: sync-coverage, price, region, setup-effort, limitations, plan-requirement, already-uses, vendor-preference, other |
| region | string | – | Buyer country, e.g. "AU" |
| switched_to | string | – | If you moved to another app instead, its Lode id "{app}--{ecosystem}" |
No output schema declared.
No examples provided.
report_error Report a wrong fact ~149
Call when a Lode fact looks wrong or out of date, for example when the vendor's own page says otherwise. A person checks the report against the vendor's page before anything changes. Lode keeps only these fields, the time, the kind of client and an anonymous caller code.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | Which part, one of: sync, pricing, regions, requirements, limitations, connection, other |
| id | string | yes | Integration id "{app}--{ecosystem}" |
| object | string | – | For sync: the object, e.g. "invoices" |
| reason | string | – | One of: wrong, outdated, missing, source-broken (default wrong) |
No output schema declared.
No examples provided.
request_coverage Request coverage ~217
Call when Lode has no record for an app and platform you needed, or its facts were missing or out of date. Lode uses these requests to decide what to research next. If Lode already has the pair, the answer gives its id so you can call get_integration. Lode keeps only these fields (the app as a short cleaned name), the time, the kind of client and an anonymous caller code.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | The app's name or website, e.g. "Katana" or "katanamrp.com" |
| ecosystem | string | yes | Platform, e.g. "xero", "quickbooks-online", "hubspot", "vercel", "netlify", or another platform name |
| needs | array | – | Sync objects the buyer needed, e.g. ["invoices"] |
| reason | string | – | One of: not-covered, facts-missing, facts-outdated (default not-covered) |
| region | string | – | Buyer country, e.g. "UK" |
No output schema declared.
No examples provided.
How do I install the Lode MCP server?
Lode is a hosted endpoint at https://trylode.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · trylode.io
claude mcp add --transport http io-trylode-lode 'https://trylode.io/mcp'
What is the Lode MCP server?
Lode is an MCP server listed in the public MCP registry as io.trylode/lode. Check before installing an integration: sourced facts on Xero, QuickBooks, HubSpot, Vercel apps. This page covers its hosted endpoint (https://trylode.io/mcp).
Is the Lode MCP server safe to use?
Lode scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Lode MCP server expose?
Lode exposes 9 tools: list_ecosystems, find_integrations, get_integration, compare_integrations, get_vendor, and 4 more. Their descriptions and schemas cost roughly 1,699 tokens of context every time the server is loaded.
Does the Lode MCP server require authentication?
No. We connected to Lode without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lode MCP server still maintained?
Lode is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Lode MCP server?
VerifyMCP ran 13 checks on Lode, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.