Other · Remote MCP server
Lodestar Stamp
Dated, source-linked receipts before an agent recommends or books. Lodestar does not approve.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Banjo-Ventures/lodestar-stamp- Version
- 0.1.15
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- Banjo-Ventures (GitHub)
- Website
- lodestarstamp.com/docs
- Repository
- github.com/Banjo-Ventures/lodestar (folder packages/lodestar-stamp-mcp)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.lodestarindex.com/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | lodestar-stamp-mcp | 0.1.15 | stdio |
How to connect Lodestar Stamp
Lodestar Stamp is a remote MCP server: there is nothing to install. Its endpoint is https://api.lodestarindex.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: lodestar-stamp-mcp version 0.1.15. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y lodestar-stamp-mcp@0.1.15.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"lodestar-stamp": {
"command": "npx",
"args": [
"-y",
"lodestar-stamp-mcp@0.1.15"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Localize.ioAI localization for agents: translation, TMS sync, translation memories, glossaries, post-editing. | Remote · HTTP |
| Loci Labs Real-World ObservationsFresh human-observable information about physical places and conditions that may be stale online. | Remote · HTTP |
| LockboxEncrypted secrets for Next.js. AES-256-GCM with no vault needed. | Local · stdio |
| Lockstep MCPLocal lockfile and package-manager reproducibility analysis without dependency details. Tools... | Local · stdio |
| LodestoneOne connector URL giving any MCP client live access to 21 services and 51 tools. | Remote · HTTP |
| Logi ApprovalLogi Agent Approval Gate — human approval on the phone before high-risk agent actions. | Local · stdio |
| LogluneReproduce, inspect, diff and bisect feature-flag rulesets; author and publish flag changes. | Remote · HTTP |
| Logolark: Company Logo API & Favicon Finder by DomainLogolark: company domain to logo, square icon and brand colour. Free, no key. | Remote · HTTP |