Finance · Remote MCP server
Jupiter Invoice
Create and manage invoices and customers on Jupiter Invoice (MCP, API-key auth).
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.jupiterinvoice/server- Version
- 1.0.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-06-29
- Updated
- 2026-06-29
- Publisher
- com.jupiterinvoice
- Namespace
- Namespace verified by the MCP Registry via the domain jupiterinvoice.com · how
- Website
- jupiterinvoice.com
- Repository
- github.com/middlefieldgs/JupiterInvoice
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://jupiterinvoice.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Jupiter Invoice
Jupiter Invoice is a remote MCP server: there is nothing to install. Its endpoint is https://jupiterinvoice.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.
Derived from the registry entry; the live check above only shows whether the endpoint answered. 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 finance servers
| Server | Runs |
|---|---|
| JP Data (Japanese Public Business Data)Japanese open-data MCP server: corporate-number validation, zengin bank codes, national holidays. | Local · stdio |
| JPYC Agent MCPOAuth-protected JPYC wallet, transfer, and contract workflows on Polygon. | Remote · HTTPLive check: ✗ no handshake |
| Json Repair MCPRepairs malformed JSON from LLM output, validated against a schema. Paid per call via Stripe. | Local · stdio |
| Junto MCPThe payment protocol for people and agents. One MCP server, any payment rail. | Local · stdio |
| Jupiter MCPJupiter - 4 tools for swap quotes, liquidity pools, and trading data. | Remote · HTTPLive check: ✗ no handshake |
| Jupiter Solana Swap Quote APISolana swap quotes via Jupiter - best route, price impact, priority fees, USD pricing. x402. | Remote · SSELive check: ✗ no handshake |
| JupitersignupList, read, create, and edit JupiterSignup sign-up and payment forms. API key required. | Remote · HTTPLive check: sign-in required |
| JYOTINT Sealed ForecastsBitcoin-anchored sealed-forecast record: search, grades, calibration, luck test. Read-only, no key. | Remote · HTTPLive check: ✓ handshake |