Maps & transport · Remote MCP server
iParts Estonia Parts Catalogue
Read-only iParts Estonia auto parts catalogue: numbers, vehicles, categories, fitment, offers, oils.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ee.iparts/catalogue- Version
- 0.9.0
- Status
- Active
- Category
- maps & transport
- Transport
- Streamable HTTP
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- ee.iparts
- Namespace
- Namespace verified by the MCP Registry via the domain iparts.ee · how
- Website
- iparts.ee
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://iparts.ee/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 403)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 403
- Checked on
- 2026-10-05
How to connect iParts Estonia Parts Catalogue
iParts Estonia Parts Catalogue is a remote MCP server: there is nothing to install. Its endpoint is https://iparts.ee/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
Site checks
The website's own root, iparts.ee, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More maps & transport servers
| Server | Runs |
|---|---|
| IP Location MCPMCP server for IPv4 geolocation with Chinese output: country/region/city, ISP and ASN. | Remote · HTTPLive check: ✗ no handshake |
| Ip2location GeolocationLook up IP address location and geolocation data with country, city, timezone, and ISP details. | Local · stdio |
| IP99 IP risk & geolocationFree IP risk and geolocation lookup: proxy, VPN and datacenter detection. No API key. | Remote · HTTPLive check: ✓ handshake |
| Ipapi MCPIP geolocation from ipapi.co. No key required. | Local · stdio |
| IPGeolocation.io MCP ServerOfficial MCP server for IP geolocation, security, ASN, abuse, timezone, astronomy, and user-agent. | Local · stdio |
| Ipinfo MCPIPinfo.io IP address details: geolocation, ASN, org, carrier. | Local · stdio |
| Japan External ExecutionManual-review external execution in Japan for AI agents: human tasks, logistics, and verification. | Remote · HTTPLive check: ✓ handshake |
| JustRouting MCP ServerRoad routing, travel-time matrices, geocoding, and fleet optimization for Southeast Asia. | Local · stdio |