Add VINdata MCP remote server

[bhuvanabala]

Adds VINdata MCP, a remote Streamable HTTP MCP server for VIN decoding and European vehicle data.

Repository:
https://github.com/bhuvanabala/vindata-mcp

Endpoint:
https://vindata-mcp.vindata.workers.dev/mcp

Tool:
decode_vin

VINdata MCP is already published in the Official MCP Registry and indexed on Glama, PulseMCP, and Smithery.

[bhuvanabala]

VINdata MCP is already published in the Official MCP Registry and is live as a remote Streamable HTTP MCP server.

Repository:
https://github.com/bhuvanabala/vindata-mcp

Endpoint:
https://vindata-mcp.vindata.workers.dev/mcp

Tool:
decode_vin

It has also been indexed on Glama and PulseMCP.

[JAORMX]

Thanks for the submission, and for building on MCP! I took VINdata MCP for a spin — the endpoint is live and decode_vin responds correctly to a real initialize / tools/list handshake, so the server itself works. 👍

That said, I'm going to decline this for now. The entry doesn't yet meet our registry inclusion criteria, and I'd rather see the project mature a bit before it lands in the catalog. The main blockers:

• No license. The upstream repo has no LICENSE file, so the code is "all rights reserved" by default. We require a permissive license (Apache-2.0 / MIT / BSD-2 / BSD-3) — this is a hard gate.
• Documentation doesn't describe the server. The README is the unmodified Cloudflare remote-mcp-github-oauth demo template — it documents GitHub OAuth and demo tools (add, userInfoOctokit, generateImage), with nothing about VIN decoding or the decode_vin tool. We need a README that actually documents this server (setup, the tool, auth requirements).
• Project maturity / adoption. The repo was created only a few days ago, has no CI workflows, no tests, no releases or version tags, and no community traction yet. We'd like to see more real-world usage and a track record before adding it.
• No security/supply-chain signals. No SECURITY.md, no dependency automation (Dependabot/Renovate), and no build provenance.

One gentle clarification: being published in the upstream Official MCP Registry and indexed on Glama / PulseMCP / Smithery is great, but it isn't part of our inclusion criteria — we evaluate each entry independently against our own criteria.

If you'd like to resubmit once the above are addressed, a few catalog-specific notes to get it right next time:

• Location & namespace: new entries go under registries/toolhive/servers/<name>/, normalized under the io.github.stacklok namespace (see the README and docs/adding-entries-llm.md) — not directly under registries/official/ with a third-party namespace.
• Tier: third-party servers are "tier": "Community", not "Official" (Official is reserved for the ToolHive team, MCP spec authors, or the platform owner of the service).
• Icon: use a repo-hosted icon.svg (image/svg+xml) in the server directory rather than an external PNG.
• Add the repository field, and drop the hand-set metadata block — metadata.* is auto-populated by CI.

Appreciate the contribution — please do come back once the project has a license, real docs, and a bit more mileage.

[JAORMX]

commented