Lode MCP server
io.trylode/lodetrylode.iostreamable-httpv0.10.0Scanned
Check before installing an integration: sourced facts on Xero, QuickBooks, HubSpot, Vercel apps
9 tools: 3 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Lode MCP server can do
The Lode MCP server is published by trylode.io, a domain the MCP Registry verified. It has 9 tools. It can create or change data (3 tools: request_coverage, report_choice and report_error), but cannot delete data. 6 tools only read.
1 tool brings in text other people can write (list_ecosystems).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 0.10.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 3Claude Code: ask
report_choiceCall after comparing integrations, once the buyer has picked one (or none), if the user agrees.No findings
Why it is in this group
- The description's first verb is "call": a word for a change.
Description, as the server wrote it 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. 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.
Annotations the server declares
- title: Report which app was chosen
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
report_errorCall when a Lode fact looks wrong or out of date, for example when the vendor's own page says otherwise.No findings
Why it is in this group
- The description's first verb is "call": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Report a wrong fact
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
request_coverageCall when Lode has no record for an app and platform you needed, or its facts were missing or out of date.No findings
Why it is in this group
- The name "request_coverage" says "request": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Request coverage
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 6Show 6 read-only tools
compare_integrationsUse when choosing between apps for the same job.No findings
Why it is in this group
- The name "compare_integrations" says "compare": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Compare integrations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
find_integrationsUse before recommending or installing an integration: find apps that integrate with an ecosystem (xero, quickbooks-online, hubspot, vercel, netlify), filtered and ranked for a buye…No findings
Why it is in this group
- The name "find_integrations" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find integrations for a buyer
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_changesWhat changed in Lode records, newest first: prices, sync capabilities, limits, regions and verification status.No findings
Why it is in this group
- The name "get_changes" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Recent changes
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_integrationUse before installing, provisioning or recommending a specific integration, or to check a claim about it.No findings
Why it is in this group
- The name "get_integration" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get integration facts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_vendorOne 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).No findings
Why it is in this group
- The name "get_vendor" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get vendor
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_ecosystemsList 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 re…Reads text others writeNo findings
Why it is in this group
- The name "list_ecosystems" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "review": it reads comments, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: List ecosystems
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 21, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 502
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 502.
Posture changes
- Nov 21, 2026
- HTTP status of an anonymous initialize: 200 to 502
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 502; tools/list served without credentials: yes -> no; Protocol version: 2025-06-18 -> none.View diff
- HTTP status of an anonymous initialize: 200 to 502
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
Tools3 added, 6 changed.+3 added~6 changedView diff
- Added:report_choiceChanges things
- Added:report_errorChanges things
- Added:request_coverageChanges things
- Changed:compare_integrationsOnly readsdescriptioninputSchemaannotations
- Changed:find_integrationsOnly readsdescriptioninputSchemaannotations
- Changed:get_changesOnly readsinputSchemaannotations
- Changed:get_integrationOnly readsdescriptionannotations
- Changed:get_vendorOnly readsannotations
- Changed:list_ecosystemsOnly readsdescriptionannotations
Install
Pinned to version 0.10.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http lode https://trylode.io/mcpclaude mcp add --transport http lode https://trylode.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__lode__list_ecosystems",
"mcp__lode__find_integrations",
"mcp__lode__get_integration",
"mcp__lode__compare_integrations",
"mcp__lode__get_vendor",
"mcp__lode__get_changes"
],
"ask": [
"mcp__lode__request_coverage",
"mcp__lode__report_choice",
"mcp__lode__report_error"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lode. Review it before you use it.
Capability tags behind 1 rule
- mcp__lode__list_ecosystems untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.trylode/lode/verify?hash=82da77e40f24e96c226939d0e965e6a18d246dfb857fb114de99b7e1ef1a6dd5" | jq -e '.changed == false'Pinned hash 82da77e40f24, from Nov 20, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.trylode/lode/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.trylode/lode)Source: MCP Registry · repository. Synced Nov 20, 2026, 06:18 UTC.
Lode MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Lode MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Lode MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Lode MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Lode MCP server have?
- 9 tools: 3 write, 6 read. request_coverage, report_choice, report_error, list_ecosystems, find_integrations, get_integration, compare_integrations, get_vendor and 1 more.
Does the Lode MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Lode MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Lode MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.